CVE-2026-60086: PraisonAI Prompt Injection Defense Bypass (v4.6.78)
PraisonAI versions before 4.6.78 have a weakness in their prompt injection defense system. The defense is designed to block dangerous attacks, but it only stops threats it classifies as CRITICAL—which requires matching three or more threat detection families at once. Attackers can bypass this by crafting simpler prompt injections that are classified as HIGH severity instead, allowing malicious inputs to reach the underlying AI model without being blocked.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 5.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- Weaknesses (CWE)
- CWE-693
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-10 / 2026-07-14
NVD description (verbatim)
PraisonAI before 4.6.78 contains a prompt injection defense bypass vulnerability where the injection defense only blocks threats classified as CRITICAL, requiring three or more detector families to match simultaneously. Attackers can craft single or double-vector prompt injections that are classified as HIGH threat level and pass through unblocked to reach the model.
3 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
CVE-2026-60086 is a prompt injection defense bypass in PraisonAI affecting versions prior to 4.6.78. The vulnerability stems from an insufficiently restrictive classification threshold in the injection defense mechanism. The system blocks only threats classified as CRITICAL severity, a threshold requiring simultaneous matches across three or more detector families. Attackers can craft single or double-vector prompt injections that trigger only HIGH-level threat classifications, circumventing the defense and reaching the language model. This represents a failure in layered defense design where the protection strategy depends on a single severity cutoff rather than a more nuanced risk model.
Business impact
This vulnerability enables attackers to inject malicious prompts into PraisonAI systems without triggering automated safeguards. Depending on how PraisonAI is deployed, successful prompt injection could lead to data exfiltration, model manipulation, unauthorized information access, or misuse of the AI for generating harmful content. For organizations using PraisonAI in customer-facing or data-sensitive applications, the risk includes reputational damage, compliance violations, and loss of user trust. The impact is moderated by the MEDIUM severity rating and the requirement for network access, but the ease of crafting bypassing prompts makes this a practical risk.
Affected systems
PraisonAI installations running versions before 4.6.78 are vulnerable. The vulnerability is network-accessible (no authentication required) and does not depend on user interaction or system configuration. Any deployment of affected PraisonAI versions is exposed if it processes untrusted prompt input from external sources.
Exploitability
Exploitation requires only network access and the ability to send a crafted prompt to a vulnerable PraisonAI instance. No special privileges, authentication, or user interaction are needed. The barrier to exploitation is low—attackers can use common prompt injection techniques adjusted to fall below the CRITICAL detection threshold. The CVSS score of 5.3 reflects the low complexity and high accessibility of the attack vector, though the impact is limited to integrity (prompt manipulation rather than confidentiality breach or availability loss).
Remediation
Organizations must upgrade PraisonAI to version 4.6.78 or later. The patched version is expected to address the defense bypass by either raising the detection threshold, improving the detector tuning to catch HIGH-severity injections, or implementing a more robust multi-layered defense strategy. Verify the specific improvements in the vendor advisory before deployment.
Patch guidance
Apply PraisonAI version 4.6.78 or later as soon as feasible. Verify the patch release notes confirm remediation of the prompt injection bypass. Test the update in a non-production environment first to ensure compatibility with your workflows. After patching, consider conducting prompt injection testing to validate the defense improvements. Since the vulnerability requires network access, prioritize patching any internet-facing or user-accessible PraisonAI instances.
Detection guidance
Monitor PraisonAI instances for HIGH-severity threat classifications that are being allowed to proceed to the model. Log and alert on prompt inputs that contain known injection patterns (such as jailbreak phrases, privilege escalation attempts, or data extraction commands) even if they do not trigger CRITICAL classification. Implement network-level monitoring to detect unexpected query patterns or volumes that may indicate active exploitation. Review model outputs for signs of manipulation or unexpected behavior that could indicate successful injection attacks.
Why prioritize this
While the CVSS score is MEDIUM (5.3), the practical ease of exploitation and the low barrier to attack (no authentication, no complexity) make this a near-term priority for any organization running PraisonAI. The vulnerability is not currently tracked in CISA's Known Exploited Vulnerabilities catalog, but the simplicity of crafting bypassing prompts means exploitation risk will grow as awareness spreads. Prioritize patching if PraisonAI is used in production or customer-facing applications.
Risk score, explained
The CVSS 3.1 score of 5.3 reflects a MEDIUM severity vulnerability with network accessibility (AV:N), low attack complexity (AC:L), no privilege requirement (PR:N), and no user interaction (UI:N). The impact is limited to integrity (I:L) with no confidentiality or availability impact, which caps the score below HIGH. However, the real-world exploitability is higher than the score suggests because the defense mechanism is fundamentally flawed; improving detection tuning alone may not fully address the underlying design issue.
Frequently asked questions
Can attackers exploit this without sending traffic to PraisonAI directly?
No. The vulnerability requires network access to a PraisonAI instance and the ability to send crafted prompts to it. If PraisonAI is running on an internal network without internet exposure, the risk is lower, but insider threats or compromised lateral network access could still enable exploitation.
What happens if a HIGH-severity injection gets through? What's the worst-case outcome?
Once a prompt injection reaches the underlying language model, the attacker can attempt to extract training data, manipulate model outputs, trigger unauthorized actions, or generate harmful content. The specific harm depends on how the model is integrated into your application and what data or capabilities it can access. Integrity is the primary impact, but downstream consequences could be severe.
If we patch to 4.6.78, are we fully protected against prompt injection?
Patching to 4.6.78 addresses this specific defense bypass vulnerability. However, prompt injection is a broad threat category, and new techniques continue to emerge. Patching removes this known weakness but does not eliminate all prompt injection risk. Consider defense-in-depth measures such as input validation, output filtering, and model behavior monitoring.
Why does the defense only block CRITICAL and not HIGH or MEDIUM threats?
The vendor likely chose a high threshold (CRITICAL + three detector families) to minimize false positives and allow legitimate use. However, this creates a gap where lower-severity injections pass through. The patch should recalibrate this threshold based on actual risk assessment rather than detection confidence alone.
This analysis is based on the CVE record and vendor information available as of 2026-07-14. Verify all technical details against the official PraisonAI security advisory before implementing remediation. Exploit proof-of-concepts and detailed attack code are not provided in this analysis to reduce risk of weaponization. Organizations should conduct internal testing and threat modeling specific to their deployment and data sensitivity. SEC.co makes no guarantee of the completeness or accuracy of this analysis and recommends independent security review. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).
Weaknesses (CWE)
Related vulnerabilities
- CVE-2025-30431MEDIUMmacOS Private Information Disclosure Vulnerability – Patch Guidance
- CVE-2025-48571MEDIUMAndroid Bluetooth SMS Interception Vulnerability (CVSS 4.3)
- CVE-2026-10174MEDIUMAider 0.86.3 Pre-commit Hook Bypass Vulnerability
- CVE-2026-10944MEDIUMChrome iOS Autofill Data Leak Vulnerability – Patch Now
- CVE-2026-10950MEDIUMChrome iOS Autofill Data Leak Vulnerability – Patch Guide
- CVE-2026-11174MEDIUMChrome Site Isolation Bypass – CVSS 5.3 Medium Vulnerability
- CVE-2026-11206MEDIUMChrome Service Worker Data Leak Vulnerability – CVSS 6.5
- CVE-2026-11219MEDIUMGoogle Chrome Navigation Bypass Vulnerability – Patching Guide