CVE-2026-27141 | Sending certain HTTP/2 frames can cause a server to panic in golang.org/x/net

Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

Published: 2026-02-26 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-27141 is rated Low Risk (31.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-27141

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-21 0.06% 0.02% -0.04%
2 2026-03-04 0.02% 0.06% +0.05%
3 2026-02-27 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-27141

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-27141

OS Trackers for CVE-2026-27141

vendor priority summary link
debian unimportant CVE-2026-27141 unimportant priority: Debian including 1 source packages (golang-golang-x-net), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2026-27141
redhat medium — https://access.redhat.com/security/cve/CVE-2026-27141
suse high CVE-2026-27141 severity important: SUSE including 103 source package names (alloy, azure-storage-azcopy, …), 393 product×package rows across 32 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (32 product lines)): Known Not Affected 393. https://www.suse.com/security/cve/CVE-2026-27141/
ubuntu medium CVE-2026-27141 medium priority: Ubuntu including 7 source packages (adsys, containerd, …), 42 status rows across 7 suites (bionic, focal, jammy, noble, questing, upstream, xenial): not-affected 27, DNE 9, needs-triage 6. https://ubuntu.com/security/CVE-2026-27141

Affected software / configurations for CVE-2026-27141

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-27141

cvelogic Threat Intelligence