Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.8

How to Fix CVE-2026-27952: Code injection in agenta-api

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27952 is a code injection in Agenta-AI agenta-api. The fix is to apply the vendor patch noted below.

⚡ At a glance
Severity8.8 (High)
Actively exploited?No public listing in CISA KEV
Affectedagenta-api < 0.48.1
Fixed inSee vendor advisory
Type (CWE)CWE-94: Improper Control of Generation of Code ('Code Injection')

What is CVE-2026-27952?

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. The CVSS base score is 8.8 (High), which puts this in the upper risk band and warrants a fast patch cycle. The official advisory is at https://github.com/Agenta-AI/agenta/security/advisories/GHSA-pmgp-2m3v-34mq.

Am I affected?

Check the version of agenta-api you are running and compare it against the Affected row above (agenta-api < 0.48.1). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s agenta-api 2>/dev/null | grep -i ^Version
rpm -q agenta-api 2>/dev/null
command -v agenta-api >/dev/null && agenta-api --version 2>/dev/null

# Windows (PowerShell)
Get-Package -Name "*agenta-api*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "agenta-api" 2>$null

How to fix CVE-2026-27952

Upgrade agenta-api to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade agenta-api
dpkg -s agenta-api | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh agenta-api -y
# or for older releases:
sudo yum update agenta-api -y
rpm -q agenta-api

SUSE / openSUSE


sudo zypper refresh
sudo zypper update agenta-api
rpm -q agenta-api

Python / pip


pip install --upgrade agenta-api
pip show agenta-api | grep -i version

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-27952 affecting agenta-api
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27952-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*agenta-api*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\agenta-api-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\agenta-api" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "agenta-api" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "agenta-api"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-27952 affecting agenta-api
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27952-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s agenta-api 2>/dev/null | grep -i ^Version || echo "agenta-api not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q agenta-api || echo "agenta-api not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27952-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/agenta-api /etc/agenta-api.d /etc/agenta-api.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y agenta-api
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y agenta-api
elif command -v yum >/dev/null; then
    yum update -y agenta-api
elif command -v zypper >/dev/null; then
    zypper --non-interactive update agenta-api
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s agenta-api 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q agenta-api
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-27952" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27952"

Disable the affected service (Linux)


sudo systemctl stop agenta-api 2>/dev/null || true
sudo systemctl disable agenta-api 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s agenta-api 2>/dev/null | grep -i ^Version
rpm -q agenta-api 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true

# Windows
Get-Package -Name "*agenta-api*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

Is CVE-2026-27952 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27952?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27952?

8.8 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

Where is the official advisory for CVE-2026-27952?

The vendor advisory is at https://github.com/Agenta-AI/agenta/security/advisories/GHSA-pmgp-2m3v-34mq. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27952.

References


*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*