Name constraints for URI names were incorrectly accepted
Details
Package
rustls-webpki
Version
0.102.8
Date
2026-04-14
Patched versions
>=0.103.12, <0.104.0-alpha.1,>=0.104.0-alpha.6
Name constraints for URI names were ignored and therefore accepted.
Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented. URI name constraints are now rejected unconditionally.
Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
> Name constraints for URI names were incorrectly accepted
| Details | |
| ------------------- | ---------------------------------------------- |
| Package | `rustls-webpki` |
| Version | `0.102.8` |
| Date | 2026-04-14 |
| Patched versions | `>=0.103.12, <0.104.0-alpha.1,>=0.104.0-alpha.6` |
Name constraints for URI names were ignored and therefore accepted.
Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented. URI name constraints are now rejected unconditionally.
Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
This vulnerability is identified as [GHSA-965h-392x-2mh5](https://github.com/rustls/webpki/security/advisories/GHSA-965h-392x-2mh5). Thank you to [@1seal](https://github.com/1seal) for the report.
See [advisory page](https://rustsec.org/advisories/RUSTSEC-2026-0098.html) for additional details.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
rustls-webpki0.102.8>=0.103.12, <0.104.0-alpha.1,>=0.104.0-alpha.6Name constraints for URI names were ignored and therefore accepted.
Note this library does not provide an API for asserting URI names, and URI name constraints are otherwise not implemented. URI name constraints are now rejected unconditionally.
Since name constraints are restrictions on otherwise properly-issued certificates, this bug is reachable only after signature verification and requires misissuance to exploit.
This vulnerability is identified as GHSA-965h-392x-2mh5. Thank you to @1seal for the report.
See advisory page for additional details.