Local command execution via unescaped infile path
Published Jul 23, 2026 · Updated Jul 23, 2026
OS command injection in @release-it/conventional-changelog 11.0.0 and 11.0.1 allows local users to execute commands through infile. The writeChangelog function in index.js interpolates the infile value directly into git add ${infile} through a shell without escaping metacharacters. Exploitation requires control of release configuration or invocation, an absent changelog file, and execution of the release workflow; commands run with the release process's privileges.
Summary
What happened
OS command injection in @release-it/conventional-changelog 11.0.0 and 11.0.1 allows local users to execute commands through infile. The writeChangelog function in index.js interpolates the infile value directly into git add ${infile} through a shell without escaping metacharacters. Exploitation requires control of release configuration or invocation, an absent changelog file, and execution of the release workflow; commands run with the release process's privileges.
The record
- CVE
- CVE-2026-16735
- Published
- Jul 23, 2026
- Updated
- Jul 23, 2026
- Vendor
- release-it
- Product
- @release-it/conventional-changelog
- Classifications
- CWE-78, CWE-77, T1059.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 2026CVE publishedPublication date reported by the CVE source.
- Jul 23, 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=11.0.0
- Affected versionversion=11.0.1
What conditions does exploitation require?
What is affected?
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
- GitHub issue #149 proof of conceptproof of concept · demonstrated
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