Platform
python
Component
premsql
Fixed in
0.2.1
0.2.2
A code injection vulnerability has been discovered in premsql versions 0.2.0 through 0.2.1. This flaw resides within the eval function of the premsql/agents/baseline/workers/followup.py file, allowing attackers to manipulate the result argument and potentially execute arbitrary code. The vulnerability is remotely exploitable and a public exploit is available, increasing the risk of immediate attacks. While a fix is not yet available, mitigation strategies are possible.
Successful exploitation of CVE-2026-5594 allows an attacker to execute arbitrary code on the system running premsql. This could lead to complete system compromise, including data exfiltration, modification, or deletion. Given the remote nature of the vulnerability and the availability of a public exploit, the potential impact is significant. An attacker could leverage this to gain persistent access, move laterally within the network if premsql is integrated with other systems, and potentially compromise sensitive data managed by the application. The blast radius extends to any data processed or stored by premsql.
This vulnerability is considered actively exploitable due to the public availability of a proof-of-concept. It was disclosed on 2026-04-05. The vendor, premsql, was contacted but did not respond. The vulnerability is not currently listed on CISA KEV, but its public exploit status warrants close monitoring. The ease of exploitation suggests a potentially high probability of widespread attacks if left unaddressed.
Exploit Status
EPSS
0.05% (15% percentile)
CISA SSVC
CVSS Vector
Due to the lack of a direct patch, mitigation focuses on limiting the attack surface. Implement strict input validation on all data passed to the eval function within premsql/agents/baseline/workers/followup.py. Specifically, sanitize the result argument to prevent malicious code injection. Consider restricting the execution environment of premsql to a sandboxed container with limited privileges. While not a complete solution, this can reduce the potential impact of a successful exploit. Monitor system logs for unusual activity related to premsql, particularly any attempts to execute unexpected commands. Regularly review and update the codebase to address potential vulnerabilities.
Update to a patched version of premsql that addresses the code injection (Code Injection) vulnerability. Review the source code to identify and remove any instances of the `eval` function that may be vulnerable to argument manipulation. Implement robust input validation to prevent code injection (Code Injection).
Vulnerability analysis and critical alerts directly to your inbox.
CVE-2026-5594 is a medium severity code injection vulnerability affecting premsql versions 0.2.0–0.2.1. It allows attackers to execute arbitrary code by manipulating the 'result' argument in a specific file.
You are affected if you are using premsql versions 0.2.0 or 0.2.1 and have not implemented mitigation strategies. The vulnerability is remotely exploitable and a public exploit exists.
A direct patch is not yet available. Mitigation involves strict input validation on the 'result' argument and restricting the execution environment of premsql.
Yes, a public exploit is available, indicating a high probability of active exploitation. Monitor your systems closely for suspicious activity.
As of the disclosure date, premsql has not released an official advisory. Monitor the premsql project's website and GitHub repository for updates.
Upload your dependency file and we'll tell you instantly if this and other CVEs hit you.
Upload your requirements.txt file and we'll tell you instantly if you're affected.