dbcve.org
AgentaApplication · Agentatech

CVE-2026-27952

CRITICAL · 9.9 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 0.48.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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. In Agenta-API prior to version 0.48.1, a Python sandbox escape vulnerability existed in Agenta's custom code evaluator. Agenta used RestrictedPython as a sandboxing mechanism for user-supplied evaluator code, but incorrectly whitelisted the `numpy` package as safe within the sandbox. This allowed authenticated users to bypass the sandbox and achieve arbitrary code execution on the API server. The escape path was through `numpy.ma.core.inspect`, which exposes Python's introspection utilities — including `sys.modules` — thereby providing access to unfiltered system-level functionality like `os.system`. This vulnerability affects the Agenta self-hosted platform (API server), not the SDK when used as a standalone Python library. The custom code evaluator runs server-side within the API process. The issue is fixed in v0.48.1 by removing `numpy` from the sandbox allowlist. In later versions (v0.60+), the RestrictedPython sandbox was removed entirely and replaced with a different execution model.

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 sandbox escape vulnerability existed in Agenta's custom code evaluator where RestrictedPython incorrectly whitelisted the numpy package. Attackers exploited numpy.ma.core.inspect to access sys.modules, bypassing sandbox restrictions and achieving arbitrary code execution on the API server.

MitigationUpgrade Agenta-API to version 0.48.1 or later (v0.60+ recommended, which removes RestrictedPython entirely). If upgrading is not feasible, disable the custom code evaluator feature.

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.48.1

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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. Identify Agenta version
    Locate the installed Agenta package or check the running API version (typically via package metadata, container label, or API endpoint response headers). Compare the version number to the affected range: versions prior to 0.48.1 are vulnerable.
    Affected if Installed version is earlier than 0.48.1
  2. Confirm custom code evaluator is enabled
    Inspect the Agenta configuration or environment variables to determine if the custom code evaluator feature is active. Look for configuration flags or settings related to code execution, sandbox, or evaluator functionality.
    Affected if Custom code evaluator feature is enabled and running
  3. Verify numpy package availability in sandbox
    Examine the RestrictedPython configuration or whitelisted packages list used by the custom code evaluator. Determine whether numpy is included in the allowed packages.
    Affected if numpy is whitelisted or accessible within the RestrictedPython sandbox
  4. Check for numpy.ma.core.inspect access
    Test whether the sandbox permits access to numpy.ma.core.inspect, which can be used to retrieve sys.modules and bypass sandbox restrictions. This may require attempting a controlled code execution test or reviewing sandbox module access logs.
    Affected if numpy.ma.core.inspect is reachable from within the sandbox environment

The environment is affected if running Agenta version below 0.48.1 with the custom code evaluator enabled and numpy accessible in the RestrictedPython sandbox.

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.48.1 or later
Fixed in 0.48.1
Interim mitigation

Upgrade Agenta-API to version 0.48.1 or later (v0.60+ recommended, which removes RestrictedPython entirely). If upgrading is not feasible, disable the custom code evaluator feature.

Recommended fix High confidence

v0.48.1 (or later; v0.60+ recommended as it removes RestrictedPython entirely)

  1. Upgrade Agenta-API to version 0.48.1 or later to remediate the numpy sandbox escape vulnerability
  2. After upgrading, verify that the custom code evaluator functionality still works as expected, as numpy was removed from the sandbox allowlist
  3. If using Agenta v0.60 or later, verify that the new execution model (replacing RestrictedPython) is functioning correctly
  4. Restart the Agenta-API service to apply the changes
Caveat Removing numpy from the sandbox allowlist may break existing custom code evaluators that depend on numpy functionality within the sandbox

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

Fix this in Agenta Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27952 — 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-27952 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