Intel

AIKIDO-2026-820118

bcpkix-jdk18on is vulnerable to Use of a Broken or Risky Cryptographic Algorithm

CVE-2026-103606Published 4 days ago
November 16, 2026

63

CVE Score

Medium

Use of a Broken or Risky Cryptographic Algorithm

Are you affected? Scan for Free

TL;DR

TSPAlgorithms.ALLOWED includes MD5, and TimeStampToken.validate() accepts a message imprint whose digest is in that set. A time-stamp token can therefore validate with an MD5 imprint. The fix removes MD5 from the default allowed set. TSPAlgorithms.LEGACY and org.bouncycastle.tsp.allowed_imprint_algorithms still allow it.

How do I fix this?

Upgrade the org.bouncycastle:bcpkix-jdk18on and/or the org.bouncycastle:bcpkix-jdk15to18 library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you validate RFC 3161 time-stamp tokens with TimeStampToken.validate().

Versions

1.63 - 1.86

Fixed in 1.87

Background info

bcpkix-jdk18on is vulnerable to Use of a Broken or Risky Cryptographic Algorithm in versions 1.63 - 1.86.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea