CVE-2026-27141: Sending certain HTTP/2 frames can cause a server to panic in golang.org/x/net
Published Feb 26, 2026
·Updated
Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic
Other sources
Sending certain HTTP/2 frames can cause a server to panic in golang.org/x/net
— Microsoft
Affected Software
6 affected componentsFixes available
go/golang.org/x/net
Microsoft azl3 azurelinux-image-tools 1.2.0-1
Microsoft azl3 ignition-flatcar 2.22.0-1
Microsoft azl3 ignition-flatcar 2.22.0-2
IBM MQ Operator<=SC2: v3.2.0 - v3.2.23
CD: v3.3.0, v3.4.0, v3.4.1, v3.5.0, v3.5.1 - v3.5.3, v3.6.0 - v3.6.4, v3.7.0 - v3.7.2, v3.8.0, v3.8.1, v3.9.0, v3.9.1
LTS: v2.0.0 - 2.0.29
IBM supplied MQ Advanced container images<=SC2: 9.4.0.6-r1, 9.4.0.6-r2, 9.4.0.7-r1, 9.4.0.10-r1, 9.4.0.10-r2, 9.4.0.11-r1, 9.4.0.11-r2, 9.4.0.11-r3, 9.4.0.12-r1, 9.4.0.15-r1 - 9.4.0.15-r4, 9.4.0.16-r1, 9.4.0.16-r2, 9.4.0.17-r1, 9.4.0.17-r2, 9.4.0.20-r1CD: 9.4.1.0-r1, 9.4.1.0-r2, 9.4.1.1-r1, 9.4.2.0-r1, 9.4.2.0-r2, 9.4.2.1-r1, 9.4.2.1-r2, 9.4.3.0-r1, 9.4.3.0-r2, 9.4.3.1-r1 - 9.4.3.1-r3, 9.4.4.0-r1 - 9.4.4.0-r4, 9.4.4.1-r1, 9.4.5.0-r1, 9.4.5.0-r2LTS: 9.3.0.0-r1, 9.3.0.0-r2, 9.3.0.0-r3, 9.3.0.1-r1, 9.3.0.1-r2, 9.3.0.1-r3, 9.3.0.1-r4, 9.3.0.3-r1, 9.3.0.4-r1, 9.3.0.4-r2, 9.3.0.5-r1, 9.3.0.5-r2, 9.3.0.5-r3, 9.3.0.6-r1, 9.3.0.10-r1, 9.3.0.10-r2, 9.3.0.11-r1,9.3.0.11-r2, 9.3.0.15-r1, 9.3.0.16-r1, 9.3.0.16-r2, 9.3.0.17-r1, 9.3.0.17-r2, 9.3.0.17-r3, 9.3.0.20-r1, 9.3.0.20-r2, 9.3.0.21-r1, 9.3.0.21-r2, 9.3.0.21-r3, 9.3.0.25-r1, 9.4.0.0-r1, 9.4.0.0-r2, 9.4.0.0-r3, 9.4.0.5-r1, 9.4.0.5-r2
Event History
Feb 26, 2026
CVE Published
via MITRE·06:50 PM
Data Sourced
via MITRE·06:50 PM
DescriptionWeakness
Data Sourced
via NVD·08:31 PM
DescriptionSeverityWeakness
Mar 5, 2026
Data Sourced
via Microsoft·09:08 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·09:08 AM
SeverityAffected Software
Updated
via Microsoft·09:08 AM
DescriptionSeverity
May 15, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-27141?
CVE-2026-27141 has been assessed as a high severity vulnerability due to its ability to cause server panic in affected systems.
2
How do I fix CVE-2026-27141?
To fix CVE-2026-27141, update to the latest version of golang.org/x/net where the nil check issue has been addressed.
3
What types of frames trigger the CVE-2026-27141 vulnerability?
CVE-2026-27141 is triggered by sending 0x0a-0x0f HTTP/2 frames which result in a server panic.
4
Which software is affected by CVE-2026-27141?
CVE-2026-27141 affects the golang.org/x/net library used in Go applications.
5
Is there a workaround for CVE-2026-27141 until a patch is applied?
A viable workaround for CVE-2026-27141 is to avoid sending 0x0a-0x0f HTTP/2 frames until the vulnerability is patched.