Skip to main content
VulnerabilityPublished

CVE-2026-12171: cookpete auto-changelog · Untrusted Functionality Inclusion

Affects cookpete auto-changelogSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.4 High : upgrade to 2.6.1 soon.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade cookpete auto-changelog to 2.6.1.

Affected software

ProductAffectedFixed in
cookpeteauto-changelogAffected
  • <2.6.1
Fixed in
  • 2.6.1
npmauto-changelogpkg:npm/auto-changelogOther threatsAffected
  • <2.6.1
Fixed in
  • 2.6.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Version 2.6.1 of auto-changelog treats in-repository configuration as untrusted and refuses to run if security-sensitive options are set, unless the --unsafe-config flag is explicitly passed. Users should upgrade to version 2.6.1 or later to mitigate this vulnerability. If upgrading is not immediately possible, avoid running auto-changelog on untrusted repositories or pull requests.

Description

auto-changelog versions before 2.6.1 merge configuration from inside the target repository, including untrusted files, into their options. This allows execution of attacker-controlled code via the handlebarsSetup option, loading malicious modules via plugins, git argument injection, arbitrary file writes, and outbound requests to attacker-chosen URLs. Version 2.6.1 mitigates this by treating in-repository configuration as untrusted and refusing to run if unsafe options are set unless overridden by a specific flag.

References

Community reviews

Loading reviews…