Command execution via unsanitized ownership-file owner
Published Sep 3, 2026 · Updated Sep 3, 2026
OS command injection in @amazon-codecatalyst/blueprints.blueprint before 0.3.156 allows remote authenticated users to execute commands. During resynthesis, the framework passes a local merge entry's owner field from .ownership-file to an OS command through a shell without validation. Repository commit permission is required, and commands run with the resynthesis environment's privileges; CodeCatalyst service validation blocks this path.
Summary
What happened
OS command injection in @amazon-codecatalyst/blueprints.blueprint before 0.3.156 allows remote authenticated users to execute commands. During resynthesis, the framework passes a local merge entry's owner field from .ownership-file to an OS command through a shell without validation. Repository commit permission is required, and commands run with the resynthesis environment's privileges; CodeCatalyst service validation blocks this path.
The record
- CVE
- CVE-2026-85012
- Published
- Sep 3, 2026
- Updated
- Sep 3, 2026
- Vendor
- Amazon Web Services
- Product
- @amazon-codecatalyst/blueprints.blueprint
- Classifications
- CWE-78, T1059
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 3, 2026CVE publishedPublication date reported by the CVE source.
- Sep 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.3.156
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo