CVE-2026-85012
Shell command injection in CodeCatalyst blueprints before 0.3.156 via owner field.
Is CVE-2026-85012 being exploited?
Not confirmed. CVE-2026-85012 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 1.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-85012?
CVE-2026-85012 is rated High with a CVSS score of 8.5. 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-85012?
Yes. A fix has been recorded for CVE-2026-85012. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85012 affect?
CVE-2026-85012 affects @amazon-codecatalyst/blueprints.blueprint < 0.3.156, AWS CodeCatalyst blueprint resynthesis, Projects using crafted .ownership-file [local] merge strategy. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85012?
Upgrade to @amazon-codecatalyst/blueprints.blueprint >= 0.3.156 and validate .ownership-file entries.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A repo committer can execute arbitrary commands in the blueprint resynthesis environment via shell metacharacters in the owner field.
Patch when possible
- affected< 0.3.156
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.