Skip to main content

Threats Tagged 'cve-2026-71891'

View all threats tagged with 'cve-2026-71891'. Filter and sort to focus on specific types of threats.

Pro Console Lifetime

Stop chasing alerts. Route them.

Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.

Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)

View Plans & Pricing

API access activates after upgrading in Console -> Billing.

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now

Filter Threats

Narrow down the results by type, severity, or affected countries

Search threats by title, CVE ID, or description. Maximum 100 characters.
Active filters (1):Tag: cve-2026-71891

Threats Tagged 'cve-2026-71891'

Click on any threat for detailed analysis and mitigation recommendations

A vulnerability in Bouncy Castle for Java before version 1.86 allows acceptance of a public key constructed on a non-canonical elliptic curve that shares the BLS12-381 field characteristic but is not a valid G1 point. This flaw affects key validation in BLS12_381BasicScheme and related classes, enabling aggregate signature verification to accept signatures including phantom signers. The issue arises only if an application explicitly constructs ECPoints on non-canonical curves and accepts them as valid keys; the standard compressed-point decoder is unaffected.

Join the discussion

CVE-2026-71891 is a high-severity vulnerability in Bouncy Castle for Java versions 1.85 up to but not including 1.86. It involves improper verification of cryptographic signatures due to acceptance of public keys constructed on non-canonical elliptic curves that share the field characteristic of BLS12-381 but differ in curve parameters. This flaw allows an attacker to create a phantom signer in aggregate signature verification, bypassing proper subgroup checks. The vulnerability is only exploitable if an application explicitly constructs ECPoints on non-standard curves and uses them as authority keys; the standard compressed-point decoder is unaffected. The issue has been addressed by adding strict validation of the curve parameters before subgroup checks.

Join the discussion

Showing 1 to 2 of 2 results

Filters:Tag: cve-2026-71891
Page 1 of 1
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses