dbcve.org
AgentaApplication · Agentatech

CVE-2026-27961

HIGH · 8.8 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 0.86.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A Server-Side Template Injection (SSTI) vulnerability exists in Agenta's API server evaluator template rendering in versions prior to 0.86.8. The vulnerable code resides in the SDK package but executes server-side within the API process when running evaluators, allowing attackers to inject malicious template code that is interpreted server-side. This vulnerability only impacts self-hosted or managed Agenta platform deployments, not standalone SDK usage.

MitigationUpgrade to version 0.86.8 or later to remediate the SSTI vulnerability. For self-hosted deployments, ensure the API server is updated to the patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AgentaApplication
Affected:< 0.86.8

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm self-hosted or managed Agenta deployment
    Identify if you are running a self-hosted or managed Agenta platform deployment rather than using the SDK in standalone mode. Check if there is an API server process running (agenta-api, agenta-backend, or similar) that handles evaluator requests.
    Affected if The environment is a self-hosted or managed Agenta platform with an API server present
  2. Locate the installed Agenta version
    Check the version of your Agenta installation. For Docker deployments, inspect the container image tags or docker-compose.yml version specifications. For pip installations, run 'pip show agenta' or check the version in your requirements.txt. For Git installations, check the git tags or commit hash against release tags.
    Affected if The installed version is earlier than 0.86.8 (e.g., 0.86.7, 0.86.0, 0.85.0, etc.)
  3. Verify evaluator functionality is in use
    Determine if the evaluator template rendering feature is active. Check if evaluator workflows, prompt evaluators, or custom evaluation templates are configured or being used in your deployment. Review application logs for evaluator-related endpoints (e.g., /api/evaluate, /api/evaluators, or similar API paths).
    Affected if Evaluator templates are being rendered through the API server, enabling the SSTI attack surface

You are affected if you run a self-hosted or managed Agenta platform deployment with an API server version earlier than 0.86.8 that uses evaluator template rendering functionality.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.86.8 or later
Fixed in 0.86.8
Interim mitigation

Upgrade to version 0.86.8 or later to remediate the SSTI vulnerability. For self-hosted deployments, ensure the API server is updated to the patched version.

Recommended fix High confidence

0.86.8

  1. 1. Backup your current Agenta deployment and database before upgrading
  2. 2. Identify your current deployment method (Docker/docker-compose or Kubernetes)
  3. 3. For Docker/docker-compose: Edit your docker-compose.yml file and update the agenta image tag from your current version to '0.86.8'
  4. 4. For Kubernetes: Update the container image version in your deployment manifests to '0.86.8'
  5. 5. Pull the updated container images
  6. 6. Redeploy or restart your Agenta services
  7. 7. Verify the upgrade was successful by checking the Agenta version in the web UI or via API
  8. 8. Test that evaluators function correctly after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Agenta Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27961 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27961 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data