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.
CVE-2026-12171
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (12th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-92475 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
Upgrade to auto-changelog 2.6.1 or later (from the CVE record's solution, Harborist) — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 51EG Risk 51/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: Upgrade to auto-changelog 2.6.1 or later (from the CVE record's solution, Harborist). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 12th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
Upgrade to auto-changelog 2.6.1 or later (from the CVE record's solution, Harborist). Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 5, 2026
Last Modified
October 6, 2026
Advisory Details (2)
Auto-updated Oct 5, 2026commit 1d02a48a0a57 (cookpete/auto-changelog)
Fix landed in cookpete/auto-changelog commit 1d02a48a0a57 — awaiting tagged release
https://github.com/cookpete/auto-changelog/commit/1d02a48a0a57c69a3cd268aca375d64d50877c1aRCE via untrusted in-repo config (`handlebarsSetup` → `require()`) when run over attacker-controlled repo content (incl. CI on untrusted PRs) · Advisory · cookpete/auto-changelog · GitHub
https://github.com/cookpete/auto-changelog/security/advisories/GHSA-xpvr-2hvx-m8q4Weakness Classification(5)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 46× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-27 20:45 UTCEG score recompute
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-10-25 14:49 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-20 19:08 UTCEG score recompute
- 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-18 05:04 UTCEG score recompute
- 2026-10-17 18:52 UTCEG score recompute
- 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 21 moreShow fewer
- 2026-10-12 16:36 UTCEG score recompute
- 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-11 20:12 UTCEG score recompute
- 2026-10-11 18:24 UTCEG score recompute
- 2026-10-11 14:58 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-11 03:26 UTCEG score recompute
- 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-10 03:33 UTCEG score recompute
- 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-09 03:47 UTCEG score recompute
- 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-08 03:59 UTCEG score recompute
- 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-06 16:20 UTCEG score recompute
- 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 11th percentile
- 2026-10-05 20:26 UTCEG score recompute
- 2026-10-05 19:22 UTCEG score recompute
- 2026-10-05 17:28 UTCEG score recompute
- 2026-10-05 16:32 UTCEG score recomputeFirst assessed: 7.8 HIGH
- 2026-10-05 16:31 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-88 · CWE-829
Frequently asked(5)
What is CVE-2026-12171?
When was the CVE record for CVE-2026-12171 published?
Is CVE-2026-12171 actively exploited?
What is the CVSS score of CVE-2026-12171?
How do I remediate CVE-2026-12171?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-12171
Is Your Infrastructure Affected by CVE-2026-12171?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.