Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-71891 Overview
CVE-2026-71891 is a signature verification flaw [CWE-347] in Bouncy Castle for Java before version 1.86. The vulnerability affects the BLS12_381BasicScheme.keyValidate routine and every scheme that depends on it, including BasicScheme, MessageAugmentation, and ProofOfPossession. An attacker can craft an elliptic curve point on a foreign ECCurve that shares BLS12-381's field characteristic but defines a different equation and a forged cofactor of one. The point passes keyValidate without being a valid G1 point. Within aggregate signatures, this admits a phantom signer whose public key contributes the identity element in the pairing's target group.
Critical Impact
Aggregate BLS signatures can be accepted as valid even when they contain no signature for a crafted public key, breaking the integrity guarantees of multi-signer verification.
Affected Products
- Bouncy Castle for Java versions prior to 1.86
- BLS12_381BasicScheme, BasicScheme, MessageAugmentation, and ProofOfPossession verifiers
- Applications that construct ECPoint instances on explicit, non-canonical curves and accept them as authority-bearing BLS public keys
Discovery Timeline
- 2026-10-03 - CVE-2026-71891 published to NVD
- 2026-10-06 - Last updated in NVD database
Technical Details for CVE-2026-71891
Vulnerability Analysis
The flaw lies in how BLS12_381BasicScheme.keyValidate trusts curve metadata attached to the public key point. The method invokes pk.isValid() and relies on ECPoint.satisfiesOrder, which returns true immediately when the curve declares a cofactor of one. Because the point carries its own curve parameters, an attacker-supplied ECCurve can advertise a cofactor of one while using an entirely different curve equation. The prime-order subgroup check becomes a no-op.
In Bouncy Castle's pairing implementation, such a non-G1 point contributes the identity element in the target group. An aggregate signature verified against a set of public keys that includes this crafted key is accepted, even though no signature was ever produced for that key and message pair. The result is a phantom signer injected into aggregate verification. The impact is limited to applications that build ECPoint objects from explicit curve parameters. The standard 48-byte compressed-point decoder always supplies the canonical BLS12-381 curve and is not affected.
Root Cause
BLS12_381BasicScheme.keyValidate validated subgroup membership using the point's own curve object rather than confirming the point belongs to the canonical BLS12-381 G1 curve. The subgroup check short-circuits on cofactor == 1, so a forged curve bypasses the only remaining defense against non-G1 inputs.
Attack Vector
Exploitation requires an application that accepts externally constructed ECPoint values on arbitrary curves as BLS public keys and uses them in aggregate verification. User interaction is required to supply the crafted key. Successful exploitation lets an attacker have an aggregate signature accepted without contributing a real signature for one of the listed signers.
{
return false;
}
+ // The subgroup check below trusts pk's own curve's cofactor; a point built on a
+ // foreign curve that merely shares BLS12-381's field can claim cofactor 1 and pass
+ // it trivially, so the curve identity itself must be checked first.
+ if (!BLS12_381G1.isCanonicalCurve(pk.getCurve()))
+ {
+ return false;
+ }
if (!pk.isValid())
{
return false;
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-71891
Indicators of Compromise
- Aggregate BLS verification events accepting signatures where a listed public key was constructed from explicit curve parameters rather than the canonical 48-byte compressed decoder.
- Application logs showing ECPoint instantiation on custom ECCurve objects passed to BLS12_381BasicScheme.keyValidate.
- Public keys whose underlying curve reports cofactor 1 yet differs from the canonical BLS12-381 G1 curve equation y^2 = x^3 + 4.
Detection Strategies
- Audit application code for callers of BLSPublicKeyParameters that bypass the 48-byte compressed-point decoder and build points from raw curve parameters.
- Instrument verification pathways to log and reject public keys whose curve parameters do not match the canonical BLS12-381 G1 field, equation, order, and cofactor.
- Scan dependency manifests (Maven, Gradle) for bcprov-jdk* versions earlier than 1.86.
Monitoring Recommendations
- Monitor cryptographic verification outcomes for anomalies such as aggregate signatures validating with unusually formed participant keys.
- Track upgrades of the Bouncy Castle library across build pipelines and runtime environments to confirm patched versions are deployed.
- Correlate verification failures and successes in the SIEM to detect probing against BLS-based protocols.
How to Mitigate CVE-2026-71891
Immediate Actions Required
- Upgrade Bouncy Castle for Java to version 1.86 or later across all applications and transitive dependencies.
- Review every code path that constructs BLS public keys without using the canonical 48-byte compressed decoder.
- Reject any BLSPublicKeyParameters whose underlying ECCurve is not the canonical BLS12-381 G1 curve.
Patch Information
The fix in commit c16bcfd adds an isCanonicalCurve check in BLS12_381BasicScheme.keyValidate and introduces the canonical curve coefficient B = 4 in BLS12_381G1. The check confirms the point's curve carries the canonical G1 field, equation, order, and cofactor before any subgroup validation runs. See the Bouncy Castle CVE-2026-71891 advisory for details.
Workarounds
- Restrict BLS public key ingestion to the standard 48-byte compressed-point decoder, which always supplies the canonical curve.
- Add application-level validation that compares the ECCurve of every incoming public key against the canonical BLS12-381 G1 curve parameters before verification.
- Isolate aggregate verification logic so that untrusted parties cannot supply arbitrary ECPoint objects.
# Maven dependency update to the patched release
mvn versions:use-dep-version -Dincludes=org.bouncycastle:bcprov-jdk18on -DdepVersion=1.86 -DforceVersion=true
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

