CVE-2026-27141

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-02-26. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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
39.5%
KEV
Not listed

Published

February 26, 2026

Last Modified

April 15, 2026

Advisory Details (3)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

GO-2026-4559 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4559
generic

x/net/http2: nil panic in typeFrameParser for frame types 0x0a-0x0f · Issue #77652 · golang/go · GitHub

https://go.dev/issue/77652
generic
https://go.dev/cl/746180

Vendor Advisories for CVE-2026-27141(5)

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 / EcosystemFixed in / PatchReleasedSource
redhatgolang1-25-main-1.25.9-1.hum12026-04-10redhat
redhatgolang1-26-main-1.26.2-1.hum12026-04-09redhat

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)
PackageVulnerable rangeFixed inDependents
golang.org/x/net—0.51.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

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.

Data Freshness Timeline

(refreshed 13× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 125 total refreshes for this CVE.

  1. 2026-07-16 17:03 UTCEPSS rescore
  2. 2026-07-16 17:03 UTCEPSS rescore
  3. 2026-07-15 16:57 UTCEPSS rescore
  4. 2026-07-15 16:57 UTCEPSS rescore
  5. 2026-07-15 02:00 UTCEPSS rescore
  6. 2026-07-15 02:00 UTCEPSS rescore
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 05:46 UTCEPSS rescore
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 08:27 UTCEPSS rescore
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-08 15:15 UTCEPSS rescore
  15. 2026-07-08 15:15 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 02:30 UTCEPSS rescore
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:06 UTCEPSS rescore
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 75 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-27 03:08 UTCEPSS rescore
  9. 2026-06-25 13:49 UTCEPSS rescore
  10. 2026-06-25 13:49 UTCEPSS rescore
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-24 14:05 UTCEPSS rescore
  13. 2026-06-23 21:33 UTCEPSS rescore
  14. 2026-06-23 21:32 UTCEPSS rescore
  15. 2026-06-22 14:25 UTCEPSS rescore
  16. 2026-06-22 14:25 UTCEPSS rescore
  17. 2026-06-21 14:56 UTCEPSS rescore
  18. 2026-06-21 14:56 UTCEPSS rescore
  19. 2026-06-21 01:59 UTCEPSS rescore
  20. 2026-06-21 01:59 UTCEPSS rescore
  21. 2026-06-19 19:25 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-17 17:53 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
  26. 2026-06-16 17:52 UTCEPSS rescore
  27. 2026-06-15 17:48 UTCEPSS rescore
  28. 2026-06-14 23:18 UTCEPSS rescore
  29. 2026-06-13 23:00 UTCEPSS rescore
  30. 2026-06-12 23:12 UTCEPSS rescore
  31. 2026-06-12 23:12 UTCEPSS rescore
  32. 2026-06-12 01:38 UTCEG score recompute
  33. 2026-06-12 01:38 UTCVendor advisory
  34. 2026-06-12 01:38 UTCGHSA enrichment
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-10 22:18 UTCEPSS rescore
  37. 2026-06-10 22:18 UTCEPSS rescore
  38. 2026-06-10 19:33 UTCEG score recompute
  39. 2026-06-10 19:33 UTCVendor advisory
  40. 2026-06-10 19:33 UTCGHSA enrichment
  41. 2026-06-10 13:22 UTCEPSS rescore
  42. 2026-06-10 08:42 UTCEG score recompute
  43. 2026-06-10 08:42 UTCVendor advisory
  44. 2026-06-10 08:42 UTCGHSA enrichment
  45. 2026-06-09 18:18 UTCEG score recompute
  46. 2026-06-09 18:18 UTCVendor advisory
  47. 2026-06-09 18:18 UTCGHSA enrichment
  48. 2026-06-08 14:17 UTCEPSS rescore
  49. 2026-06-08 14:17 UTCEPSS rescore
  50. 2026-06-08 03:16 UTCEG score recompute
  51. 2026-06-08 03:16 UTCVendor advisory
  52. 2026-06-08 03:16 UTCGHSA enrichment
  53. 2026-06-07 16:24 UTCEG score recompute
  54. 2026-06-07 16:24 UTCVendor advisory
  55. 2026-06-07 16:24 UTCGHSA enrichment
  56. 2026-06-07 15:25 UTCEPSS rescore
  57. 2026-06-07 15:25 UTCEPSS rescore
  58. 2026-06-07 15:25 UTCEPSS rescore
  59. 2026-06-06 13:47 UTCEPSS rescore
  60. 2026-06-06 13:47 UTCEPSS rescore
  61. 2026-06-05 22:47 UTCEPSS rescore
  62. 2026-06-05 22:47 UTCEPSS rescore
  63. 2026-06-05 06:10 UTCEPSS rescore
  64. 2026-06-05 06:10 UTCEPSS rescore
  65. 2026-06-04 13:12 UTCEPSS rescore
  66. 2026-06-04 13:12 UTCEPSS rescore
  67. 2026-06-02 20:13 UTCEPSS rescore
  68. 2026-06-02 20:13 UTCEPSS rescore
  69. 2026-06-01 13:51 UTCEPSS rescore
  70. 2026-06-01 13:51 UTCEPSS rescore
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 22:30 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-31 00:16 UTCEPSS rescore
  75. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

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 39.5% 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