Web / CMS
Remote Code Execution
Remote Code Execution via Untrusted In-Repository Configuration in auto-changelog
auto-changelog before 2.6.1 trusts configuration stored inside the target repository, allowing attacker-controlled code to execute when the tool runs over untrusted repositories or pull requests.
.webp)
Overview
The auto-changelog package contains multiple security vulnerabilities affecting versions prior to 2.6.1. The issue arises because the application merges configuration supplied within the target repository, including .auto-changelog and the auto-changelog key in package.json, into its runtime options without adequately restricting security-sensitive settings.
An attacker who can supply malicious repository content may exploit these configuration options when a developer or automated CI/CD workflow processes the repository. The handlebarsSetup option can cause attacker-controlled code to be loaded through require(), while the plugins option can load attacker-controlled modules. Depending on the execution environment, this may result in arbitrary code execution with the privileges of the invoking process, potentially exposing CI/CD secrets and other sensitive information.
Additional security issues include Git argument injection through appendGitLog and appendGitTag, arbitrary file-writing risks through the output option, and server-side request forgery (SSRF) through the template option.
The attack is particularly relevant to development environments and CI/CD pipelines that process untrusted pull requests or third-party repositories.
Version 2.6.1 introduces protections that treat repository-provided configuration as untrusted and prevent the affected security-sensitive options from being used unless the --unsafe-config flag is explicitly supplied.
Affected Product: auto-changelog (npm) by cookpete Affected Versions: All versions before 2.6.1 Fixed Version: 2.6.1 Remediation: Upgrade to auto-changelog 2.6.1 or later. Avoid processing untrusted repositories using vulnerable versions, and do not enable --unsafe-config when handling untrusted repository content.
Vulnerability details
What an attacker can do
Successful exploitation may result in: Arbitrary Code Execution: Untrusted handlebarsSetup or plugins configuration can load and run attacker-controlled code with the privileges of the developer or CI job. CI/CD Secret Exposure: A workflow processing an untrusted pull request may expose workflow secrets, tokens and other resources accessible to the job. Git Argument Injection: appendGitLog and appendGitTag can be abused to inject Git arguments, for example to write output to unintended locations. Arbitrary File Writes: The output option allows path traversal, letting attacker-influenced content be written outside the intended directory. Server-Side Request Forgery (SSRF): The template option can trigger outbound requests to an attacker-controlled destination.
Disclosure timeline
2026-10-05 - CVE-2026-12171 published.
2026-10-05 - Public vulnerability advisory (GHSA-xpvr-2hvx-m8q4) released.
Fixed in auto-changelog 2.6.1.
References
NVD: CVE-2026-12171 (https://nvd.nist.gov/vuln/detail/CVE-2026-12171)
GitHub Security Advisory GHSA-xpvr-2hvx-m8q4 (https://github.com/cookpete/auto-changelog/security/advisories/GHSA-xpvr-2hvx-m8q4)
Security fix commit (https://github.com/cookpete/auto-changelog/commit/1d02a48a0a57c69a3cd268aca375d64d50877c1a)
2026-10-05 (NVD record)
Credits
Omkar Dutta – Payatu

















