Skip to content
Noroxi
CVE-2026-59645· NVD / CVE Program· CNA bcorg

OER parser recurses without depth limit on self-referential IEEE 1609.2 schema

In Bouncy Castle for Java before 1.85, OER parser recurses without depth limit on self-referential IEEE 1609.2 schema. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bcutil-fips 2.0.7 (2.0.X series) and 2.1.7 (2.1.X series).

HighCVSS 8.7 · v4.0—No exploit Fix available
Published
Aug 2, 2026
Updated
Aug 28, 2026
EPSS
0.5% · 40th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

34

Monitor

Low priority for now.

CVSS
34 / 40 · 8.7 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.5%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · bcorg
8.7
NVD has not scored this yet; the score shown is the CNA’s.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/U:Amber

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
bouncycastlebc-java
bouncycastlebcutil-fips
bouncycastlebouncy castle for java lts

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • bouncycastle bc-javabefore 1.85
  • bouncycastle bcutil-fips2.0.2 and later · before 2.0.7
  • bouncycastle bcutil-fips2.1.4 and later · before 2.1.7
  • bouncycastle bouncy castle for java ltsup to 2.73.11 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (bcorg). Independent of NVD's CPE analysis and usually ahead of it.

  • Legion of the Bouncy Castle Inc. BC-FJA

    • 2.0.0 and later · before 2.0.7affected · maven
    • 2.1.0 and later · before 2.1.7affected · maven

  • Legion of the Bouncy Castle Inc. BC-JAVA

    • 1.70 and later · before 1.85affected · maven

  • Legion of the Bouncy Castle Inc. BC-LTS-JAVA

    • 2.73.0 and later · before 2.73.12affected · maven

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12bouncycastleall versions—

Same product

bouncycastle: all records

Other highest-scoring records for the same primary product.

  • CVE-2007-6721The Legion of the Bouncy Castle Java Cryptography API before release 1.38, as used in Crypto Provider Package before 1.36, has unknown impac
    41Plan
  • CVE-2018-1000613Legion of the Bouncy Castle Legion of the Bouncy Castle Java Cryptography APIs 1.58 up to but not including 1.60 contains a CWE-470: Use of
    40Plan
  • CVE-2026-58062Stapled OCSP response accepted without binding to the checked certificate
    37Monitor
  • CVE-2026-8763Name Constraints bypass via trailing dot in rfc822Name and URI
    37Monitor
  • CVE-2026-59650MTI/A0 DH agreement exponentiates unvalidated peer value
    37Monitor
  • CVE-2026-59638JSSE hostname verifier CN-fallback enabled by default despite documented opt-in
    37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Legion of the Bouncy Castle Inc. BC-FJA2.0.7Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-FJA2.1.7Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-JAVA1.85Vendor (CNA)
Legion of the Bouncy Castle Inc. BC-LTS-JAVA2.73.12Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-135061 days apartLazy ASN.1 sequence forcing resets nesting-depth guard
    34Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
X

Weakness class (CWE)

CWE-674 · Uncontrolled Recursion

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records