PT-2026-104570

CVE-2026-71891

·

Published

2026-10-03

·

Updated

2026-10-26

Description by

CVSS 4.0
7.1
High
MetricsAV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber
Name of the Vulnerable Software and Affected Versions Bouncy Castle for Java versions prior to 1.86
Description An issue exists in the BLS12 381BasicScheme.keyValidate function, affecting BLSPublicKeyParameters and the verify and aggregateVerify methods of BasicScheme, MessageAugmentation, and ProofOfPossession. The system accepts public keys built on a foreign ECCurve that shares the field characteristic of BLS12-381. Because the prime-order subgroup check relies on the point's own curve to define its cofactor, a point on a curve with a different equation and a forged cofactor of one can bypass keyValidate without being a valid G1 point. In the pairing implementation, such a point contributes the identity in the target group, allowing an aggregate signature to be accepted even if it lacks a signature for that specific key and message pair, effectively permitting a phantom signer. This is only reachable if an application constructs an ECPoint on an explicit, non-canonical curve and accepts it as an authority-bearing key.
Recommendations Update Bouncy Castle for Java to version 1.86 or later.
Exploitability
Exploit
Fix
Impacts
Researchers
Vendors
Affected products
Related identifiers
CLEANSTART-2026-DK36206
CLEANSTART-2026-HW07490
CLEANSTART-2026-KF30791
OPENSUSE-SU-2026:12090-1
OPENSUSE-SU-2026:22169-1
SUSE-SU-2026:24461-1
SUSE-SU-2026:4797-1
Found an issue in the description? Have something to add? Feel free to write us 👾