reject crls with unrecognized critical extensions

F-WOLFSSL-CRL-001

Public snapshot: 26 Sep 2026. Status, releases and attribution belong to each source below; none is inferred from another record.

Recorded evidence

—score not recorded

wolfSSL/wolfssl #10239Security PRwolfSSL/wolfssl

reject crls with unrecognized critical extensions

merged

details

Finding IDs: F-WOLFSSL-CRL-001
Status: merged
Reported date: 15 Apr 2026
Rationale: rejects CRLs with unrecognized critical extensions per RFC 5280 section 5.2 instead of silently accepting a revocation scope-bypass condition. public PR #10239 merged on 2026-04-21.
PR opened by: @gasbytes
PR state observed: closed; GitHub merged: true; 2026-09-24
PR observation basis: Public PR metadata recorded in the 2026-09-24 evidence audit; not a live status feed.
Contribution boundary: Report-associated upstream work; @1seal code authorship is not claimed. Credit, where recorded, is a separate fact.

F-WOLFSSL-CRL-001: Verification failures. Unknown critical CRL extensions are not rejected as required. Reviewed 24 Sep 2026. Mechanism assessed by 1seal.

Mechanism source for F-WOLFSSL-CRL-001

Security area (1seal assessment): Identity. Unknown critical CRL extensions are not rejected as required. Reviewed 24 Sep 2026.

Clarify or correct this record privately. The email subject includes the finding ID. For an existing case, continue the agreed private thread. Do not post unpublished vulnerability details in public issues. Research disclosure policy.

How this page groups evidence

This identifier groups recorded evidence; it is not an additional CVE, independent-vulnerability count or guarantee of vendor confirmation. Fixed code, released versions, attribution and independent discovery are distinct claims. Absent metadata means not recorded, not disproved. Counting rules.