Severity:

HIGH RISK

(7.5)

Risky Crypto and Weak Signature Checks in Bouncy Castle

CVE-2026-5588

Awaiting Analysis

Vulnerability type

Category:

Cryptographic Weakness

CWE:

CWE-327, CWE-347

Impact:

Integrity and Authentication Bypass

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

Certain Bouncy Castle PKIX modules use broken or risky cryptographic algorithms and insufficient signature verification logic in JcaContentVerifierProviderBuilder.

Under specific configurations, this can weaken certificate and content validation, allowing attackers to bypass integrity or authenticity checks when they can influence verification inputs.

Affected context

The vulnerability appears in applications that integrate Bouncy Castle PKIX components for certificate, CMS, or signature validation.

It is relevant when JcaContentVerifierProviderBuilder (and related builders) are used to construct verification logic, especially where algorithm choice or verification behavior is not constrained by the application.

Systems that implicitly trust Bouncy Castle defaults for cryptographic algorithms or signature validation, without additional policy enforcement, are most exposed.

Exploit preconditions

  • Attack surface: Any interface that relies on Bouncy Castle PKIX verification (e.g., certificate chains, signed objects, CMS/PKCS#7 validation).
  • Required access: Ability to supply or modify certificates, signed data, or signature parameters that are processed via Bouncy Castle's bcpkix modules.
  • Trigger point: Invocation of JcaContentVerifierProviderBuilder (or equivalent code paths) to verify signatures or certificate-related structures.
  • Why exploitation is possible: The presence of broken or risky algorithms (CWE-327) and insufficient enforcement of signature validity or algorithm constraints (CWE-347) can cause the verifier to accept signatures or algorithm choices that should be rejected, undermining integrity guarantees.

Why this happens

At its core, this issue arises from cryptographic API behavior that permits weak or risky algorithms and does not strictly enforce signature validity constraints.

The JcaContentVerifierProviderBuilder and related classes abstract algorithm selection and verification logic; if their defaults or supported sets include insecure algorithms or do not fully validate the correctness and legitimacy of signatures, the resulting verification process can be subverted.

This maps to CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where deprecated or weak primitives remain usable, and CWE-347: Improper Verification of Cryptographic Signature, where verification logic may accept signatures or parameters that do not meet required security properties.

Potential impact

  • Attackers may be able to have forged or altered signatures accepted as valid under certain verification flows.
  • Certificate chains or signed content could be trusted even when they have been tampered with.
  • Man-in-the-middle attacks on protocols relying on affected verification routines can become easier.
  • Security controls that depend on strong cryptographic assurance (such as code signing, PKI-based access control, or secure messaging) may be weakened or bypassed.

General mitigation guidance

Effective mitigation focuses on strengthening cryptographic policy and verification patterns rather than relying on library defaults.

Common approaches include:

  • Enforcing strict algorithm whitelists that allow only modern, well-reviewed algorithms and key sizes for signature verification.
  • Centralizing cryptographic configuration so that algorithm and key-size constraints are consistently applied across all verification code paths.
  • Implementing explicit checks for signature validity, certificate constraints, and acceptable parameter sets, rather than trusting automatic verification behavior.
  • Designing systems so that cryptographic failures default to rejection and do not fall back to weaker or more permissive verification modes.
  • Minimizing reliance on legacy cryptographic constructs and phasing out support for outdated algorithms in application-level policy.

How teams detect issues like this

Detection typically involves examining both code and runtime configuration for insecure cryptographic usage patterns.

Possible strategies include:

  • Static analysis rules that flag uses of cryptographic APIs without explicit algorithm or key-size constraints, especially around JcaContentVerifierProviderBuilder and PKIX verification code.
  • Code review checklists that require developers to document chosen algorithms, key sizes, and validation steps for any certificate or signature handling paths.
  • Security policies that disallow legacy or high-risk algorithms and enforce automated tests to verify that only approved cryptographic suites are accepted.
  • Runtime logging or monitoring of algorithm choices and verification outcomes, allowing identification of unexpected or weak algorithm use in production environments.

Sources

SourceLink
github.comgithub.com/bcgit/bc-java/commit/656bae0dbd9b1521f840521ff786e78749fe3057
github.comgithub.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%905588
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11720
access.redhat.comaccess.redhat.com/errata/RHSA-2026:11721
access.redhat.comaccess.redhat.com/errata/RHSA-2026:13631
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14272
access.redhat.comaccess.redhat.com/errata/RHSA-2026:14276
access.redhat.comaccess.redhat.com/errata/RHSA-2026:17668
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18054
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18055
access.redhat.comaccess.redhat.com/errata/RHSA-2026:18059
access.redhat.comaccess.redhat.com/errata/RHSA-2026:21772
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53644
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53645
access.redhat.comaccess.redhat.com/errata/RHSA-2026:53646
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60239
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60246
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60247
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60248
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60249
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60250
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60251
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60252
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60254
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60256
access.redhat.comaccess.redhat.com/errata/RHSA-2026:60259
access.redhat.comaccess.redhat.com/errata/RHSA-2026:66488
access.redhat.comaccess.redhat.com/security/cve/CVE-2026-5588
bugzilla.redhat.combugzilla.redhat.com/show_bug.cgi?id=2458634
security.access.redhat.comsecurity.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-5588.json

Frequently asked

questions

Exploitability depends on how an application uses Bouncy Castle PKIX modules. If they are central to certificate or signature verification in security-critical workflows, and inputs can be influenced by an attacker, the exposure can be significant. In tightly controlled environments with strong policy enforcement, practical risk may be reduced.

An attacker typically needs the ability to provide or manipulate the certificates, signed objects, or signature parameters processed by the affected verification routines. This can occur through network-facing protocols, file-based signature validation, or any interface that accepts externally supplied cryptographic material.

The most robust fix pattern is to define and enforce strict cryptographic policies at the application level: explicitly select strong, modern algorithms, enforce minimum key sizes, and ensure that verification routines reject any inputs that do not meet those criteria. Avoid relying on implicit defaults and review all PKIX and signature verification flows for adherence to these policies.

Prevention usually involves treating cryptographic design as a first-class concern: adopt well-established security guidelines, maintain a clear registry of allowed algorithms and parameters, integrate security reviews for all cryptographic code paths, and use automated checks to detect risky algorithm usage early in development and CI pipelines.

Find out what's already
exploitable in your codebase.