# CVE-2026-27141: Sending certain HTTP/2 frames can cause a server to panic in golang.org/x/net > Attackers can crash Go servers by sending specific HTTP/2 frames due to a missing nil check in the golang.org/x/net library. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Feb 2026 - **Updated:** 27 Feb 2026 - **Also known as:** AZL-78629, AZL-78653, AZL-78656, AZL-78659, AZL-78662, AZL-78680, AZL-81203, AZL-84807, CLEANSTART-2026-TL07792, GHSA-8fj7-8h3w-xwfm, GO-2026-4559, MINI-2p2j-jh7x-8g86, MINI-2p39-69wm-j94c, MINI-3hqc-v7gf-5w95, MINI-3m46-2mj9-75v6, MINI-3q7p-qphm-xjwc, MINI-3rh2-5636-qjm2, MINI-3vqv-9642-w849, MINI-3w5v-f7w9-mmqw, MINI-44gc-hggv-7gf5, MINI-44mw-hhh5-jr65, MINI-463h-rqq2-gx28, MINI-4832-wx9p-rhp4, MINI-4rjj-hqp2-vj86, MINI-529h-5jpf-q26w, MINI-53mq-jwcx-3rqh, MINI-53wg-mw5c-vxpf, MINI-55m2-g9vm-rgqp, MINI-59cq-xg64-2jxm, MINI-5f52-qx8x-cxfm, MINI-5rvq-frgw-gvhj, MINI-65j2-r6v6-32j4, MINI-6739-fjcp-rxmc, MINI-6mgw-6468-vjvq, MINI-6qx2-v8x4-j8g8, MINI-6w8m-f236-694q, MINI-7297-gm28-6mxr, MINI-77mm-vpv7-2x9m, MINI-7cc5-9727-p48g, MINI-7qg3-m87h-2p79, MINI-88qx-4m69-j54j, MINI-8gq4-m2rc-763m, MINI-8w4p-vw4m-xvwq, MINI-94r9-84pg-qwgr, MINI-9jww-7wvp-52wp, MINI-9q24-r4rj-c5p3, MINI-9q9h-5h24-64f3, MINI-cr78-j2r6-jhpw, MINI-cx47-rw5w-jw3p, MINI-f2x2-96vw-xwqw, MINI-f3g6-g9jf-3v3r, MINI-f778-cqxh-p7vh, MINI-fgpj-xgw9-g2w5, MINI-g54q-9wf6-h734, MINI-gc99-r449-2g7r, MINI-gc9v-mhhx-mrxq, MINI-gh94-6x8x-6h52, MINI-gpvg-3j8g-32mj, MINI-h3pg-cqg4-2x97, MINI-h4vr-x9w4-953j, MINI-h5q3-mf8x-5f78, MINI-h779-gx29-7gqj, MINI-h88q-x828-qr69, MINI-h8v3-3g9h-6666, MINI-hc8v-wqgq-gf6f, MINI-hj6q-q48q-h5q3, MINI-hmh2-mwf3-f4vh, MINI-hr54-vvch-v6x5, MINI-j3cm-w389-grf9, MINI-j9hw-4v2m-qcrc, MINI-jc9r-9h77-wr66, MINI-jqhj-c9fg-vgp2, MINI-mcr6-f8h3-36px, MINI-mpmr-939q-4ghx, MINI-mv2f-j26q-f4r3, MINI-mx4f-qx2h-vxgh, MINI-p57v-7m88-2937, MINI-prmm-8xf6-74cq, MINI-pwp3-hc85-89p2, MINI-q4m5-vv97-6w89, MINI-q58r-994g-g752, MINI-q6m6-9crx-mm4p, MINI-rff5-m32g-9cjq, MINI-rr4m-647j-4pxw, MINI-vh5h-gr5g-xpmc, MINI-w4xx-p68x-2fhq, MINI-w6w6-rmq3-v2ww, MINI-w6xq-p3q3-46x3, MINI-wj52-5jh5-7jvc, MINI-wpff-9j7x-pv2w, MINI-wvr2-h4w6-w663, MINI-x258-f394-crrx, MINI-x48r-rqp5-hg22, MINI-x5vh-57c9-v83q, MINI-xhpp-559q-jmmp, UBUNTU-CVE-2026-27141, openSUSE-SU-2026:10294-1 ## What is CVE-2026-27141? CVE-2026-27141 is a high-severity vulnerability in golang.org/x/net/http2, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Due to missing nil check, sending 0x0a-0x0f HTTP/2 frames will cause a running server to panic Weakness: CWE-476 (NULL Pointer Dereference) ## Which versions are affected by CVE-2026-27141? 1 open source package ship an affected version, including golang.org/x/net. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `golang.org/x/net` | Go | From 0.50.0 | 0.51.0 | | `telemetrygen` | openSUSE:Tumbleweed | All versions | 0.147.0-1.1 | ## How do I fix CVE-2026-27141? Upgrade golang.org/x/net to 0.51.0 or later. ## Is CVE-2026-27141 being exploited? There is no known exploitation of CVE-2026-27141 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27141 and fix it if it is affected. What it is: CVE-2026-27141 is a high-severity vulnerability in golang.org/x/net/http2, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-27141 in the wild and no public exploit code. Affected packages and fixed versions: - golang.org/x/net (Go): affected from 0.50.0; fixed in 0.51.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-27141/ (Markdown: https://insights.sbomify.com/CVE-2026-27141/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27141 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27141 - OSV: https://osv.dev/vulnerability/CVE-2026-27141 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27141/ Summaries are generated and may contain mistakes; the official description above is the record.