RGB-Tools / RGB-Tools/rust-lightning
RUSTSEC-2026-0104: Reachable panic in certificate revocation list parsing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 9
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
Reachable panic in certificate revocation list parsing
| Details | |
|---|---|
| Package | rustls-webpki |
| Version | 0.101.7 |
| Date | 2026-04-22 |
| Patched versions | >=0.103.13, <0.104.0-alpha.1,>=0.104.0-alpha.7 |
A panic was reachable when parsing certificate revocation lists via [BorrowedCertRevocationList::from_der]
or [OwnedCertRevocationList::from_der]. This was the result of mishandling a syntactically valid empty
BIT STRING appearing in the onlySomeReasons element of a IssuingDistributionPoint CRL extension.
This panic is reachable prior to a CRL's signature being verified.
Applications that do not use CRLs are not affected.
Thank you to @tynus3 for the report.
See advisory page for additional details.
Contributor guide
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
Start with the RustSec advisory and the BorrowedCertRevocationList::from_der and OwnedCertRevocationList::from_der entry points named in the report. Inspect how this repository declares or resolves rustls-webpki, then verify that the affected version is no longer used and that parsing the described empty BIT STRING does not panic.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100