Skip to main content

Threats Tagged 'cve-2026-63571'

View all threats tagged with 'cve-2026-63571'. 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-63571

Threats Tagged 'cve-2026-63571'

Click on any threat for detailed analysis and mitigation recommendations

A vulnerability in the Legion of the Bouncy Castle Inc. bc-csharp library before version 2.7.0 allows improper verification of cryptographic signatures in the attribute certificate path validator. This flaw permits a remote attacker to present a forged X.509 attribute certificate that is accepted as valid, potentially granting unauthorized roles or privileges. The issue arises because the validation process checks certification paths, validity periods, extensions, and revocation status but fails to verify the attribute certificate's signature using the issuer's public key. Only applications using the affected classes for attribute certificate validation are impacted.

Join the discussion

Improper verification of cryptographic signature in the attribute certificate path validator (PkixAttrCertPathValidator, also used by PkixAttrCertPathBuilder) in Legion of the Bouncy Castle Inc. bc-csharp before 2.7.0 allows a remote attacker to have a forged X.509 attribute certificate accepted as valid, and so obtain whatever roles or privileges an application grants on the strength of its attributes, via an attribute certificate that names a trusted attribute authority as its issuer but was not signed by it, because the RFC 3281 validation steps check the holder and issuer certification paths, validity period, extensions and revocation status but never verify the attribute certificate's signature with the issuer's public key. Only applications that use these classes to validate attribute certificates are affected.

Join the discussion

Showing 1 to 2 of 2 results

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

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses