CVE-2026-60090 Mervin Praison CVE debrief

Who should care

Users of PraisonAI before version 4.6.78 should be aware of this vulnerability and take immediate action to upgrade to a patched version. Additionally, administrators and security teams should be vigilant for potential exploitation attempts and review compensating controls for exposed systems while remediation is scheduled and verified. Operators, platform administrators, vulnerability management teams, and security teams should prioritize this vulnerability due to its critical severity and potential impact.

Technical summary

The vulnerability occurs in the create_collection() backends of PGVector and Cassandra knowledge-store in PraisonAI before version 4.6.78. The dimension argument, which is declared as an integer but not enforced at runtime, is directly interpolated into the vector column of the generated CREATE TABLE DDL. This allows an attacker to inject malicious SQL/CQL tokens into the database driver. For example, an attacker could pass a string such as '3); DROP TABLE tenant_secrets; --' to inject SQL/CQL tokens into the statement executed by the database driver.

Defensive priority

Highest Priority Given the high CVSS score of 9.3 and the potential for significant impact, this vulnerability should be addressed with the highest priority. Immediate action is required to upgrade to a patched version of PraisonAI and to implement additional security measures to detect and prevent SQL injection attacks. Monitoring for potential exploitation attempts and responding accordingly is also crucial. Compensating controls should be reviewed and implemented for exposed systems while remediation is scheduled and verified. Asset inventory and rollback/change windows should be considered in the remediation process. Tracking exceptions, retesting remediated assets, and closing the item only after evidence is documented are essential steps in ensuring the vulnerability is fully addressed. Source tracking and exposure review are also recommended to ensure a comprehensive approach to mitigating this vulnerability. The vulnerability management team should work closely with operators, platform administrators, and security teams to ensure that all necessary steps are taken to mitigate this critical vulnerability effectively. Given the potential for significant operational impact, it is essential to treat this vulnerability with the utmost urgency and to allocate necessary resources to address it promptly and effectively. The defensive priority is therefore classified as 'Highest Priority,' reflecting the need for immediate and comprehensive action to mitigate this critical vulnerability effectively. The recommended actions provided earlier should be followed closely to ensure that all aspects of the vulnerability are addressed, and that the risk is mitigated to an acceptable level. By prioritizing this vulnerability and taking prompt action, organizations can minimize the risk of exploitation and protect their assets from potential harm. Therefore, the defensive priority for CVE-2026-60090 is 'Highest Priority,' and it is essential to address this vulnerability with the urgency and comprehensiveness that it deserves. The CVSS score and potential impact of this vulnerability justify this high level of priority, and it is crucial to treat it accordingly to ensure a

Recommended defensive actions

• Upgrade to PraisonAI version 4.6.78 or later
• Validate and sanitize user input for the dimension argument
• Implement additional security measures to detect and prevent SQL injection attacks
• Monitor for potential exploitation attempts and respond accordingly
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Perform asset inventory and track exceptions for remediation
• Conduct source tracking and exposure review for affected deployments

Evidence notes

The vulnerability was reported by Vulncheck and is publicly disclosed. The CVE record was published on 2026-07-11T14:16:22.353Z and has not been modified since then. The NVD entry is currently in the 'Received' state. There is limited information available about the specific details of the vulnerability, and defenders should verify the affected scope and severity with the vendor. The PraisonAI version 4.6.78 patch is being evaluated for completeness, and additional information may be provided as it becomes available.

Official resources