CVE-2026-89091

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-95346 (ENISA EUVD) · GHSA-4jhw-j7jr-j479 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
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.5%CVSS: 8.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

A flaw was found in ansible-core. When installing a collection with ansible-galaxy collection install, the archive extractor validates member paths using lexical path normalisation (os.path.abspath) instead of resolving symbolic links (os.path.realpath), and it performs no containment check on symlink-typed directory members before creating them. A crafted collection tarball can chain symlink directory entries so that a subsequent file member is written outside the intended destination directory. This allows an attacker who can get a victim to install a malicious collection to overwrite arbitrary files with the privileges of the user running ansible-galaxy, leading to code execution on the control node. This is a bypass of the fix for CVE-2020-10691.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
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.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% 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 or medium mission impact; Track* at high (mission-essential systems).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 or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (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 8, 2026

Last Modified

October 9, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available. Sources: redhat.
Red Hat

Bug Access Denied

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

CVE-2026-89091 - 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-89091

Vendor Advisories for CVE-2026-89091(2)

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

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
ansible-core2.14.10-1 ... 2.22.0~beta2-1 (54 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
ansible-core2.19.0-1 ... 2.22.0~beta2-1 (19 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ansible-core2.19.0-1 ... 2.22.0~beta2-1 (16 versions)
  • every version on: no fix on record
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 55× 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.

  1. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  5. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-10-27 17:24 UTCEG score recompute
  8. 2026-10-27 17:24 UTCVendor advisory
  9. 2026-10-27 17:24 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-25 13:53 UTCEG score recompute
  14. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  19. 2026-10-19 17:04 UTCEG score recompute
  20. 2026-10-19 17:04 UTCVendor advisory
  21. 2026-10-19 17:04 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  23. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-18 03:02 UTCEG score recompute
  25. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
Show 30 more
  1. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  3. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  4. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-13 04:58 UTCEG score recompute
  6. 2026-10-13 04:58 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  7. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-12 14:49 UTCEG score recompute
  9. 2026-10-11 19:15 UTCEG score recompute
  10. 2026-10-11 19:01 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  11. 2026-10-11 16:32 UTCEG score recompute
  12. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  13. 2026-10-11 13:48 UTCEG score recompute
  14. 2026-10-11 06:33 UTCEG score recompute
  15. 2026-10-11 06:32 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  16. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  17. 2026-10-10 18:02 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  18. 2026-10-10 05:34 UTCEG score recompute
  19. 2026-10-10 05:34 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  20. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  21. 2026-10-09 17:05 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  22. 2026-10-09 16:34 UTCEG score recompute
  23. 2026-10-09 16:34 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  24. 2026-10-09 15:25 UTCEG score recompute
  25. 2026-10-09 15:25 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-10-09 11:17 UTCEG score recompute
  27. 2026-10-09 11:17 UTCGHSA enrichmentGHSA-4jhw-j7jr-j479 · GitHub severity HIGH · GitHub CVSS 8.8
  28. 2026-10-08 22:21 UTCEG score recompute
  29. 2026-10-08 21:53 UTCEG score recomputeFirst assessed: 8.8 HIGH
  30. 2026-10-08 21:53 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-89091?
CVE-2026-89091 is a high-severity vulnerability; its CVE record was published on October 8, 2026. A flaw was found in ansible-core. When installing a collection with ansible-galaxy collection install, the archive extractor validates member paths using lexical path normalisation (os.path.abspath) instead of resolving symbolic links (os.path.realpath), and it performs no containment check on…
When was CVE-2026-89091 made public?
CVE-2026-89091 was made public on September 25, 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 October 8, 2026. EchelonGraph's copy of the record carries a last-modified date of October 9, 2026; the record at its source may have been updated since.
Is CVE-2026-89091 actively exploited?
CVE-2026-89091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-89091?
CVE-2026-89091 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-89091?
A fix for CVE-2026-89091 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-89091 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-89091

Explore →

Is Your Infrastructure Affected by CVE-2026-89091?

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

Book a Demo →Browse All CVEs