CVE-2023-44487

CRITICALNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2023-10-10), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.5 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, nvd
Exploited in the wild
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • 5,731 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 100%CVSS: 7.5Exploit: cisa kev · ssvc active · epss top5pct · epss high · public exploitExposed services: 5,731

A fix is available — apply it.

The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

Internet exposure · derived from Shodan data

5,731 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2023-44487, in our KEV-Exposure radar’s Shodan-derived sample.

across 107 countries (United States, Germany, China, Japan, France)top: http_server, jenkins, nginx
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
96
EG Risk 96/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%
Exploitation100% × 40%
Automatability100% × 15%
CISA SSVC: Attend at low or medium mission impact; Act at high (mission-essential systems).
Action: A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.
EPSS PROB
100%
EPSS %ILE
99th
KEV
⚠ Exploited

CISA SSVCAttend at low or medium mission impact; Act at high (mission-essential systems).

A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.

Exploitation active (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 10, 2023

Last Modified

August 11, 2026

Advisory Details (10)

Auto-updated May 20, 2026
Patch available. Sources: redhat.
generic

Biggest DDoSes of all time generated by protocol 0-day in HTTP/2 - Ars Technica

https://arstechnica.com/security/2023/10/how-ddosers-used-the-http-2-protocol-to-deliver-attacks-of-unprecedented-size/
redhatMentions a patch (unverified)

cve-details

https://access.redhat.com/security/cve/cve-2023-44487
generic

oss-security - Re: CVE-2023-44487: HTTP/2 Rapid Reset attack against many implementations

http://www.openwall.com/lists/oss-security/2023/10/20/8
generic

oss-security - CVE-2023-45802: Apache HTTP Server: HTTP/2 stream memory not reclaimed right away on RST

http://www.openwall.com/lists/oss-security/2023/10/19/6
generic

oss-security - Re: CVE-2023-44487: HTTP/2 Rapid Reset attack against many implementations

http://www.openwall.com/lists/oss-security/2023/10/18/8
generic

oss-security - Vulnerability in Jenkins

http://www.openwall.com/lists/oss-security/2023/10/18/4
generic

oss-security - Re: CVE-2023-44487: HTTP/2 Rapid Reset attack against many implementations

http://www.openwall.com/lists/oss-security/2023/10/13/9
generic

oss-security - Re: CVE-2023-44487: HTTP/2 Rapid Reset attack against many implementations

http://www.openwall.com/lists/oss-security/2023/10/13/4
generic

oss-security - Re: CVE-2023-44487: HTTP/2 Rapid Reset attack against many implementations

http://www.openwall.com/lists/oss-security/2023/10/10/7
generic

oss-security - CVE-2023-44487: HTTP/2 Rapid Reset attack against many implementations

http://www.openwall.com/lists/oss-security/2023/10/10/6

Vendor Advisories for CVE-2023-44487(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
redhatmulticluster-engine/kube-rbac-proxy-mce-rhel9:17662743242026-01-15redhat
redhatrhacm2/kube-rbac-proxy-rhel9:v2.112025-12-17redhat
redhatmulticluster-engine/kube-rbac-proxy-mce-rhel9:v2.62025-12-17redhat
redhateap7-wildfly-0:7.1.12-2.GA_redhat_00002.1.ep7.el72025-09-25redhat
redhattomcat-1:10.1.36-1.el10_02025-05-13redhat
redhatdevspaces/udi-rhel8:3.15-52024-07-18redhat
redhatceph-2:16.2.10-266.el8cp2024-06-26redhat
redhatrhceph/rhceph-5-dashboard-rhel8:5-872024-06-26redhat
redhatrhceph/snmp-notifier-rhel9:1.2.1-572024-05-01redhat
redhathelm-0:3.13.2-35.el92024-04-18redhat
redhatopenshift4/ovirt-csi-driver-rhel8-operator:v4.15.0-202404030309.p0.ge9b0fa2.assembly.stream.el82024-04-16redhat
redhatnodejs:16-8090020240315081818.a75119d52024-03-20redhat
redhatrhdh/rhdh-hub-rhel9:1.1-972024-03-18redhat
redhatkube-descheduler-operator/kube-descheduler-rhel9-operator:v5.0-142024-03-06redhat
redhatrun-once-duration-override-operator/run-once-duration-override-rhel9-operator:v1.1-52024-02-28redhat
redhatopenshift4/ovirt-csi-driver-rhel9:v4.15.0-202401261531.p0.gb8d25ad.assembly.stream2024-02-27redhat
redhatopenshift-sandboxed-containers/osc-rhel9-operator:1.5.2-32024-02-15redhat
redhatjenkins-0:2.426.3.1706516352-3.el82024-02-12redhat
redhatalbo/aws-load-balancer-rhel8-operator:1.1.1-12024-01-30redhat
redhatalbo/aws-load-balancer-rhel8-operator:1.0.1-22024-01-30redhat
redhatmta/mta-cli-rhel9:7.0.0-442024-01-30redhat
redhatedo/external-dns-rhel8-operator:1.0.1-62024-01-29redhat
redhatopenshift4/ose-openshift-apiserver-rhel8:v4.13.0-202312040608.p0.g6c07330.assembly.stream2023-12-13redhat
redhatrhceph/rhceph-6-dashboard-rhel9:6-822023-12-12redhat
redhatopenshift4/ose-gcp-cloud-controller-manager-rhel8:v4.14.0-202311300410.p0.g09e96a9.assembly.stream2023-12-12redhat
redhatcontainer-native-virtualization/virt-artifacts-server-rhel9:v4.14.1-42023-12-07redhat
redhatopenshift-pipelines-client-0:1.10.6-11031.el82023-12-07redhat
redhatopenshift-pipelines/pipelines-workingdirinit-rhel8:v1.10.6-102023-12-07redhat
redhatcri-o-0:1.25.5-2.rhaos4.12.git0217273.el82023-12-06redhat
redhatundertow2023-12-05redhat

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

(50 across 18 ecosystems)
Debian:12(8)
PackageVulnerable rangeFix by version rangeDependents
dnsdist1.7.3-2 ... 2.1.2-1 (37 versions)
  • every version on: no fix on record
—
grpc1.51.1-3 ... 1.83.0-1 (12 versions)
  • every version on: no fix on record
—
h2o2.2.5+dfsg2-10 ... 2.2.5+dfsg2-9 (7 versions)
  • every version on: no fix on record
—
haproxy—
  • every version up to 1.8.13-1: fixed in 1.8.13-1
—
jetty99.4.50-4, 9.4.50-4+deb12u1
  • every version up to 9.4.50-4+deb12u2: fixed in 9.4.50-4+deb12u2
—
netty1:4.1.48-7
  • every version up to 1:4.1.48-7+deb12u1: fixed in 1:4.1.48-7+deb12u1
—
nghttp21.52.0-1
  • every version up to 1.52.0-1+deb12u1: fixed in 1.52.0-1+deb12u1
—
nginx1.22.1-9 ... 1.30.4-6 (53 versions)
  • every version on: no fix on record
—
Debian:11(7)
PackageVulnerable rangeFix by version rangeDependents
dnsdist1.5.1-3 ... 2.1.1-1 (45 versions)
  • every version on: no fix on record
—
grpc1.30.2-3 ... 1.82.0-1 (22 versions)
  • every version on: no fix on record
—
h2o2.2.5+dfsg2-10 ... 2.2.5+dfsg2-9 (10 versions)
  • every version on: no fix on record
—
haproxy—
  • every version up to 1.8.13-1: fixed in 1.8.13-1
—
jetty99.4.39-3 ... 9.4.50-4 (17 versions)
  • every version up to 9.4.50-4+deb11u1: fixed in 9.4.50-4+deb11u1
—
netty1:4.1.48-4, 1:4.1.48-4+deb11u1
  • every version up to 1:4.1.48-4+deb11u2: fixed in 1:4.1.48-4+deb11u2
—
nghttp21.43.0-1
  • every version up to 1.43.0-1+deb11u1: fixed in 1.43.0-1+deb11u1
—
Debian:13(6)
PackageVulnerable rangeFix by version rangeDependents
dnsdist—
  • every version up to 1.8.2-2: fixed in 1.8.2-2
—
grpc1.51.1-6 ... 1.83.0-1 (7 versions)
  • every version on: no fix on record
—
haproxy—
  • every version up to 1.8.13-1: fixed in 1.8.13-1
—
jetty9—
  • every version up to 9.4.53-1: fixed in 9.4.53-1
—
netty—
  • every version up to 1:4.1.48-8: fixed in 1:4.1.48-8
—
nghttp2—
  • every version up to 1.57.0-1: fixed in 1.57.0-1
—
Debian:14(6)
PackageVulnerable rangeFix by version rangeDependents
dnsdist—
  • every version up to 1.8.2-2: fixed in 1.8.2-2
—
grpc1.51.1-6 ... 1.83.0-1 (7 versions)
  • every version on: no fix on record
—
haproxy—
  • every version up to 1.8.13-1: fixed in 1.8.13-1
—
jetty9—
  • every version up to 9.4.53-1: fixed in 9.4.53-1
—
netty—
  • every version up to 1:4.1.48-8: fixed in 1:4.1.48-8
—
nghttp2—
  • every version up to 1.57.0-1: fixed in 1.57.0-1
—
Debian:10(4)
PackageVulnerable rangeFix by version rangeDependents
h2o2.2.5+dfsg2-2, 2.2.5+dfsg2-2+deb10u1
  • every version up to 2.2.5+dfsg2-2+deb10u2: fixed in 2.2.5+dfsg2-2+deb10u2
—
jetty99.4.15-1 ... 9.4.50-4 (40 versions)
  • every version up to 9.4.50-4+deb10u1: fixed in 9.4.50-4+deb10u1
—
netty1:4.1.33-1, 1:4.1.33-1+deb10u1, 1:4.1.33-1+deb10u2, 1:4.1.33-1+deb10u3
  • every version up to 1:4.1.33-1+deb10u4: fixed in 1:4.1.33-1+deb10u4
—
nghttp21.36.0-2, 1.36.0-2+deb10u1
  • every version up to 1.36.0-2+deb10u2: fixed in 1.36.0-2+deb10u2
—
Maven(4)
PackageVulnerable rangeFix by version rangeDependents
com.typesafe.akka:akka-http-core3.0.0-RC1
  • every version up to 10.5.3: fixed in 10.5.3
—
com.typesafe.akka:akka-http-core_2.1110.0.0 ... 3.0.0-RC1 (58 versions)
  • every version through 10.1.15: no fix on record
—
com.typesafe.akka:akka-http-core_2.1210.0.0 ... 10.5.2 (59 versions)
  • every version up to 10.5.3: fixed in 10.5.3
—
com.typesafe.akka:akka-http-core_2.1310.1.10 ... 10.5.2 (31 versions)
  • every version up to 10.5.3: fixed in 10.5.3
—
Alpine:v3.15(2)
PackageVulnerable rangeFix by version rangeDependents
lighttpd—
  • every version up to 1.4.73-r0: fixed in 1.4.73-r0
—
nghttp2—
  • every version up to 1.46.0-r2: fixed in 1.46.0-r2
—
Alpine:v3.16(2)
PackageVulnerable rangeFix by version rangeDependents
lighttpd—
  • every version up to 1.4.73-r0: fixed in 1.4.73-r0
—
nghttp2—
  • every version up to 1.47.0-r2: fixed in 1.47.0-r2
—
Alpine:v3.17(2)
PackageVulnerable rangeFix by version rangeDependents
lighttpd—
  • every version up to 1.4.73-r0: fixed in 1.4.73-r0
—
nghttp2—
  • every version up to 1.51.0-r2: fixed in 1.51.0-r2
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
nghttp2—
  • every version up to 1.57.0-r0: fixed in 1.57.0-r0
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
golang.org/x/net—
  • every version up to 0.17.0: fixed in 0.17.0
—
Swift(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/apple/swift-nio-http2—1.28.0 (one range)—

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

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 40× in last 7d / 186× 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 862 total refreshes for this CVE.

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

Publicly available exploits

(10 references)

Working exploit code is in the public domain (9 GitHub PoCs) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCtpirate/cve-2023-44487-POC
    First seen Dec 14, 2025

    poc for the rst dos attack discovered in 2023

    Open source ↗
  • Exploit-DBEDB-52426
    First seen Sep 16, 2025

    HTTP/2 2.0 - Denial Of Service (DOS)

    Open source ↗
  • GitHub PoCmoften/CVE-2023-44487-HTTP-2-Rapid-Reset-Attack
    First seen Apr 14, 2025

    HTTP/2 Rapid Reset Exploit PoC

    Open source ↗
  • GitHub PoCthreatlabindonesia/CVE-2023-44487-HTTP-2-Rapid-Reset-Exploit-PoC
    First seen Dec 3, 2024
    Open source ↗
  • GitHub PoCnxenon/cve-2023-44487
    First seen Nov 10, 2023

    Examples for Implementing cve-2023-44487 ( HTTP/2 Rapid Reset Attack ) Concept

    Open source ↗
  • GitHub PoCndrscodes/http2-rst-stream-attacker
    First seen Nov 8, 2023

    Highly configurable tool to check a server's vulnerability against CVE-2023-44487 by rapidly sending HEADERS and RST_STREAM frames and documenting the server's responses.

    Open source ↗
  • GitHub PoCReToCode/golang-CVE-2023-44487
    First seen Oct 25, 2023
    Open source ↗
  • GitHub PoCstudiogangster/CVE-2023-44487
    First seen Oct 16, 2023

    A python based exploit to test out rapid reset attack (CVE-2023-44487)

    Open source ↗
  • GitHub PoCsecengjeff/rapidresetclient
    First seen Oct 13, 2023

    Tool for testing mitigations and exposure to Rapid Reset DDoS (CVE-2023-44487)

    Open source ↗
  • GitHub PoCAppsynergy-io/CVE-2023-44487
    First seen Oct 11, 2023

    Proof of concept for DoS exploit

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(6)

What is CVE-2023-44487?
CVE-2023-44487 is a critical vulnerability published on October 10, 2023. The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.
When was CVE-2023-44487 disclosed?
CVE-2023-44487 was first published on October 10, 2023, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-44487 actively exploited?
Yes. CISA added CVE-2023-44487 to the Known Exploited Vulnerabilities catalog on October 10, 2023, affecting IETF HTTP/2. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2023-44487?
CVE-2023-44487 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).
Which products are affected by CVE-2023-44487?
CVE-2023-44487 affects IETF HTTP/2. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2023-44487?
A fix for CVE-2023-44487 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2023-44487 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-44487

Explore →

Is Your Infrastructure Affected by CVE-2023-44487?

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

Book a Demo →Browse All CVEs