# CVE-2026-5263: URI nameConstraints not enforced in ConfirmNameConstraints()

> A malicious sub-CA can issue leaf certificates with invalid URI SANs that wolfSSL accepts, bypassing nameConstraints validation.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Apr 2026
- **Updated:** 2 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-5263, GHSA-9xmr-c663-3rpr, JLSEC-2026-717, UBUNTU-CVE-2026-5263

## What is CVE-2026-5263?

CVE-2026-5263 is a high-severity vulnerability in Wolfssl Wolfssl, published on 9 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

URI nameConstraints from constrained intermediate CAs are parsed but not enforced during certificate chain verification in wolfcrypt/src/asn.c. A compromised or malicious sub-CA could issue leaf certificates with URI SAN entries that violate the nameConstraints of the issuing CA, and wolfSSL would accept them as valid.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2026-5263?

It affects 1 product.


Products: Wolfssl Wolfssl.

## How do I fix CVE-2026-5263?

Apply the vendor's patch.

## Is CVE-2026-5263 being exploited?

There is no known exploitation of CVE-2026-5263 in the wild and no public exploit code.

## Other vulnerabilities in Wolfssl Wolfssl

- [CVE-2024-5991](https://insights.sbomify.com/CVE-2024-5991/): Buffer overread in domain name matching (critical 10.0)
- [CVE-2021-37155](https://insights.sbomify.com/CVE-2021-37155/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-36177](https://insights.sbomify.com/CVE-2020-36177/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2896](https://insights.sbomify.com/CVE-2014-2896/): Memory corruption in n/a (critical 9.8)
- [CVE-2014-2897](https://insights.sbomify.com/CVE-2014-2897/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5263 and fix it if it is affected.

What it is: CVE-2026-5263 is a high-severity vulnerability in Wolfssl Wolfssl, published on 9 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5263 in the wild and no public exploit code.

Affected product: Wolfssl Wolfssl. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-5263/ (Markdown: https://insights.sbomify.com/CVE-2026-5263/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5263
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5263
- OSV: https://osv.dev/vulnerability/CVE-2026-5263

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5263/
Summaries are generated and may contain mistakes; the official description above is the record.