CVE-2023-45288

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 92% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated

Also known asEUVD-2024-1094 (ENISA EUVD) · GHSA-4v7x-pqxf-cx7m (GitHub Security Advisories)Source: ENISA EUVD

9.0EG
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).
  • High exploitation likelihood — EPSS 92%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 92%CVSS: 7.5Exploit: Public PoCExposed services: Not assessed

A fix is available — apply it.

An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for an attacker to send. The fix sets a limit on the amount of excess header frames we will process before closing a connection.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
86
EG Risk 86/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)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation92% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
92%
EPSS %ILE
99th
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.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
92% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 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 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). 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)14 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 partial (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

April 4, 2024

Last Modified

April 15, 2026

Advisory Details (8)

Auto-updated Oct 13, 2026
Patch available.
Web page

oss-security - Go 1.22.2 and 1.21.9 (CVE-2023-45288 HTTP/2 CONTINUATION issue)

http://www.openwall.com/lists/oss-security/2024/04/05/4
Web page

oss-security - CERT/CC VU#421644: HTTP/2 CONTINUATION frames can be utilized for DoS attacks

http://www.openwall.com/lists/oss-security/2024/04/03/16
Web page

GO-2024-2687 - Go Packages

https://pkg.go.dev/vuln/GO-2024-2687
Web page

[SECURITY] Fedora 40 Update: kubernetes-1.29.4-1.fc40 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/QRYFHIQ6XRKRYBI2F5UESH67BJBQXUPT/
Web page

net/http, x/net/http2: close connections when receiving too many headers (CVE-2023-45288) · Issue #65051 · golang/go · GitHub

https://go.dev/issue/65051

Patch Availability(33)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17918998772026-10-15redhat
redhatweb-terminal/web-terminal-tooling-rhel9:1.11-82025-09-15redhat
redhatopenshift-gitops-1/must-gather-rhel8:v1.14.4-12025-05-28redhat
redhatopenshift-gitops-1/must-gather-rhel8:v1.15.2-42025-05-15redhat
redhatrhceph/snmp-notifier-rhel9:1.2.1-982025-04-28redhat
redhatrhcos-418.94.202502100215-02025-02-25redhat
redhatrhceph/snmp-notifier-rhel9:1.2.1-922025-02-24redhat
redhatrhceph/snmp-notifier-rhel8:1.2.1-882025-02-13redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:v4.12.0-202501270458.p0.gb0407e3.assembly.stream.el82025-02-06redhat
redhatcert-manager/jetstack-cert-manager-rhel9:v1.15.42025-01-21redhat
redhatopenshift4/ose-kube-rbac-proxy:v4.12.0-202410182029.p0.gc69fae7.assembly.stream.el82024-11-07redhat
redhatopenshift4/ose-kube-rbac-proxy:v4.13.0-202410190100.p0.gf35f954.assembly.stream.el82024-11-06redhat
redhatopenshift4/ose-kube-rbac-proxy:v4.15.0-202410230304.p0.g9308e7f.assembly.stream.el82024-10-31redhat
redhatopenshift4/ose-kube-rbac-proxy:v4.14.0-202410091239.p0.gb8b8259.assembly.stream.el82024-10-23redhat
redhatrhmtc/openshift-migration-controller-rhel8:v1.8.4-222024-09-26redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:v4.13.0-202409020337.p0.g3a7ac1b.assembly.stream.el82024-09-25redhat
redhatopenshift4/ose-oauth-apiserver-rhel8:v4.12.0-202409101431.p0.g1053f14.assembly.stream.el82024-09-18redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:v4.14.0-202408260910.p0.g433fd32.assembly.stream.el82024-09-11redhat
redhatopenshift4/ose-oauth-apiserver-rhel8:v4.13.0-202408281337.p0.g6a59716.assembly.stream.el82024-09-04redhat
redhatopenshift4/ose-cluster-baremetal-operator-rhel9:v4.16.0-202408262007.p0.g8f65ef6.assembly.stream.el92024-09-03redhat
redhatopenshift-builds-operator-container2024-09-03redhat
redhatopenshift4/ose-oauth-apiserver-rhel8:v4.14.0-202407250240.p0.ge1cd9d0.assembly.stream.el82024-08-07redhat
redhatopenshift-builds/openshift-builds-rhel9-operator:1.1.02024-08-05redhat
redhatoadp/oadp-rhel9-operator:1.3.3-122024-08-01redhat
redhatgit-lfs-0:3.2.0-1.el9_22024-07-31redhat
redhatgit-lfs-0:2.11.0-2.el8_4.22024-07-31redhat
redhatopenshift4/ose-operator-registry:v4.12.0-202407151105.p0.g3327393.assembly.stream.el82024-07-25redhat
redhatopenshift4/ose-openshift-apiserver-rhel9:v4.15.0-202407151306.p0.g08f4c42.assembly.stream.el92024-07-25redhat
redhatdevspaces/devspaces-rhel8-operator:3.15-102024-07-18redhat
redhatopenshift4/ose-operator-registry:v4.13.0-202407081338.p0.gd8cfe86.assembly.stream.el82024-07-17redhat
gogolang.org/x/net @ 0.23.0 (fixes < 0.23.0)—ghsa
gonet/http @ 1.21.9 (fixes < 1.21.9)—ghsa
gonet/http @ 1.22.2 (fixes >= 1.22.0-0, < 1.22.2)—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

(10 across 5 ecosystems)
Go(4)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/net—
  • every version up to 0.23.0: fixed in 0.23.0
—
golang.org/x/net/http2—
  • every version up to 0.23.0: fixed in 0.23.0
—
net/http—
  • every version up to 1.21.9: fixed in 1.21.9
  • 1.22.0-0 up to 1.22.2: fixed in 1.22.2
—
stdlib—
  • every version up to 1.21.9: fixed in 1.21.9
  • 1.22.0-0 up to 1.22.2: fixed in 1.22.2
—
Debian:11(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.151.15.15-1 ... 1.15.9-6 (10 versions)
  • every version on: no fix on record
—
golang-golang-x-net1:0.0+git20210119.5f4716e+dfsg-4 ... 1:0.7.0+dfsg-1 (40 versions)
  • every version on: no fix on record
—
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
golang-1.191.19.10-1 ... 1.19.9-1 (12 versions)
  • every version on: no fix on record
—
golang-golang-x-net1:0.10.0-1 ... 1:0.7.0+dfsg-1 (27 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-net—
  • every version up to 1:0.23.0+dfsg-: fixed in 1:0.23.0+dfsg-
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-golang-x-net—
  • every version up to 1:0.23.0+dfsg-: fixed in 1:0.23.0+dfsg-
—

Weakness Classification(1)

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 17× in last 7d / 52× 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 89 of 148 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. 11 repeat rows among the latest 100 are merged into the row they repeat. The 59 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 15:04 UTCVendor advisory
  2. 2026-11-01 15:04 UTCGHSA enrichmentGHSA-4v7x-pqxf-cx7m · GitHub severity MODERATE · GitHub CVSS 5.3
  3. 2026-11-01 08:18 UTCGHSA enrichmentGHSA-4v7x-pqxf-cx7m · GitHub severity MODERATE · GitHub CVSS 5.3
  4. 2026-11-01 08:18 UTCEG score recompute
  5. 2026-10-31 13:02 UTCEG score recompute
  6. 2026-10-31 13:02 UTCVendor advisory
  7. 2026-10-30 10:58 UTCEG score recompute
  8. 2026-10-30 10:58 UTCVendor advisory
  9. 2026-10-29 16:30 UTCEPSS rescoreEPSS 92% · 99th percentile
  10. 2026-10-29 08:56 UTCEG score recompute
  11. 2026-10-29 08:56 UTCVendor advisory
  12. 2026-10-28 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
  13. 2026-10-28 06:48 UTCEG score recompute
  14. 2026-10-28 06:48 UTCVendor advisory
  15. 2026-10-27 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
  16. 2026-10-27 04:45 UTCEG score recompute
  17. 2026-10-27 04:45 UTCVendor advisory
  18. 2026-10-25 22:19 UTCVendor advisory
  19. 2026-10-25 17:33 UTCEG score recompute
  20. 2026-10-25 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
  21. 2026-10-24 20:15 UTCEG score recompute
  22. 2026-10-24 20:15 UTCVendor advisory
  23. 2026-10-23 18:12 UTCEG score recompute
  24. 2026-10-23 18:12 UTCVendor advisory
  25. 2026-10-22 16:09 UTCEG score recompute
Show 64 more
  1. 2026-10-22 16:09 UTCVendor advisory
  2. 2026-10-21 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
  3. 2026-10-21 13:32 UTCEG score recompute
  4. 2026-10-21 13:32 UTCVendor advisory
  5. 2026-10-20 16:30 UTCEPSS rescoreEPSS 92% · 99th percentile
  6. 2026-10-20 11:30 UTCEG score recompute
  7. 2026-10-20 11:30 UTCVendor advisory
  8. 2026-10-19 09:26 UTCEG score recompute
  9. 2026-10-19 09:26 UTCVendor advisory
  10. 2026-10-18 16:29 UTCEPSS rescoreEPSS 92% · 99th percentile
  11. 2026-10-18 07:08 UTCEG score recompute
  12. 2026-10-18 07:08 UTCVendor advisory
  13. 2026-10-17 16:30 UTCEPSS rescoreEPSS 92% · 99th percentile
  14. 2026-10-17 05:02 UTCEG score recompute
  15. 2026-10-17 05:02 UTCVendor advisory
  16. 2026-10-16 16:36 UTCEPSS rescoreEPSS 92% · 99th percentile
  17. 2026-10-16 02:59 UTCEG score recompute
  18. 2026-10-16 02:59 UTCVendor advisory
  19. 2026-10-14 23:02 UTCEG score recompute
  20. 2026-10-14 23:02 UTCVendor advisory
  21. 2026-10-14 16:30 UTCEPSS rescoreEPSS 92% · 99th percentile
  22. 2026-10-13 18:43 UTCEG score recompute
  23. 2026-10-13 18:43 UTCVendor advisory
  24. 2026-10-12 16:39 UTCEG score recompute
  25. 2026-10-12 16:39 UTCVendor advisory
  26. 2026-10-11 21:43 UTCEG score recompute
  27. 2026-10-08 17:06 UTCEPSS rescoreEPSS 92% · 99th percentile
  28. 2026-09-30 19:14 UTCOSV refresh
  29. 2026-09-30 16:31 UTCEG score recompute
  30. 2026-09-30 15:01 UTCEPSS rescoreEPSS 92% · 99th percentile
  31. 2026-09-27 13:42 UTCEPSS rescoreEPSS 92% · 99th percentile
  32. 2026-09-26 15:56 UTCEPSS rescoreEPSS 92% · 99th percentile
  33. 2026-09-24 14:01 UTCEPSS rescoreEPSS 92% · 99th percentile
  34. 2026-09-23 13:46 UTCEPSS rescoreEPSS 92% · 99th percentile
  35. 2026-09-18 19:25 UTCEPSS rescoreEPSS 92% · 99th percentile
  36. 2026-09-16 05:11 UTCEPSS rescoreEPSS 92% · 99th percentile
  37. 2026-09-12 02:10 UTCOSV refresh
  38. 2026-09-11 14:50 UTCEPSS rescoreEPSS 92% · 99th percentile
  39. 2026-09-06 13:45 UTCEPSS rescoreEPSS 92% · 99th percentile
  40. 2026-09-05 15:26 UTCEPSS rescoreEPSS 92% · 99th percentile
  41. 2026-08-30 19:15 UTCEPSS rescoreEPSS 92% · 99th percentile
  42. 2026-08-28 21:39 UTCEPSS rescoreEPSS 92% · 99th percentile
  43. 2026-08-26 14:43 UTCEPSS rescoreEPSS 92% · 99th percentile
  44. 2026-08-25 13:46 UTCEPSS rescoreEPSS 92% · 99th percentile
  45. 2026-08-24 07:57 UTCOSV refresh
  46. 2026-08-15 01:28 UTCEPSS rescoreEPSS 92% · 99th percentile
  47. 2026-08-08 16:35 UTCEPSS rescoreEPSS 92% · 99th percentile
  48. 2026-08-08 04:19 UTCOSV refresh
  49. 2026-08-06 13:45 UTCEPSS rescoreEPSS 92% · 99th percentile
  50. 2026-07-30 16:26 UTCEPSS rescoreEPSS 92% · 99th percentile
  51. 2026-07-24 14:16 UTCEPSS rescoreEPSS 92% · 99th percentile
  52. 2026-07-23 14:16 UTCEPSS rescoreEPSS 92% · 99th percentile
  53. 2026-07-23 02:27 UTCEG score recompute
  54. 2026-07-22 21:22 UTCEG score recompute▲ 1.50
  55. 2026-07-22 21:22 UTCVendor advisory
  56. 2026-07-22 14:06 UTCEPSS rescoreEPSS 92% · 99th percentile
  57. 2026-07-21 15:23 UTCEPSS rescoreEPSS 92% · 99th percentile
  58. 2026-07-20 17:06 UTCEPSS rescoreEPSS 92% · 99th percentile
  59. 2026-07-18 10:03 UTCEPSS rescoreEPSS 92% · 99th percentile
  60. 2026-07-16 17:01 UTCEPSS rescoreEPSS 92% · 99th percentile
  61. 2026-07-11 08:22 UTCOSV refresh
  62. 2026-07-08 15:13 UTCEPSS rescoreEPSS 92% · 99th percentile
  63. 2026-06-30 23:21 UTCEPSS rescoreEPSS 92% · 99th percentile
  64. 2026-06-29 14:05 UTCEPSS rescoreEPSS 92% · 99th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • GitHub PoChex0punk/cont-flood-poc
    Published Apr 12, 2024

    PoC for CVE-2023-45288, continuation flood vulnerability

    Open source ↗

Frequently asked(5)

What is CVE-2023-45288?
CVE-2023-45288 is a critical-severity vulnerability; its CVE record was published on April 4, 2024. An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no…
When was the CVE record for CVE-2023-45288 published?
The CVE record for CVE-2023-45288 was published on April 4, 2024. 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 April 15, 2026; the record at its source may have been updated since.
Is CVE-2023-45288 actively exploited?
CVE-2023-45288 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 92% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2023-45288?
CVE-2023-45288 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
How do I remediate CVE-2023-45288?
A fix for CVE-2023-45288 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-45288 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-2023-45288

Explore →

Is Your Infrastructure Affected by CVE-2023-45288?

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