Security readout for executives and security teams
Plain-English summary
wolfSSL may accept some certificates that should be rejected when a constrained intermediate CA limits allowed URI names. If that intermediate CA is compromised or malicious, it could issue a certificate outside its permitted URI scope and wolfSSL would still treat the chain as valid.
Executive priority
Treat as high priority for systems where wolfSSL validates external certificates or enforces delegated CA boundaries. Urgency is lower where wolfSSL is absent or URI nameConstraints are not part of trust decisions, but exposure should be verified promptly.
Technical view
In wolfcrypt/src/asn.c, URI nameConstraints are parsed but not enforced in ConfirmNameConstraints() during certificate chain verification. A leaf certificate containing URI SAN entries that violate the issuing constrained CA's limits may validate. The issue is classified as CWE-295 with CVSS 4.0 score 7.0 high.
Likely exposure
Exposure is most likely where wolfSSL performs certificate path validation and relies on intermediate CA URI nameConstraints for trust boundaries. The provided affected-version data is unclear, listing wolfSSL version "0" with default status unaffected, so product/version exposure needs vendor confirmation.
Exploitation context
The bundle does not show KEV listing or active exploitation. The described abuse requires a compromised or malicious constrained sub-CA capable of issuing leaf certificates, then relying on wolfSSL accepting URI SANs outside the permitted nameConstraints.
Researcher notes
Evidence supports a certificate validation flaw in URI nameConstraints enforcement. Do not assume affected versions beyond the bundle; the version field is ambiguous. PR #10048 and the Talos report are the key technical references for confirming patch status and exact behavior.
Mitigation direction
- Check wolfSSL and Talos guidance for affected and fixed versions.
- Upgrade wolfSSL when the vendor identifies a corrected release.
- Review whether PR #10048 is included in your wolfSSL build.
- Limit trust in constrained intermediates where URI constraints are security-critical.
- Monitor CVE, Talos, and wolfSSL advisories for updated remediation details.
Validation and detection
- Inventory applications and appliances that embed wolfSSL.
- Identify wolfSSL versions and whether certificate verification is enabled.
- Check for reliance on URI SAN nameConstraints in constrained intermediates.
- Confirm builds include the vendor fix or documented mitigation.
- Review trust stores for constrained sub-CAs with URI restrictions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-5263 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7 (4.0)
- Known Exploited
- No
- Published
Vector: 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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——wolfSSLVulnerability scoring details
Base CVSS 4.0 score
7HighVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/wolfSSL/wolfssl/pull/10048CVE reference, wolfSSL
- https://www.talosintelligence.com/vulnerability_reports/TALOS-2026-2410CVE reference, CVE
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.