Skip to content
Cloud

CVE-2026-16796

8.4
High
EPSS 0.63%Patch availableJul 24, 2026

Authenticated RCE via crafted package names in AWS Bedrock AgentCore Python SDK.

common questions

Is CVE-2026-16796 being exploited?

Not confirmed. CVE-2026-16796 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.63% probability of exploitation in the next 30 days.

How severe is CVE-2026-16796?

CVE-2026-16796 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-16796?

Yes. A fix has been recorded for CVE-2026-16796. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-16796 affect?

CVE-2026-16796 affects AWS Bedrock AgentCore Python SDK <1.18.1, AWS Bedrock Code Interpreter sandbox, Applications using vulnerable SDK install_packages(). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-16796?

Upgrade AgentCore SDK to >=1.18.1 and audit package install inputs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
AWS Bedrock AgentCore Python SDK <1.18.1AWS Bedrock Code Interpreter sandboxApplications using vulnerable SDK install_packages()
impact

Authenticated attacker can execute arbitrary commands in the Code Interpreter sandbox via crafted package-name arguments, enabling RCE and potential data exposure.

action required

Immediate action required

affected versions
AWS bedrock-agentcore 1.18.1
  • affected< 1.18.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free