CVE-2026-40895

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

follow-redirects is an open source, drop-in replacement for Node's http and https modules that automatically follows redirects. Prior to 1.16.0, when an HTTP request follows a cross-domain redirect (301/302/307/308), follow-redirects only strips authorization, proxy-authorization, and cookie headers (matched by regex at index.js). Any custom authentication header (e.g., X-API-Key, X-Auth-Token, Api-Key, Token) is forwarded verbatim to the redirect target. This vulnerability is fixed in 1.16.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/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
Severity75% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

Published

April 21, 2026

Last Modified

September 10, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: github.
githubMentions a patch (unverified)

Custom Authentication Headers Leaked to Cross-Domain Redirect Targets · Advisory · follow-redirects/follow-redirects · GitHub

https://github.com/follow-redirects/follow-redirects/security/advisories/GHSA-r4q5-vmmm-2653

Vendor Advisories for CVE-2026-40895(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-codeserver-datascience-cpu-py312-rhel9:17878015272026-09-08redhat
redhatopenshift4/ose-console-rhel9:17848033442026-08-06redhat
redhatopenshift4/ose-console-rhel9:17852785692026-08-05redhat
redhatmta/mta-ui-rhel9:17851690132026-08-04redhat
redhatopenshift4/ose-console-rhel9:17846348772026-07-29redhat
redhatopenshift4/ose-console-rhel9:17847310142026-07-28redhat
redhatopenshift4/ose-console-rhel9:17847137622026-07-28redhat
redhatopenshift4/ose-console-rhel9:17841253292026-07-21redhat
redhatrhmtc/openshift-migration-ui-rhel8:17836905322026-07-20redhat
redhatrhacm2/console-rhel9:17834517292026-07-08redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17817084342026-06-24redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17817319142026-06-23redhat
redhatopenshift4/ose-monitoring-plugin-rhel9:17816950122026-06-23redhat
redhatcluster-observability-operator/distributed-tracing-console-plugin-rhel9:17811163922026-06-15redhat
redhatrhacm2/console-rhel9:17806008232026-06-11redhat
redhatmulticluster-engine/console-mce-rhel9:17809108882026-06-11redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17804671472026-06-10redhat
redhatquay/quay-rhel8:17808913952026-06-09redhat
redhatansible-automation-platform-25/lightspeed-rhel8:17800829492026-06-09redhat
redhatrhacm2/console-rhel9:17808767342026-06-08redhat
redhatmulticluster-engine/console-mce-rhel9:17809175312026-06-08redhat
redhatquay/quay-rhel8:17798114732026-06-04redhat
redhatquay/quay-rhel8:17798222612026-06-03redhat
redhatquay/quay-rhel8:17798114122026-06-02redhat
redhatquay/quay-rhel9:17799222052026-06-02redhat
redhatdevspaces/pluginregistry-rhel9:17793594232026-05-28redhat
redhatrhdh/rhdh-hub-rhel9:17798415862026-05-27redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17793715942026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17792930132026-05-26redhat

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

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-follow-redirects1.13.1-1 ... 1.16.0+~1.14.4-2 (20 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-follow-redirects1.15.11+~1.14.4-1 ... 1.16.0+~1.14.4-2 (9 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-follow-redirects1.15.11+~1.14.4-1, 1.15.11+~1.14.4-2, 1.15.9+~1.14.4-1, 1.16.0+~1.14.4-1, 1.16.0+~1.14.4-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-follow-redirects1.15.11+~1.14.4-1, 1.15.11+~1.14.4-2, 1.15.9+~1.14.4-1
  • every version up to 1.16.0+~1.14.4-1: fixed in 1.16.0+~1.14.4-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
follow-redirects—
  • every version up to 1.16.0: fixed in 1.16.0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(24)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 276 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-40895?
CVE-2026-40895 is a high vulnerability published on April 21, 2026. follow-redirects is an open source, drop-in replacement for Node's http and https modules that automatically follows redirects. Prior to 1.16.0, when an HTTP request follows a cross-domain redirect (301/302/307/308), follow-redirects only strips authorization, proxy-authorization, and cookie…
When was CVE-2026-40895 disclosed?
CVE-2026-40895 was first published on April 21, 2026, with the most recent update on September 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40895 actively exploited?
CVE-2026-40895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40895?
CVE-2026-40895 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-40895?
A fix for CVE-2026-40895 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40895 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-40895

Explore →

Is Your Infrastructure Affected by CVE-2026-40895?

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

Book a Demo →Browse All CVEs