CVE-2026-55553

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.7% (50th 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 — Patch released this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.7%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

urllib is an HTTP client for Node.js that supports authentication, redirects, timeouts, and other request features. Prior to 4.9.1 and 2.44.1, urllib follows redirects through followRedirect but reuses caller-supplied options across origins. In src/HttpClient.ts, #requestInternal recursively calls this.#requestInternal(nextUrl.href, options, requestContext), causing options.headers and auth or digestAuth values to be reused when the redirect target has a different scheme, host, or port. Authorization, Cookie, Proxy-Authorization, x-api-key, x-auth-token, and x-access-token can therefore be sent to an attacker-controlled redirected origin, exposing credentials intended for the original origin and potentially allowing reuse against the original partner API or related services. No user interaction is required. This issue is fixed in versions 2.44.1 and 4.9.1.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
50th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. 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 yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (7)

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

v4.9.1

Patch available: node-modules/urllib v4.9.1

https://github.com/node-modules/urllib/releases/tag/v4.9.1
GitHub release Patch Available

v2.44.1

Patch available: node-modules/urllib v2.44.1

https://github.com/node-modules/urllib/releases/tag/v2.44.1
GitHub commit Patch Available

commit 811a8d56e64e (node-modules/urllib)

Patch available: node-modules/urllib v4.9.1 (contains commit 811a8d56e64e)

https://github.com/node-modules/urllib/commit/811a8d56e64e540bf6a19bf8b3737692f05d5c46
GitHub commit Patch Available

commit 7c86c465883e (node-modules/urllib)

Patch available: node-modules/urllib v2.44.1 (contains commit 7c86c465883e)

https://github.com/node-modules/urllib/commit/7c86c465883ebd3dea5109c87d7bbe3b00960a16
GitHub pull request Patch Available

fix: do not forward credential headers on cross-origin redirect

Patch available: node-modules/urllib v2.44.1 (PR #813 merged 2026-06-13)

https://github.com/node-modules/urllib/pull/813
GitHub pull request Patch Available

fix: do not forward credential headers on cross-origin redirect

Patch available: node-modules/urllib v4.9.1 (PR #812 merged 2026-06-13)

https://github.com/node-modules/urllib/pull/812
GitHub advisoryMentions a patch (unverified)

Cross-origin redirects preserve credential-bearing request headers, leading to potential credential leakage · Advisory · node-modules/urllib · GitHub

https://github.com/node-modules/urllib/security/advisories/GHSA-hq3h-g68c-hp78

Vendor Advisories for CVE-2026-55553(7)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhdh/rhdh-hub-rhel9:17913114952026-10-08redhat
redhatrhdh/red-hat-developer-hub-backstage-plugin-scaffolder-backend-module-orchestrator:17912496402026-10-06redhat
redhatansible-automation-platform/automation-portal:17902549632026-09-28redhat
redhatansible-automation-platform/automation-portal:17902564052026-09-28redhat
redhatrhdh/rhdh-hub-rhel9:17895542852026-09-21redhat

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

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
urllib—
  • 3.0.0 up to 4.9.1: fixed in 4.9.1
  • every version up to 2.44.1: fixed in 2.44.1
—

Weakness Classification(3)

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

Data Freshness Timeline

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

Showing the most recent 100 of 124 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 24 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:39 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:17 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  9. 2026-10-10 12:01 UTCEG score recompute
  10. 2026-10-10 12:01 UTCVendor advisory
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  12. 2026-10-09 04:22 UTCEG score recompute
  13. 2026-10-09 04:22 UTCVendor advisory
  14. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  15. 2026-10-08 03:15 UTCEG score recompute
  16. 2026-10-08 03:15 UTCVendor advisory
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  18. 2026-10-07 06:49 UTCVendor advisory
  19. 2026-10-06 19:19 UTCEG score recompute
  20. 2026-10-06 19:19 UTCVendor advisory
  21. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  22. 2026-10-06 07:42 UTCVendor advisory
  23. 2026-10-05 18:56 UTCEG score recompute
  24. 2026-10-05 18:56 UTCVendor advisory
  25. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.7% · 49th percentile
Show 75 more
  1. 2026-10-05 07:22 UTCEG score recompute
  2. 2026-10-05 07:22 UTCVendor advisory
  3. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  4. 2026-10-04 19:49 UTCVendor advisory
  5. 2026-10-04 06:52 UTCVendor advisory
  6. 2026-10-03 19:22 UTCEG score recompute
  7. 2026-10-03 19:22 UTCVendor advisory
  8. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  9. 2026-10-03 06:35 UTCVendor advisory
  10. 2026-10-02 19:05 UTCEG score recompute
  11. 2026-10-02 19:05 UTCVendor advisory
  12. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  13. 2026-10-02 07:32 UTCVendor advisory
  14. 2026-10-01 20:03 UTCEG score recompute
  15. 2026-10-01 20:03 UTCVendor advisory
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  17. 2026-10-01 07:44 UTCVendor advisory
  18. 2026-09-30 20:14 UTCEG score recompute
  19. 2026-09-30 20:14 UTCVendor advisory
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  21. 2026-09-30 06:45 UTCEG score recompute
  22. 2026-09-30 06:45 UTCVendor advisory
  23. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  24. 2026-09-29 09:01 UTCEG score recompute
  25. 2026-09-29 09:01 UTCVendor advisory
  26. 2026-09-28 21:29 UTCEG score recompute
  27. 2026-09-28 21:29 UTCVendor advisory
  28. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  29. 2026-09-28 08:32 UTCVendor advisory
  30. 2026-09-27 21:02 UTCEG score recompute
  31. 2026-09-27 21:02 UTCVendor advisory
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  33. 2026-09-27 09:33 UTCVendor advisory
  34. 2026-09-26 22:03 UTCEG score recompute
  35. 2026-09-26 22:03 UTCVendor advisory
  36. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  37. 2026-09-25 06:27 UTCVendor advisory
  38. 2026-09-24 18:57 UTCEG score recompute
  39. 2026-09-24 18:57 UTCVendor advisory
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  41. 2026-09-24 07:27 UTCVendor advisory
  42. 2026-09-23 19:57 UTCEG score recompute
  43. 2026-09-23 19:57 UTCVendor advisory
  44. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  45. 2026-09-23 07:15 UTCVendor advisory
  46. 2026-09-22 19:46 UTCEG score recompute
  47. 2026-09-22 19:46 UTCVendor advisory
  48. 2026-09-22 08:16 UTCEG score recompute
  49. 2026-09-22 08:16 UTCVendor advisory
  50. 2026-09-21 20:47 UTCVendor advisory
  51. 2026-09-20 21:48 UTCEG score recompute
  52. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  53. 2026-09-19 22:48 UTCEG score recompute
  54. 2026-09-18 23:48 UTCEG score recompute
  55. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  56. 2026-09-18 00:43 UTCEG score recompute
  57. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  58. 2026-09-16 14:14 UTCEG score recompute
  59. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  60. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  61. 2026-09-15 03:43 UTCEG score recompute
  62. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  63. 2026-09-13 17:15 UTCEG score recompute
  64. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  65. 2026-09-12 18:16 UTCEG score recompute
  66. 2026-09-11 19:14 UTCEG score recompute
  67. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  68. 2026-09-10 20:14 UTCEG score recompute
  69. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  70. 2026-09-09 01:14 UTCEG score recompute
  71. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  72. 2026-09-07 22:35 UTCEG score recompute
  73. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.4% · 30th percentile
  74. 2026-09-06 23:32 UTCEG score recompute
  75. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.4% · 30th percentile

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-55553?
CVE-2026-55553 is a high-severity vulnerability; its CVE record was published on August 25, 2026. urllib is an HTTP client for Node.js that supports authentication, redirects, timeouts, and other request features. Prior to 4.9.1 and 2.44.1, urllib follows redirects through followRedirect but reuses caller-supplied options across origins. In src/HttpClient.ts, #requestInternal recursively calls…
When was the CVE record for CVE-2026-55553 published?
The CVE record for CVE-2026-55553 was published on August 25, 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 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55553 actively exploited?
CVE-2026-55553 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (50th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55553?
CVE-2026-55553 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55553?
A fix for CVE-2026-55553 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55553 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-55553

Explore →

Is Your Infrastructure Affected by CVE-2026-55553?

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

Book a Demo →Browse All CVEs