CVE-2025-48865

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

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

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2025-05-29. NVD baseline CVSS 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-16398 (ENISA EUVD) · GHSA-q7p4-7xjv-j3wf (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
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.5%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. Prior to version 1.6.6, Fabio allows clients to remove X-Forwarded headers (except X-Forwarded-For) due to a vulnerability in how it processes hop-by-hop headers. Fabio adds HTTP headers like X-Forwarded-Host and X-Forwarded-Port when routing requests to backend applications. Since the receiving application should trust these headers, allowing HTTP clients to remove or modify them creates potential security vulnerabilities. Some of these custom headers can be removed and, in certain cases, manipulated. The attack relies on the behavior that headers can be defined as hop-by-hop via the HTTP Connection header. This issue has been patched in version 1.6.6.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
72
EG Risk 72/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)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
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 (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-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-11-01). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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, Track* at medium and Attend at high mission impact.

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 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)3 days if the affected system is publicly exposed; 60 days if it is not.

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

May 30, 2025

Last Modified

June 4, 2025

Advisory Details (3)

Auto-updated Aug 2, 2026
Patch available. Sources: github_commit, github_release, github.
GitHub advisoryMentions a patch (unverified)

HTTP clients can manipulate custom headers added by Fabio · Advisory · fabiolb/fabio · GitHub

https://github.com/fabiolb/fabio/security/advisories/GHSA-q7p4-7xjv-j3wf
GitHub release Patch Available

v1.6.6

Patch available: fabiolb/fabio v1.6.6

https://github.com/fabiolb/fabio/releases/tag/v1.6.6
GitHub commit

commit fdaf1e966162 (fabiolb/fabio)

Fix landed in fabiolb/fabio commit fdaf1e966162 — awaiting tagged release

https://github.com/fabiolb/fabio/commit/fdaf1e966162e9dd3b347ffdd0647b39dc71a1a3

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/fabiolb/fabio @ 1.6.6 (fixes <= 1.6.5)—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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/fabiolb/fabio—
  • every version up to 1.6.6: fixed in 1.6.6
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 56× 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 96 of 220 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/fabiolb/fabio

Frequently asked(5)

What is CVE-2025-48865?
CVE-2025-48865 is a critical-severity vulnerability; its CVE record was published on May 30, 2025. Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. Prior to version 1.6.6, Fabio allows clients to remove X-Forwarded headers (except X-Forwarded-For) due to a vulnerability in how it processes hop-by-hop headers. Fabio adds HTTP headers like X-Forwarded-Host and…
When was the CVE record for CVE-2025-48865 published?
The CVE record for CVE-2025-48865 was published on May 30, 2025. 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 June 4, 2025; the record at its source may have been updated since.
Is CVE-2025-48865 actively exploited?
CVE-2025-48865 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-2025-48865?
CVE-2025-48865 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2025-48865?
A fix for CVE-2025-48865 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-48865

Explore →

Is Your Infrastructure Affected by CVE-2025-48865?

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

Book a Demo →Browse All CVEs