CVE-2022-41717

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

6.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2022-12-08 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 05:03 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 6.1% in the next 30 days (EPSS).
• Severity: 5.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2022-12-08 20:15 UTC

Last modified

2026-06-17 05:03 UTC

Exploit probability

6.1% · EPSS, next 30 days

Weakness

CWE-770 · Allocation without limits

Record status

Modified

Affected

• Golang Go < 1.18.9
• Golang Go < 1.19.4
• Golang http2 < 0.4.0
• Fedoraproject Fedora 37
• Fedoraproject Fedora 38

Attack profile CVSS 3.1 · 5.3

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2022-41717.md and follow it. Check whether this project is affected by CVE-2022-41717. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge