CVE-2026-59641: In Bouncy Castle for Java before 1.85, S/MIME validator trusts signer-asserted signingTime for path validation

Q: How do I fix CVE-2026-59641?

bc-java: upgrade to 1.85; bcjmail-fips: upgrade to 1.0.7, 2.0.7, 2.1.7; bcmail-fips: upgrade to 1.0.7, 2.0.7, 2.1.7. Exact commands for each OS are on this page.

Q: Is CVE-2026-59641 being exploited?

CVE-2026-59641 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-59641 affect?

CVE-2026-59641 affects bc-java, bcjmail-fips, bcmail-fips. Severity is medium (CVSS 5.3). 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 a

Q: How urgent is CVE-2026-59641?

Priority 25/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.3REMOTEUPGRADEUPGRADEUPGRADE

CVE-2026-59641 is a medium-severity flaw (CVSS 5.3) affecting bc-java, bcjmail-fips, bcmail-fips. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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).

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.2% (top 93%)
CISA exploited list	No
Weakness	CWE-345
Published	2026-08-03
Last modified	2026-08-28

Publisher (CNA): bcorg · Vendor: bouncycastle

Last updated 2026-08-28 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-08-03 01:16 UTCPublished CVE record published
2026-08-28 18:09 UTCUpdated Record last modified

bouncycastle bc-java UPGRADE

Affected: < 1.85

Fixed in: 1.85

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bc-java || rpm -q bc-java || bc-java --version

2. UPGRADE to 1.85 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bc-java

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bc-java

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

bouncycastle bcjmail-fips UPGRADE

Affected: < 1.0.7 · >= 2.0.5 and < 2.0.7 · >= 2.1.6 and < 2.1.7

Fixed in: 1.0.7, 2.0.7, 2.1.7

Safe to downgrade to: a release before 2.0.5

1. Check installed version

apt-cache policy bcjmail-fips || rpm -q bcjmail-fips || bcjmail-fips --version

2. UPGRADE to 1.0.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bcjmail-fips

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bcjmail-fips

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.5 (Debian / Ubuntu)

apt-cache madison bcjmail-fips sudo apt install bcjmail-fips=<VERSION_BEFORE_2.0.5> sudo apt-mark hold bcjmail-fips

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list bcjmail-fips sudo dnf downgrade bcjmail-fips-<VERSION_BEFORE_2.0.5> sudo dnf versionlock add bcjmail-fips

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

bouncycastle bcmail-fips UPGRADE

Affected: < 1.0.7 · >= 2.0.5 and < 2.0.7 · >= 2.1.6 and < 2.1.7

Fixed in: 1.0.7, 2.0.7, 2.1.7

Safe to downgrade to: a release before 2.0.5

1. Check installed version

apt-cache policy bcmail-fips || rpm -q bcmail-fips || bcmail-fips --version

2. UPGRADE to 1.0.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bcmail-fips

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bcmail-fips

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2.0.5 (Debian / Ubuntu)

apt-cache madison bcmail-fips sudo apt install bcmail-fips=<VERSION_BEFORE_2.0.5> sudo apt-mark hold bcmail-fips

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list bcmail-fips sudo dnf downgrade bcmail-fips-<VERSION_BEFORE_2.0.5> sudo dnf versionlock add bcmail-fips

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

bouncycastle bouncy castle for java lts UPGRADE

Affected: <= 2.73.11

Fixed in: newer than 2.73.11

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy bouncy-castle-for-java-lts || rpm -q bouncy-castle-for-java-lts || bouncy-castle-for-java-lts --version

2. UPGRADE to newer than 2.73.11 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade bouncy-castle-for-java-lts

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade bouncy-castle-for-java-lts

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-59641?

bc-java: upgrade to 1.85; bcjmail-fips: upgrade to 1.0.7, 2.0.7, 2.1.7; bcmail-fips: upgrade to 1.0.7, 2.0.7, 2.1.7. Exact commands for each OS are on this page.

Is CVE-2026-59641 being exploited?

CVE-2026-59641 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-59641 affect?

CVE-2026-59641 affects bc-java, bcjmail-fips, bcmail-fips. Severity is medium (CVSS 5.3). 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 a

How urgent is CVE-2026-59641?

Priority 25/100. Remotely exploitable, no login, no user action

Software pages

Java vulnerabilities

Related CVEs

CVE-2026-59644 HIGH 7.5 UPGRADE In Bouncy Castle for Java before 1.85, MLS hash-ratchet honours arbitrary 32-bit generation counter from sende
CVE-2026-12852 HIGH 7.5 UPGRADE In Bouncy Castle for Java before 1.85, MLS wire decoder allocates attacker-declared opaque length before bound
CVE-2026-59652 MEDIUM 6.5 UPGRADE In Bouncy Castle for Java before 1.85, LDAP filter injection in legacy jdk1.4 LDAPStoreHelper.
CVE-2026-17507 HIGH 7.5 UPGRADE In Bouncy Castle for Java before 1.86, the MLS implementation (org.bouncycastle.mls) holds RFC 9420's uint32 l
CVE-2024-14041 MEDIUM 5.9 UPGRADE In Bouncy Castle for Java from 1.73 to before 1.78, three ML-KEM (CRYSTALS-Kyber) routines divided secret-deri

References

← Back to latest CVEs