Insufficient Verification of Data Authenticity Affecting org.bouncycastle:bcjmail-jdk18on package, versions [,1.85)


Severity

Recommended
0.0
high
0
10

CVSS assessment by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.18% (8th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-JAVA-ORGBOUNCYCASTLE-18512864
  • published4 Aug 2026
  • disclosed3 Aug 2026
  • creditUnknown

Introduced: 3 Aug 2026

NewCVE-2026-59641  (opens in a new tab)
CWE-345  (opens in a new tab)

How to fix?

Upgrade org.bouncycastle:bcjmail-jdk18on to version 1.85 or higher.

Overview

Affected versions of this package are vulnerable to Insufficient Verification of Data Authenticity through a trusted signer-asserted timestamp in the getSignatureTime() method of the S/MIME validator, which returns the CMS signingTime signed attribute and passes it to PKIXCertPathReviewer via usedParameters.setDate(). An attacker holding an expired or revoked signing key can make a signature validate as trusted by setting signingTime to an instant before the revocation or expiry, so the certificate validity and CRL revocation checks run at that chosen time and both isValidCertPath() and ValidationResult.isValidSignature() return true. This requires the signing certificate to chain to a trusted anchor and the application to rely on the S/MIME validator for signature trust, and no RFC 3161 timestamp token is checked to constrain the asserted time against the current time.

CVSS Base Scores

version 4.0
version 3.1