CVE-2023-45288

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: epss, nvd
Elevated
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 92%
CISA-KEV: Not listedEPSS PROB: 92%CVSS: 7.5Exploit: Elevated riskExposed 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
92
EG Risk 92/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
Severity90% × 45%
Exploitation92% × 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
92%
EPSS %ILE
99th
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

April 4, 2024

Last Modified

April 15, 2026

References (17)

Vendor Advisories for CVE-2023-45288(20)

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

Patch Availability(30)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
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
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-openshift-apiserver-rhel9:v4.15.0-202407151306.p0.g08f4c42.assembly.stream.el92024-07-25redhat
redhatopenshift4/ose-operator-registry:v4.12.0-202407151105.p0.g3327393.assembly.stream.el82024-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
redhatgit-lfs-0:2.13.3-3.el8_6.12024-07-15redhat
redhatgit-lfs-0:3.2.0-2.el8_8.12024-07-15redhat
redhatgit-lfs-0:2.13.3-5.el9_0.12024-07-15redhat
redhatrhacm2/acm-cluster-permission-rhel9:v2.10.4-62024-07-10redhat

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-
—

All Vendor Advisories

(25)

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 1× in last 7d / 14× 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 108 total refreshes for this CVE.

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

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 ↗

Related CVEs(same product + same vendor)

Frequently asked(5)

What is CVE-2023-45288?
CVE-2023-45288 is a critical vulnerability 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 CVE-2023-45288 disclosed?
CVE-2023-45288 was first published on April 4, 2024, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
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 + CISA KEV + 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.

Book a Demo →Browse All CVEs