CVE-2026-12171 Details
Description
auto-changelog before 2.6.1 merges configuration from inside the target repository (the .auto-changelog file and the auto-changelog key in package.json) into its options, and honors security-sensitive options from that untrusted source. The handlebarsSetup option is passed to require(), so running auto-changelog over attacker-controlled repository content (for example, in a CI workflow that checks out an untrusted pull request head, or locally on a forked or third-party repository) executes attacker-chosen code with the privileges of the invoking user or CI job, including access to workflow secrets, without the repository dependencies ever being installed. The plugins option similarly loads attacker-controlled modules from the repository. Under the same conditions, appendGitLog/appendGitTag allow git argument injection (e.g. --output= to write arbitrary files), output allows writing attacker-influenced content to arbitrary paths, and template causes an outbound request to an attacker-chosen URL. Version 2.6.1 treats in-repository configuration as untrusted and refuses to run when it sets these options, unless the new --unsafe-config flag is passed.
A vulnerability in auto-changelog versions prior to 2.6.1 allows for arbitrary code execution by merging untrusted configuration from within the target repository into its options. This includes the .auto-changelog file and the auto-changelog key in package.json. The issue arises because certain options, such as handlebarsSetup, are passed to require(), enabling the execution of attacker-controlled code with the privileges of the user or CI job running the command. This vulnerability is particularly concerning in CI workflows that handle untrusted pull requests, where the executed code can access sensitive workflow secrets. Additionally, the plugins option can be exploited in a similar manner by loading malicious modules from the repository.
Users are advised to update to auto-changelog version 2.7.0 or later, where this vulnerability has been addressed. In version 2.6.1, the in-repository configuration was treated as untrusted, and options that could load code or inject git arguments were disabled, unless the new --unsafe-config flag was used. However, version 2.7.0 removed the option to trust unverified repository configurations altogether.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Oct 5, 2026CISA-ADP
Assessed Oct 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/cookpete/auto-changelog/security/advisories/GHSA-xpvr-2hvx-m8q4 | CISA-ADP | AdvisoryRemedyVendor |
| https://github.com/cookpete/auto-changelog/commit/1d02a48a0a57c69a3cd268aca375d64d50877c1a | harborist | Source CodeVendor |
| https://github.com/cookpete/auto-changelog/security/advisories/GHSA-xpvr-2hvx-m8q4 | harborist | AdvisoryRemedyVendor |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | harborist |
| CWE-829 | Inclusion of Functionality from Untrusted Control Sphere | harborist |
| CWE-88 | Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') | harborist |
| CWE-918 | Server-Side Request Forgery (SSRF) | harborist |
| CWE-94 | Improper Control of Generation of Code ('Code Injection') | harborist |
Affected Products
| Product | Versions |
|---|---|
| auto-changelog | <= 2.6.0 (semver) |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 5, 2026 | CVE Modified | CISA-ADP |
| Oct 5, 2026 | New CVE Received | harborist |
Volerion