Skip to main content

Auto Changelog

1 CVEs product

Monthly

CVE-2026-12171 Oct 05, 16:25 HIGH PATCH This Week

Untrusted in-repo configuration in auto-changelog before 2.6.1 lets attacker-controlled repository content execute code with the privileges of the invoking user or CI job. Because versions prior to 2.6.1 merge the .auto-changelog file and the package.json 'auto-changelog' key into runtime options by default, options such as handlebarsSetup and plugins are passed to Node's require(), yielding code execution without the repository's dependencies ever being installed; under the same conditions output, appendGitLog/appendGitTag, remote and URL templates enable arbitrary file writes, git argument injection and outbound requests. Exploitation is not confirmed actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, but the attack requires the victim to invoke auto-changelog against a repository they do not control - most realistically a CI job checking out an untrusted pull-request head - so exposure is concentrated in that specific population rather than being broadly remotely reachable.

RCE Node.js Auto Changelog
NVD GitHub
CVSS 4.0
8.4
EPSS
0.2%
EPSS 0% CVSS 8.4
HIGH PATCH This Week

Untrusted in-repo configuration in auto-changelog before 2.6.1 lets attacker-controlled repository content execute code with the privileges of the invoking user or CI job. Because versions prior to 2.6.1 merge the .auto-changelog file and the package.json 'auto-changelog' key into runtime options by default, options such as handlebarsSetup and plugins are passed to Node's require(), yielding code execution without the repository's dependencies ever being installed; under the same conditions output, appendGitLog/appendGitTag, remote and URL templates enable arbitrary file writes, git argument injection and outbound requests. Exploitation is not confirmed actively exploited (no CISA KEV listing) and no public exploit code has been identified at time of analysis, but the attack requires the victim to invoke auto-changelog against a repository they do not control - most realistically a CI job checking out an untrusted pull-request head - so exposure is concentrated in that specific population rather than being broadly remotely reachable.

RCE Node.js Auto Changelog
NVD GitHub

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy