CVE-2026-59641
S/MIME validator trusts signer-asserted signingTime for path validation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.85, 2.73.12, 1.0.7, 2.0.7, 2.1.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
In Bouncy Castle for Java before 1.85, S/MIME validator trusts signer-asserted signingTime for path validation. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcmail-fips and bcjmail-fips 1.0.7 (1.0.X series), 2.0.7 (2.0.X series) and 2.1.7 (2.1.X series).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- bcmail
fixed in 1.85
- bcmail-lts8on
From 2.73.0 · fixed in 2.73.12
- bcmail-fips
From 1.0.0 · fixed in 1.0.7; From 2.0.0 · fixed in 2.0.7; From 2.1.0 · fixed in 2.1.7
- bcjmail-fips
From 1.0.4 · fixed in 1.0.7; From 2.0.0 · fixed in 2.0.7; From 2.1.0 · fixed in 2.1.7