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.1%, top 82% 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.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

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.5(medium)
EPSS
38.5%
KEV
Not listed

Published

April 21, 2026

Last Modified

July 10, 2026

Advisory Details (1)

Auto-updated Jun 9, 2026
Patch available. Sources: github.
github Patch Available

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

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmulticluster-engine/console-mce-rhel9:17809108882026-06-11redhat
redhatrhacm2/console-rhel9:17806008232026-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
redhatcryostat/cryostat-openshift-console-plugin-rhel9:4.2.0-92026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17793715942026-05-26redhat
redhatadvanced-cluster-security/rhacs-main-rhel8:17792930132026-05-26redhat
redhatquay/quay-rhel8:17796893922026-05-26redhat
redhatrhoai/odh-mod-arch-model-registry-rhel9:17786669872026-05-20redhat
redhatquay/quay-rhel9:17792040862026-05-19redhat
redhatmulticluster-engine/console-mce-rhel9:17785326102026-05-19redhat
redhatmulticluster-engine/console-mce-rhel9:17783838632026-05-14redhat
redhatmulticluster-engine/console-mce-rhel9:17785113482026-05-14redhat
redhatnetwork-observability/network-observability-console-plugin-rhel9:17785104612026-05-13redhat
redhatopenshift-service-mesh/kiali-rhel9:17781640422026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel9:17781639092026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel9:17781639862026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel9:17781642082026-05-12redhat
redhatopenshift-service-mesh/kiali-rhel8:17781913782026-05-12redhat
redhatdiscovery/discovery-ui-rhel9:17781567562026-05-07redhat
redhatrhdh/rhdh-hub-rhel9:17779032622026-05-05redhat

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 rangeFixed inDependents
follow-redirects1.16.0

Weakness Classification(2)

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

Additional Vendor Advisories

(15)

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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 118 total refreshes for this CVE.

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

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 in the National Vulnerability Database on April 21, 2026, with the most recent update on July 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 38.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40895, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.