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.
CVE-2026-60086
MEDIUMPre-NVD 5.35.3—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.3 from GitHub Security Advisory published 2026-07-10. a secondary CVSS source baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EPSS
- 12.5%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
Advisory Details (2)
Auto-updated Jul 10, 2026🔬 Proof of concept available. Patch available. Sources: github.
generic
PraisonAI before 4.6.78 Prompt Injection Defense Bypass | Advisories | VulnCheck
https://www.vulncheck.com/advisories/praisonai-before-prompt-injection-defense-bypassgithub Patch Available🟡 PoC Available
Prompt-injection defense blocks only when 3+ detector families fire simultaneously; realistic single-vector injections pass through unblocked · Advisory · MervinPraison/PraisonAI · GitHub
https://github.com/MervinPraison/PraisonAI/security/advisories/GHSA-4r3p-w3mc-5v34Vendor Advisories for CVE-2026-60086(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-11 14:45 UTCEG score recompute
- 2026-07-11 14:45 UTCGHSA enrichment
- 2026-07-10 14:43 UTCEG score recompute
- 2026-07-10 14:42 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-60086?
CVE-2026-60086 is a medium vulnerability published on July 10, 2026. 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…
When was CVE-2026-60086 disclosed?
CVE-2026-60086 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-60086 actively exploited?
CVE-2026-60086 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-60086?
CVE-2026-60086 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-60086?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-60086, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-60086
Is Your Infrastructure Affected by CVE-2026-60086?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.