Vulnerabilities

Vulnerability · CVE-2026-27138

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.

Published Mar 6, 2026 · catalog updated Jun 17, 2026 · Certificate verification can panic

Check if you run it

No confirmed exploitation is on record for CVE-2026-27138. EPSS is 0.33%. Act only if a listed version of Certificate verification can panic is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (Certificate verification can panic).
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.33%
Remediation
Advisory link
Affected products
cpe golang/go

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe golang/go1.26.0

How to fix CVE-2026-27138

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-27138. EPSS is 0.33%. Act only if a listed version of Certificate verification can panic is installed.

Which versions are affected?

Compare what you have installed with 1.26.0. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-295: Improper Certificate Validation. EPSS 0.33%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Mar 6, 2026 · NIST NVD

    Detected

    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.

  2. Jun 17, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-27138

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-27138

    30-day exploitation probability 0.3%

    first.org
  • NIST NVDVulnerability recordCVE-2026-27138

    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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.