Agenta is an open-source LLMOps platform. A Server-Side Template Injection (SSTI) vulnerability exists in versions prior to 0.86.8 in Agenta's API server evaluator template rendering. Although the vulnerable code lives in the SDK package, it is executed server-side within the API process when running evaluators. This does not affect standalone SDK usage — it only impacts self-hosted or managed Agenta platform deployments. Version 0.86.8 contains a fix for the issue.
CVE-2026-27961
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.8
- EG Score
- 8.8(low)
- EG Risk
- 44(Track)EG Risk 44/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity88% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 24%
- KEV
- Not listed
Published
February 26, 2026
Last Modified
June 17, 2026
References (1)
- security-advisories@githubhttps://github.com/Agenta-AI/agenta/security/advisories/GHSA-cfr2-mp74-3763
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| agenta | 0.1.0 ... 0.9.0 (461 versions) | 0.86.8 | — |
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-08-01 04:16 UTCEPSS rescore
- 2026-07-30 16:27 UTCEPSS rescore
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-28 15:36 UTCEPSS rescore
- 2026-07-27 13:34 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-1336
- CVE-2025-12107NVD 7.2EG 10.0CRITICAL
- CVE-2025-34300EG 10.0EPSS p99CRITICAL
- CVE-2025-53833EG 10.0EPSS p95CRITICAL
- CVE-2025-47916EG 10.0EPSS p100CRITICAL
- CVE-2025-46661EG 10.0CRITICAL
- CVE-2024-32651EG 10.0EPSS p100CRITICAL
- CVE-2025-14700EG 9.9EPSS p93CRITICAL
- CVE-2025-32461EG 9.9CRITICAL
- CVE-2025-23211EG 9.9CRITICAL
- CVE-2024-12583EG 9.9CRITICAL
Frequently asked(5)
What is CVE-2026-27961?
When was CVE-2026-27961 disclosed?
Is CVE-2026-27961 actively exploited?
What is the CVSS score of CVE-2026-27961?
How do I remediate CVE-2026-27961?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27961
Is Your Infrastructure Affected by CVE-2026-27961?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.