CVE-2026-130644

HIGHPre-NVD 8.18.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-11-18. A secondary CVSS source baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-128429 (ENISA EUVD) · GHSA-qvg5-6mh8-jpg9 (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A path traversal flaw was found in ansible-core. When installing a collection with ansible-galaxy collection install, the install destination directory is derived from the namespace and name fields declared inside the collection artifact's own metadata, which are not validated as well-formed collection identifiers or checked for path containment. A malicious collection artifact -- delivered as a local file, a remote URL, a source directory, a git repository, or as a dependency -- can use a crafted name value to redirect the install destination outside the configured collections path, causing ansible-galaxy to delete an existing directory writable by the invoking user and then write attacker-controlled files to that location.

CVSS v3
8.1
EG Score
8.1HIGHhigh confidence
EG Risk
37
EG Risk 37/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)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
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 (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-20). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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)60 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 partial (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

November 18, 2026

Last Modified

November 21, 2026

Advisory Details (2)

Auto-updated Nov 18, 2026
Patch available. Sources: redhat.
Red Hat

2574391 – (CVE-2026-130644) CVE-2026-130644 ansible-core: ansible-core: ansible-galaxy collection install path traversal via unvalidated artifact-derived collection name allows file writes and directory deletion outside the collections path

https://bugzilla.redhat.com/show_bug.cgi?id=2574391
Red HatMentions a patch (unverified)

CVE-2026-130644 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-130644

Vendor Advisories for CVE-2026-130644(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 11× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-11-21 03:28 UTCEchelonGraph re-scored
  3. 2026-11-21 03:28 UTCGHSA enrichmentGHSA-qvg5-6mh8-jpg9 · GitHub severity HIGH · GitHub CVSS 8.1
  4. 2026-11-21 02:48 UTCEchelonGraph re-scored
  5. 2026-11-21 02:47 UTCGHSA enrichmentGHSA-qvg5-6mh8-jpg9 · GitHub severity HIGH · GitHub CVSS 8.1
  6. 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-11-19 18:28 UTCEchelonGraph re-scored
  8. 2026-11-19 18:28 UTCGHSA enrichmentGHSA-qvg5-6mh8-jpg9 · GitHub severity HIGH · GitHub CVSS 8.1
  9. 2026-11-19 17:53 UTCEchelonGraph re-scored
  10. 2026-11-19 17:53 UTCGHSA enrichmentGHSA-qvg5-6mh8-jpg9 · GitHub severity HIGH · GitHub CVSS 8.1
  11. 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  12. 2026-11-18 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-11-18 06:46 UTCEchelonGraph re-scored
  14. 2026-11-18 06:46 UTCGHSA enrichmentGHSA-qvg5-6mh8-jpg9 · GitHub severity HIGH · GitHub CVSS 8.1
  15. 2026-11-18 05:03 UTCENISA EUVD ID recordedEUVD-2026-128429 · Source: ENISA EUVD
  16. 2026-11-18 04:28 UTCEchelonGraph re-scored
  17. 2026-11-18 03:43 UTCEchelonGraph re-scoredFirst assessed: 8.1 HIGH
  18. 2026-11-18 03:42 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-130644?
CVE-2026-130644 is a high-severity vulnerability; its CVE record was published on November 18, 2026. A path traversal flaw was found in ansible-core. When installing a collection with ansible-galaxy collection install, the install destination directory is derived from the namespace and name fields declared inside the collection artifact's own metadata, which are not validated as well-formed…
When was CVE-2026-130644 made public?
CVE-2026-130644 was made public on November 17, 2026: that is the date its CVE record's CNA, Red Hat, Inc., gives for when the vulnerability was made public. The CVE record itself was published on November 18, 2026. EchelonGraph's copy of the record carries a last-modified date of November 21, 2026; the record at its source may have been updated since.
Is CVE-2026-130644 actively exploited?
CVE-2026-130644 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-130644?
CVE-2026-130644 has a CVSS base score of 8.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-130644?
A fix for CVE-2026-130644 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-130644 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-130644

Explore →

Is Your Infrastructure Affected by CVE-2026-130644?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.