CVE-2026-63718

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-10-01. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
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.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') response smuggling vulnerability in Apache HTTP Server via mod_proxy_uwsgi and a crafted uwsgi response with Transfer-Encoding.

This issue affects Apache HTTP Server: from 2.4.30 through 2.4.68.

CVSS v3
7.5
EG Score
7.5HIGHhigh confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
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.3%
EPSS %ILE
22nd
KEV
Not listed

CISA SSVCTrack 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 none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 1, 2026

Last Modified

October 1, 2026

Advisory Details (1)

Auto-updated Oct 1, 2026
⚠️ Active exploitation confirmed. Patch available.
generic Patch Available🔴 Active Exploitation

Apache HTTP Server 2.4 vulnerabilities - The Apache HTTP Server Project

https://httpd.apache.org/security/vulnerabilities_24.html

Vendor Advisories for CVE-2026-63718(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhathttpd-main-2.4.69-1.hum12026-10-02redhat

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.

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 23× in last 7d / 23× 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-10-04 11:03 UTCVendor advisory
  2. 2026-10-04 11:03 UTCGHSA enrichment
  3. 2026-10-03 22:43 UTCEG score recompute
  4. 2026-10-03 22:43 UTCVendor advisory
  5. 2026-10-03 22:43 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 10:23 UTCVendor advisory
  8. 2026-10-03 10:23 UTCGHSA enrichment
  9. 2026-10-02 22:02 UTCEG score recompute
  10. 2026-10-02 22:02 UTCVendor advisory
  11. 2026-10-02 22:02 UTCGHSA enrichment
  12. 2026-10-02 17:56 UTCEPSS rescore
  13. 2026-10-02 09:41 UTCEG score recompute
  14. 2026-10-02 09:41 UTCGHSA enrichment
  15. 2026-10-01 21:20 UTCGHSA enrichment
  16. 2026-10-01 20:33 UTCGHSA enrichment
  17. 2026-10-01 20:29 UTCGHSA enrichment
  18. 2026-10-01 19:51 UTCEG score recompute▲ 7.50
  19. 2026-10-01 19:51 UTCGHSA enrichment
  20. 2026-10-01 19:50 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  21. 2026-10-01 17:27 UTCNVD update
  22. 2026-10-01 16:28 UTCEG score recompute
  23. 2026-10-01 16:25 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-63718?
CVE-2026-63718 is a high vulnerability published on October 1, 2026. Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') response smuggling vulnerability in Apache HTTP Server via modproxyuwsgi and a crafted uwsgi response with Transfer-Encoding. This issue affects Apache HTTP Server: from 2.4.30 through 2.4.68.
When was CVE-2026-63718 disclosed?
CVE-2026-63718 was first published on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-63718 actively exploited?
CVE-2026-63718 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (22nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-63718?
CVE-2026-63718 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-63718?
A fix for CVE-2026-63718 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-63718 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-63718

Explore →

Is Your Infrastructure Affected by CVE-2026-63718?

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