CVE-2026-27141

HIGHNVD 7.57.5—

7.5

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

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 6.9%
KEV: Not listed

Published

February 26, 2026

Last Modified

April 15, 2026

References (4)

security@golanghttps://go.dev/cl/746180
security@golanghttps://go.dev/issue/77652
security@golanghttps://nvd.nist.gov/vuln/detail/CVE-2026-27141
security@golanghttps://pkg.go.dev/vuln/GO-2026-4559

Vendor Advisories for CVE-2026-27141(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(2)

Vendor / Ecosystem	Fixed in / Patch	Released	Source
redhat	golang1-25-main-1.25.9-1.hum1	2026-04-10	redhat
redhat	golang1-26-main-1.26.2-1.hum1	2026-04-09	redhat

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

(1 across 1 ecosystem)

Go(1)

Package	Vulnerable range	Fixed in	Dependents
golang.org/x/net	—	0.51.0	—

Additional Vendor Advisories

(1)

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.

Microsoft MSRCCVE-2026-271412026-03-05
Sending certain HTTP/2 frames can cause a server to panic in golang.org/x/net

Data Freshness Timeline

(refreshed 17× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-27 13:40 UTCepss_batch
2026-05-26 13:44 UTCepss_batch
2026-05-26 13:44 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-24 16:59 UTCepss_batch
2026-05-23 15:21 UTCepss_batch
2026-05-22 21:16 UTCepss_batch

Frequently asked(5)

What is CVE-2026-27141?

CVE-2026-27141 is a high vulnerability published on February 26, 2026. Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic

When was CVE-2026-27141 disclosed?

CVE-2026-27141 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-27141 actively exploited?

CVE-2026-27141 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-27141?

CVE-2026-27141 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2026-27141?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27141, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-27141

Explore →

Is Your Infrastructure Affected by CVE-2026-27141?

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

Start Free Scan →Browse All CVEs

CVE-2026-27141

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2026-27141(2)