# CVE-2026-85012: OS command injection in the Amazon CodeCatalyst blueprints SDK

> An attacker with repository commit permissions can execute arbitrary commands in the blueprint resynthesis environment via shell metacharacters in a crafted ownership file.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026

## What is CVE-2026-85012?

CVE-2026-85012 is a high-severity command injection vulnerability in AWS @amazon-codecatalyst/blueprints.blueprint, published on 3 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper neutralization of special elements used in an OS command (CWE-78) in the blueprint resynthesis framework in Amazon Web Services codecatalyst-blueprints before 0.3.156 might allow a user with permission to commit to a repository in the project to execute arbitrary commands in the blueprint resynthesis environment via shell metacharacters in the owner field of a [local] merge strategy entry in a crafted .ownership-file.

Version 0.3.156 removes shell interpretation of the owner field, running the command directly rather than through a shell, and rejects values outside an allowlisted command form. This eliminates shell metacharacter command injection. To remediate this issue, users should upgrade to version 0.3.156 or later.

No action is required for use of the Amazon CodeCatalyst service. Resynthesis runs in an isolated per-project environment with scoped credentials, and the service applies server-side validation there that rejects [local] merge strategy commands outside a restricted allowlisted form, including for blueprint versions published before 0.3.156.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-85012?


## How do I fix CVE-2026-85012?

No fix has been published for CVE-2026-85012 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-85012 being exploited?

There is no known exploitation of CVE-2026-85012 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85012 and fix it if it is affected.

What it is: CVE-2026-85012 is a high-severity command injection vulnerability in AWS @amazon-codecatalyst/blueprints.blueprint, published on 3 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-85012 in the wild and no public exploit code.

Affected product: AWS @amazon-codecatalyst/blueprints.blueprint. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-85012/ (Markdown: https://insights.sbomify.com/CVE-2026-85012/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85012
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85012
- OSV: https://osv.dev/vulnerability/CVE-2026-85012

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85012/
Summaries are generated and may contain mistakes; the official description above is the record.