NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

CVE-2022-41717 — net/http2

MEDIUM

CVE-2022-41717 is a medium-severity (CVSS 5.3) CWE-770 vulnerability in golang.org/x/net/http2. A fix is available for golang.org/x/net/http2 — see the affected versions and patch details below.

Excessive memory growth in net/http and golang.org/x/net/http2

Also known asBIT-golang-2022-41717GHSA-xrjj-mj9h-534mGO-2022-1144
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
6.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk
0.00%2.60%5.20%7.80%0.3%6.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹golang.org/x/net/http2🐹golang.org/x/net

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogolang.org/x/net/http2all versions0.4.0go get golang.org/x/net/http2@v0.4.0
🐹Gogolang.org/x/netall versions0.4.0go get golang.org/x/net@v0.4.0

Affected Products

3 products · 5 configurations
OS
fedorafedoraproject
2 versions
3738
Application
gogolang
≥ 1.19.0 && < 1.19.4
range
Application
http2golang
< 0.4.0
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for golang.org/x/net/http2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update golang.org/x/net/http2 to 0.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-41717 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Within Red Hat OpenShift Container Platform, the grafana container is listed as will not fix. Since OCP 4.10, Grafana itself is not shipped and the Grafana web server is protected behind an OAuth proxy server.

ProductFixed inAdvisory
Logging subsystem for Red Hat OpenShift 5.4openshift-logging/lokistack-gateway-rhel8:v5.4.11-10RHSA-2023:0632
Logging subsystem for Red Hat OpenShift 5.4openshift-logging/eventrouter-rhel8:v0.4.0-95RHSA-2023:0931
MTA-6.0-RHEL-8mta/mta-admin-addon-rhel8:6.0.1-8RHSA-2023:0934
NETWORK-OBSERVABILITY-1.2.0-RHEL-9network-observability/network-observability-console-plugin-rhel9:v1.2.0-19RHSA-2023:1817
OADP-1.0-RHEL-8oadp/oadp-registry-rhel8:1.0.7-3RHSA-2023:0692
OADP-1.1-RHEL-8oadp/oadp-kubevirt-velero-plugin-rhel8:1.1.2-18RHSA-2023:1174
OpenShift Developer Tools and Services for OCP 4.9ocp-tools-4/service-binding-operator-bundle:v1.3.3-5RHSA-2023:0918
Openshift Serverless 1 on RHEL 8openshift-serverless-clients-0:1.6.1-2.el8RHSA-2023:1179

Frequently Asked Questions

An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests. HTTP/2 server connections contain a cache of HTTP header keys sent by the client. While the total number of entries in this cache is capped, an attacker sending very large keys can cause the server to allocate approximately 64 MiB per open connection.
O3 Security · Impact-Aware SCA

Is CVE-2022-41717 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2022-41717: net/http2 — Fixed in 0.4.0