CVE-2026-11393
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 · uneditedImproper neutralization of triple-quote characters during Python code generation in AgentCore CLI before v0.14.2 might allow an authenticated remote threat actor to execute arbitrary code on AWS AgentCore Runtime under the imported agent's IAM execution role and on the local environment of another user in the same AWS account, via a crafted collaborationInstruction stored on a Bedrock Agent collaborator and later processed by that other user during agent import. To remediate this issue, users should upgrade to version 0.14.2.
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 confidenceImproper neutralization of triple-quote characters in Python code generation within AgentCore CLI before v0.14.2 allows authenticated attackers to inject arbitrary Python code via crafted collaborationInstruction stored on Bedrock Agent collaborators. When another user imports the agent, the malicious code executes under the imported agent's IAM execution role and on the user's local environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check if AgentCore CLI is installedRun command: pip show agentcore or pip list | grep -i agentcore. Also check for AWS Bedrock agent configurations in your environment.Affected if AgentCore CLI is installed and version is below 0.14.2
-
Verify AgentCore CLI versionRun: pip show agentcore or agentcore --version to get the exact version numberAffected if Version is present and lower than 0.14.2
-
Inspect Bedrock Agent collaborators for collaborationInstructionsReview AWS Bedrock Agent configurations for any collaborator definitions that contain the collaborationInstructions field. Use AWS CLI: aws bedrock-agent list-agents and inspect agent collaborator configurations.Affected if Any Bedrock Agent collaborators exist with collaborationInstructions that contain triple-quote characters (""") or unusual Python-like code patterns
-
Check for recently imported agentsReview logs or configurations for imported Bedrock Agents from other users. Check agent import history and source repositories.Affected if Agents were imported from untrusted sources or external collaborators since the vulnerability exists
User is affected if AgentCore CLI version is below 0.14.2 AND there are Bedrock Agent collaborators with crafted collaborationInstructions containing triple-quote characters or injected Python code.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade AgentCore CLI to version 0.14.2 or later to remediate the triple-quote injection vulnerability.
v0.14.2
- Check the current version of AgentCore CLI installed in your environment
- Upgrade AgentCore CLI to version 0.14.2 or later using your package manager or installation method (e.g., pip, npm, or the official installer)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-11393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-11393 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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