How many CVEs have patched parse?

2 published CVEs changed parse in bcgit/bc-java, in 3 distinct patches totalling 28 changed lines, between 2024 and 2026.

What is the latest CVE that changed parse?

CVE-2026-59645 (OER parser recurses without depth limit on self-referential IEEE 1609.2 schema), published 2026-08-03, changed lines 152 to 159 of util/src/main/java/org/bouncycastle/oer/OERInputStream.java.

How does parse compare to the rest of bcgit/bc-java?

bcgit/bc-java has 73 CVEs with a located fix in total; 2 of them changed parse.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

bcgit/bc-java

Function

3 files

parse

Name: parse in bcgit/bc-java: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

Defined in 3 files

Last patched August 3, 2026

2

CVEs

That changed this function

3

Distinct patches

Backports counted once

28

Lines changed

Added plus removed

2024–2026

Years

By CVE publication date

Overview

parse in bcgit/bc-java was changed by 2 published CVE fixes between 2024 and 2026, in 3 distinct patches that added or removed 28 lines in total.

The name occurs in 3 files: core/src/main/java/org/bouncycastle/crypto/params/Ed448PublicKeyParameters.java, core/src/main/java/org/bouncycastle/crypto/params/Ed25519PublicKeyParameters.java, util/src/main/java/org/bouncycastle/oer/OERInputStream.java.

bcgit/bc-java has 73 CVEs with a located fix in total, so 3% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed parse, newest first, with the lines each fix touched.

OER parser recurses without depth limit on self-referential IEEE 1609.2 schema
CVE-2026-59645 · util/src/main/java/org/bouncycastle/oer/OERInputStream.java · lines 152–159 · +8 −0
High · CVSS 8.7
EPSS 0.5%2026-08-03
Bouncy Castle crafted signature and public key can be used to trigger an infinite loop
CVE-2024-30172 · core/src/main/java/org/bouncycastle/crypto/params/Ed25519PublicKeyParameters.java · lines 117–126 · +10 −0
Medium · CVSS 6.9
EPSS 0.8%2024-05-09
Bouncy Castle crafted signature and public key can be used to trigger an infinite loop
CVE-2024-30172 · core/src/main/java/org/bouncycastle/crypto/params/Ed448PublicKeyParameters.java · lines 108–117 · +10 −0
Medium · CVSS 6.9
EPSS 0.8%2024-05-09

Get an alert when the next CVE fix lands in bcgit/bc-java, with the patched functions.

Monitor bc-java CVEs

Other functions in these files

Functions in the same files that CVE fixes also changed.

Other hotspots in the repository

Functions in bcgit/bc-java changed by the most CVE fixes.

engineDoFinal3 CVEs · prov/src/main/java/org/bouncycastle/jcajce/provider/asymmetric/dh/IESCipher.java checkNameConstraints2 CVEs · pkix/src/main/java/org/bouncycastle/pkix/jcajce/PKIXCertPathReviewer.java processPacket2 CVEs · core/src/main/java/org/bouncycastle/crypto/modes/KCCMBlockCipher.java checkNameConstraints2 CVEs · prov/src/main/java/org/bouncycastle/x509/PKIXCertPathReviewer.java readBlock2 CVEs · pg/src/main/java/org/bouncycastle/openpgp/operator/bc/BcAEADUtil.java readBlock2 CVEs · pg/src/main/java/org/bouncycastle/openpgp/operator/jcajce/JceAEADUtil.java

All patched functions in bcgit/bc-java

Frequently asked questions

Common questions about CVE fixes to parse.

How many CVEs have patched parse?: 2 published CVEs changed parse in bcgit/bc-java, in 3 distinct patches totalling 28 changed lines, between 2024 and 2026.
What is the latest CVE that changed parse?: CVE-2026-59645 (OER parser recurses without depth limit on self-referential IEEE 1609.2 schema), published 2026-08-03, changed lines 152 to 159 of util/src/main/java/org/bouncycastle/oer/OERInputStream.java.
How does parse compare to the rest of bcgit/bc-java?: bcgit/bc-java has 73 CVEs with a located fix in total; 2 of them changed parse.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track bcgit/bc-java CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing