CVE-2026-62987

MEDIUMPre-NVD 5.85.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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, secondary
Trending — 3 sources updated this weekElevated
5.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.8Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. From 1.6.6 until 1.7.2, the CVE-2025-48865 fix in proxy/http_headers.go uses protectHeaders for a hardcoded set of forwarded headers but omits the operator-configured ClientIPHeader, TLSHeader, and RequestID names. In proxy/http_proxy.go, HTTPProxy.ServeHTTP calls addHeaders to set these trust headers before Go ReverseProxy processes the inbound Connection header, allowing an unauthenticated client to name and remove the configured headers before the request reaches the backend. Deployments that enable the corresponding proxy.header options can therefore lose client-IP, TLS-termination, or request-correlation signals used by backend authorization and auditing; the options are empty by default, and the hardcoded protected forwarded headers are unaffected. This issue is fixed in version 1.7.2.

CVSS v3
5.8
EG Score
5.8(medium)
EG Risk
57(Attend)
EG Risk 57/100SSVC: Attend

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
Severity58% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 21, 2026

Last Modified

September 24, 2026

Advisory Details (3)

Auto-updated Sep 21, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_commit, github_release.
github_release Patch Available

v1.7.2

Patch available: fabiolb/fabio v1.7.2

https://github.com/fabiolb/fabio/releases/tag/v1.7.2
github_commit

commit 240526a80040 (fabiolb/fabio)

Fix landed in fabiolb/fabio commit 240526a80040 — awaiting tagged release

https://github.com/fabiolb/fabio/commit/240526a8004077edad4fb96d25b382bfc3901357
github Patch Available🟡 PoC Available

Incomplete fix for CVE-2025-48865: operator-configured trust headers (clientip/tls/requestid) still strippable via the Connection header · Advisory · fabiolb/fabio · GitHub

Affected: v1.6.6). This is an incomplete-fix sibling - the same hop-by-hop stripping primit

https://github.com/fabiolb/fabio/security/advisories/GHSA-fq95-v8xc-jm3v

Vendor Advisories for CVE-2026-62987(1)

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

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/fabiolb/fabio—1.7.2—

Weakness Classification(2)

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

Data Freshness Timeline

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

  1. 2026-09-24 21:38 UTCEG score recompute
  2. 2026-09-24 13:30 UTCEG score recompute
  3. 2026-09-23 17:54 UTCEPSS rescore
  4. 2026-09-22 17:40 UTCEG score recompute
  5. 2026-09-21 19:29 UTCEG score recompute
  6. 2026-09-21 18:30 UTCEG score recompute
  7. 2026-09-21 17:25 UTCEG score recompute
  8. 2026-09-21 16:25 UTCEG score recompute
  9. 2026-09-21 16:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-62987?
CVE-2026-62987 is a medium vulnerability published on September 21, 2026. Fabio is an HTTP(S) and TCP router for deploying applications managed by consul. From 1.6.6 until 1.7.2, the CVE-2025-48865 fix in proxy/httpheaders.go uses protectHeaders for a hardcoded set of forwarded headers but omits the operator-configured ClientIPHeader, TLSHeader, and RequestID names. In…
When was CVE-2026-62987 disclosed?
CVE-2026-62987 was first published in the National Vulnerability Database on September 21, 2026, with the most recent update on September 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-62987 actively exploited?
CVE-2026-62987 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.1% of all scored CVEs.
What is the CVSS score of CVE-2026-62987?
CVE-2026-62987 has a CVSS v3 base score of 5.8 (NVD).
How do I remediate CVE-2026-62987?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62987, 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-62987

Explore →

Is Your Infrastructure Affected by CVE-2026-62987?

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