Loading vulnerability…
CVE-2026-59641 is an insufficient data-authenticity verification flaw in the Bouncy Castle Java mail module's S/MIME validation functionality, including SignedMailValidator. During certificate path validation, the validator trusts the signingTime value asserted by the signer rather than using a trusted validation time. A signer can therefore influence the time against which the signing certificate path is evaluated, potentially bypassing certificate-validity policy. Affected versions are Bouncy Castle for Java before 1.85, Bouncy Castle for Java LTS from 2.73.0 before 2.73.12, and BC-FJA bcmail-fips and bcjmail-fips releases before 1.0.7, 2.0.7, or 2.1.7 in their respective release branches.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An S/MIME certificate-path validation flaw in Bouncy Castle Java components that causes the validator to trust a signer-asserted signingTime value.
An integrity-impacting flaw in Bouncy Castle S/MIME validation where signer-asserted signingTime is trusted during certificate path validation, affecting Bouncy Castle for Java, Java LTS, and Java FIPS mail components.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.