RUSTSEC-2026-0098: Name constraints for URI names were incorrectly accepted
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
Name constraints for URI names were incorrectly accepted
| Details | |
|---|---|
| Package | rustls-webpki |
| Version | 0.103.11 |
| 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. Thank you to @1seal for the report.
See advisory page for additional details.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named. Start with the linked GHSA and RustSec advisory, then determine what change this docs.rs issue is requesting; the issue text does not define a completion condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100