webpki: Name constraints were accepted for certificates asserting a wildcard name
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-295.
Summary
Permitted subtree name constraints for DNS names were accepted for certificates asserting a wildcard name. This was incorrect because, given a name constraint of `accept.example.com`, `*.example.com` could feasibly allow a name of `reject.example.com` which is outside the constraint. This is very similar to [CVE-2025-61727](https://go.dev/issue/76442). Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | rustls-webpki (crates.io) | 0.101.0 to before 0.103.12 | 0.103.12 | Patch available | GHSA-xgp8-3hg3-c2mh |
| — | rustls-webpki (crates.io) | 0.104.0-alpha.1 to before 0.104.0-alpha.6 | 0.104.0-alpha.6 | Patch available | GHSA-xgp8-3hg3-c2mh |
- rustls-webpki (crates.io) Vendor— Affected 0.101.0 to before 0.103.12 Fixed in 0.103.12 Patch available GHSA-xgp8-3hg3-c2mh
- rustls-webpki (crates.io) Vendor— Affected 0.104.0-alpha.1 to before 0.104.0-alpha.6 Fixed in 0.104.0-alpha.6 Patch available GHSA-xgp8-3hg3-c2mh
Remediation
- Fix · GHSA-xgp8-3hg3-c2mh rustls-webpki (crates.io) Fixed in 0.103.12 Advisory →
- Fix · GHSA-xgp8-3hg3-c2mh rustls-webpki (crates.io) Fixed in 0.104.0-alpha.6 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-xgp8-3hg3-c2mh
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences