CVE-2026-101907

HIGHPre-NVD 7.07.0
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (40th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-88384 (ENISA EUVD) · GHSA-r4gj-5m52-g5wh (GitHub Security Advisories)Source: ENISA EUVD

7.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation follows the redirect instead of returning the redirect response unchanged. The redirected request can access internal responses or reach state-changing internal endpoints despite redirects being disabled. This issue is fixed in version 1.20.0.

CVSS v3
7.0
EG Score
7.0HIGHmedium confidence
EG Risk
48
EG Risk 48/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)
Severity70% × 45%
Impact severity (EG Severity): CVSS 7.0 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 or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (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.5%
EPSS %ILE
40th
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.0): severity, escalated by confirmed exploitation. This CVE's 7.0 is its impact severity (EG Severity), not escalated.

EG Severity
7.0 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.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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: 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation public PoC (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

September 28, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Sep 28, 2026
Patch available. Sources: github_commit, github_release, github, github_pr.
GitHub release Patch Available

v1.20.0

Patch available: axios/axios v1.20.0

https://github.com/axios/axios/releases/tag/v1.20.0
GitHub commit Patch Available

commit d19040bda7a8 (axios/axios)

Patch available: axios/axios v1.20.0 (contains commit d19040bda7a8)

https://github.com/axios/axios/commit/d19040bda7a8be2f82c3c6e1a5bc03917daee39a
GitHub pull request Patch Available

fix: harden runtime option handling

Patch available: axios/axios v1.20.0 (PR #11141 merged 2026-08-12)

https://github.com/axios/axios/pull/11141
GitHub advisoryMentions a patch (unverified)

maxRedirects: 0 is not enforced by the fetch adapter, allowing redirect-based SSRF · Advisory · axios/axios · GitHub

https://github.com/axios/axios/security/advisories/GHSA-r4gj-5m52-g5wh

Vendor Advisories for CVE-2026-101907(4)

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

Patch Availability(4)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatgrafana13-1-main-13.1.6-0.6.hum12026-10-02redhat
redhatgrafana12-4-main-12.4.12-0.3.hum12026-10-02redhat
redhatgrafana13-2-main-13.2.1-0.9.hum12026-10-02redhat
npmaxios @ 1.20.0 (fixes >= 1.17.0, < 1.20.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (12 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-axios1.11.0+dfsg-1 ... 1.8.4+dfsg-1 (11 versions)
  • every version up to 1.20.0-1: fixed in 1.20.0-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
axios—
  • 1.17.0 up to 1.20.0: fixed in 1.20.0
—

Weakness Classification(2)

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

Data Freshness Timeline

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

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 86 is merged into the row it repeats.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-r4gj-5m52-g5wh · GitHub severity HIGH
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-27 20:35 UTCEG score recompute
  9. 2026-10-27 20:35 UTCVendor advisory
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  13. 2026-10-25 14:57 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  18. 2026-10-20 19:16 UTCEG score recompute
  19. 2026-10-20 19:16 UTCVendor advisory
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  23. 2026-10-18 05:11 UTCEG score recompute
  24. 2026-10-17 19:54 UTCEG score recompute
  25. 2026-10-17 19:54 UTCVendor advisory
Show 60 more
  1. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  2. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  5. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-12 16:41 UTCEG score recompute
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-11 20:16 UTCEG score recompute
  9. 2026-10-11 18:49 UTCVendor advisory
  10. 2026-10-11 18:28 UTCEG score recompute
  11. 2026-10-11 15:02 UTCEG score recompute
  12. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-11 07:17 UTCEG score recompute
  14. 2026-10-11 07:17 UTCVendor advisory
  15. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  16. 2026-10-10 19:53 UTCVendor advisory
  17. 2026-10-10 08:27 UTCVendor advisory
  18. 2026-10-09 21:02 UTCEG score recompute
  19. 2026-10-09 21:02 UTCVendor advisory
  20. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  21. 2026-10-09 09:38 UTCVendor advisory
  22. 2026-10-08 22:10 UTCEG score recompute
  23. 2026-10-08 22:10 UTCVendor advisory
  24. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-08 10:45 UTCEG score recompute
  26. 2026-10-08 10:45 UTCVendor advisory
  27. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-10-07 23:09 UTCVendor advisory
  29. 2026-10-07 11:45 UTCVendor advisory
  30. 2026-10-07 00:20 UTCEG score recompute
  31. 2026-10-07 00:20 UTCVendor advisory
  32. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  33. 2026-10-06 12:55 UTCVendor advisory
  34. 2026-10-06 01:31 UTCVendor advisory
  35. 2026-10-06 01:30 UTCEG score recompute
  36. 2026-10-06 01:30 UTCVendor advisory
  37. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  38. 2026-10-05 13:53 UTCVendor advisory
  39. 2026-10-05 02:30 UTCEG score recompute
  40. 2026-10-05 02:30 UTCVendor advisory
  41. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  42. 2026-10-04 15:05 UTCVendor advisory
  43. 2026-10-04 03:38 UTCVendor advisory
  44. 2026-10-03 16:14 UTCEG score recompute
  45. 2026-10-03 16:14 UTCVendor advisory
  46. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  47. 2026-10-03 04:50 UTCVendor advisory
  48. 2026-10-02 17:26 UTCEG score recompute
  49. 2026-10-02 05:58 UTCEG score recompute
  50. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  51. 2026-09-30 17:09 UTCEG score recompute
  52. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-09-29 18:17 UTCEG score recompute
  54. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-09-29 06:53 UTCEG score recompute
  56. 2026-09-28 19:29 UTCEG score recompute
  57. 2026-09-28 18:52 UTCEG score recompute
  58. 2026-09-28 18:20 UTCEG score recompute
  59. 2026-09-28 17:47 UTCEG score recomputeFirst assessed: 7.0 HIGH
  60. 2026-09-28 17:46 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-101907?
CVE-2026-101907 is a high-severity vulnerability; its CVE record was published on September 28, 2026. Axios is a promise-based HTTP client for the browser and Node.js. From 1.17.0 until 1.20.0, the fetch adapter bypasses the maxRedirects: 0 redirect policy. An Axios request uses the fetch adapter with maxRedirects set to zero and receives a redirect response. The underlying fetch implementation…
When was the CVE record for CVE-2026-101907 published?
The CVE record for CVE-2026-101907 was published on September 28, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-101907 actively exploited?
CVE-2026-101907 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (40th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-101907?
CVE-2026-101907 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-101907?
A fix for CVE-2026-101907 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-101907 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-101907

Explore →

Is Your Infrastructure Affected by CVE-2026-101907?

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

Book a Demo →Browse All CVEs