BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-13506High confidence

Lazy ASN.1 sequence forcing resets nesting-depth guard

Legion of the Bouncy Castle Inc. · BC-JAVA

8.7HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 35 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.44% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Legion of the Bouncy Castle Inc. BC-JAVA and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 35 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Package result overrides the generic status

BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.

Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcebouncycastleAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourcebouncycastleAffected, no fix publishedDebian currently tracks this release as open.Not published in this feedDebian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourcebouncycastleVendor fix publishedDebian records a fixed source-package version for this release.1.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourcebouncycastleVendor fix publishedDebian records a fixed source-package version for this release.1.86-1Debian Security Tracker ↗Source updated 6 Oct 2026
Ubuntu 24.04 LTSnoble · esm-appsbouncycastleUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges12 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.bouncycastle:bc-fipsECOSYSTEM: introduced 0; fixed 1.0.2.71.0.2.7OSV record ↗aggregator derived · 18 Sep 2026
Mavenorg.bouncycastle:bc-fipsECOSYSTEM: introduced 2.0.0; fixed 2.0.22.0.2OSV record ↗aggregator derived · 18 Sep 2026
Mavenorg.bouncycastle:bc-fipsECOSYSTEM: introduced 2.1.0; fixed 2.1.32.1.3OSV record ↗aggregator derived · 18 Sep 2026
Mavenorg.bouncycastle:bcprov-jdk15to18ECOSYSTEM: introduced 0; fixed 1.851.85OSV record ↗aggregator derived · 18 Sep 2026
Mavenorg.bouncycastle:bcprov-jdk18onECOSYSTEM: introduced 0; fixed 1.851.85OSV record ↗aggregator derived · 18 Sep 2026
Mavenorg.bouncycastle:bcprov-lts8onECOSYSTEM: introduced 0; fixed 2.73.122.73.12OSV record ↗aggregator derived · 18 Sep 2026
mavenorg.bouncycastle:bc-fips< 1.0.2.71.0.2.7GitHub advisory ↗github reviewed aggregator · 18 Sep 2026
mavenorg.bouncycastle:bc-fips>= 2.0.0, < 2.0.22.0.2GitHub advisory ↗github reviewed aggregator · 18 Sep 2026
mavenorg.bouncycastle:bc-fips>= 2.1.0, < 2.1.32.1.3GitHub advisory ↗github reviewed aggregator · 18 Sep 2026
mavenorg.bouncycastle:bcprov-jdk15to18< 1.851.85GitHub advisory ↗github reviewed aggregator · 18 Sep 2026
mavenorg.bouncycastle:bcprov-jdk18on< 1.851.85GitHub advisory ↗github reviewed aggregator · 18 Sep 2026
mavenorg.bouncycastle:bcprov-lts8on< 2.73.122.73.12GitHub advisory ↗github reviewed aggregator · 18 Sep 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-13506 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitybouncycastle: Bouncy Castle for Java: Denial of Service via lazy ASN.1 sequence processing
14 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • bcprov-jdk18on as a component of Red Hat AMQ Broker 7
  • bcprov-jdk18on as a component of Red Hat build of Apache Camel for Spring Boot 4
  • bcprov-jdk18on as a component of Red Hat build of Apicurio Registry 3
  • bcprov-jdk18on as a component of Red Hat Build of Keycloak
  • rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak
  • bcmail-jdk18on as a component of Red Hat Fuse 7
  • bcprov-jdk18on as a component of Red Hat Fuse 7
  • bcmail-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7
  • bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7
  • jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7
  • jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7
  • jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7
Summary
A flaw was found in Bouncy Castle for Java. A remote attacker could exploit a vulnerability related to how the software processes lazy ASN.1 sequences, which can reset an internal nesting-depth guard. This issue could lead to a Denial of Service (DoS), making the affected system or application unavailable.
Remediation
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-52139

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 35 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

In Bouncy Castle for Java before 1.85, Lazy ASN.1 sequence forcing resets nesting-depth guard. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

What

In Bouncy Castle for Java before 1.85, Lazy ASN.1 sequence forcing resets nesting-depth guard. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

What

In Bouncy Castle for Java before 1.85, Lazy ASN.1 sequence forcing resets nesting-depth guard. This issue also affects Bouncy Castle for Java LTS before 2.73.12, and Bouncy Castle for Java FIPS (BC-FJA) before bc-fips 1.0.2.7 (1.0.X series), 2.0.2 (2.0.X series) and 2.1.3 (2.1.X series).

Why

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Uncontrolled Recursion → cause the confidentiality, integrity or availability impact described by the vendor
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
Low: no specialised conditions are recorded
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-674 ↗

CWE-674: Uncontrolled Recursion. The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedCWE-674
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-3595IBM QRadar SIEM: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM QRadar SIEM ausnutzen, um beliebigen Programmcode auszuführen, um seine Privilegien zu erhöhen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-3376Atlassian Bamboo, Bitbucket, Confluence, Fisheye/Crucible, Jira Software und Jira Service Management: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Bitbucket, Confluence, Fisheye/Crucible, Jira Software und Jira Service Management ausnutzen, um beliebigen Programmcode auszuführen, Sicherheitsmaßnahmen zu umgehen, serverseitige Request-Forgery-Angriffe (SSRF) durchzuführen, Cross-Site-Scripting-Angriffe zu starten, sensible Informationen offenzulegen, Daten zu manipulieren oder Denial-of-Service-Zustände herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2026-2958IBM License Metric Tool: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in IBM License Metric Tool ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2923Atlassian Produkte (Bamboo, Bitbucket, Confluence, Crucible, Fisheye, und Jira): Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Atlassian Bamboo, Atlassian Bitbucket, Atlassian Confluence, Atlassian Crucible, Atlassian Fisheye und Atlassian Jira ausnutzen, um beliebigen Programmcode auszuführen, um einen Denial of Service Angriff durchzuführen, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuführen, um einen SQL-Injection Angriff durchzuführen, und um Sicherheitsvorkehrungen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2026-2622Bouncy Castle: Mehrere Schwachstellen

Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Bouncy Castle ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Daten zu manipulieren, sensible Informationen offenzulegen oder einen Denial-of-Service-Zustand auszulösen.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260805Security Bulletin 5 Aug 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 5 Aug 2026, published on 5 August 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
INCIBE-CERT · Spanish · boletin-de-seguridad-de-atlassian-agosto-de-2026Boletín de seguridad de Atlassian: agosto de 2026

ación de estas dependencias por parte de Atlassian presenta un riesgo menor, no crítico, según la evaluación realizada. A continuación, se detallan las vulnerabilidades de severidad alta que afectan a Atlassian: CVE-2026-14682: RCE (Remote Code Execution) en org.bouncycastle:bcprov-jdk18on. CVE-2026-12143: RCE (Remote Code Execution) en form-data. CVE-2026-58059: DoS (Denial of Service) en org.bouncycastle:bcprov-jdk18on. CVE-2026-12802: Fallo criptográfico en org.bouncycastle:bcpkix-jdk18on. CVE-2026-58060: RCE (Remote Code Execution) en org.bouncycastle:bcprov-jdk18on. CVE-2026-12803: Fallo criptográfico en org.bouncycastle:bcprov-jdk18on. CVE-2026-13506: DoS (Denial of Service) en org.bouncycastle:bcprov-jdk18on. CVE-2026-56745: DoS (Denial of Service) en io.netty:netty-codec-http. CVE-2026-59639: Fallo criptográfico en org.bouncycastle:bcpkix-jdk18on. CVE-2026-12816: Fallo criptográfico en org.bouncycastle:bcprov-jdk18on. CVE-2026-59901: DoS (Denial of Service) en io.netty:netty-codec. CVE-2026-59642: Fallo criptográfico en org.bouncycastle:bcpkix-jdk18on. CVE-2026-0603: SQLi (SQL Injection) en org.hibernate:hibernate-core-jakarta. CVE-2026-67320: Divulgación de información en axios. CVE-2026-54291: MITM (Man-in-the-Middle) en org.postgresql:postgresql. CVE-2026-41907: RCE (Remote Code Exe

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

d?id=CVE-2026-11824 Référence CVE CVE-2026-11940 https://www.cve.org/CVERecord?id=CVE-2026-11940 Référence CVE CVE-2026-11972 https://www.cve.org/CVERecord?id=CVE-2026-11972 Référence CVE CVE-2026-11979 https://www.cve.org/CVERecord?id=CVE-2026-11979 Référence CVE CVE-2026-12003 https://www.cve.org/CVERecord?id=CVE-2026-12003 Référence CVE CVE-2026-12087 https://www.cve.org/CVERecord?id=CVE-2026-12087 Référence CVE CVE-2026-12912 https://www.cve.org/CVERecord?id=CVE-2026-12912 Référence CVE CVE-2026-13221 https://www.cve.org/CVERecord?id=CVE-2026-13221 Référence CVE CVE-2026-13346 https://www.cve.org/CVERecord?id=CVE-2026-13346 Référence CVE CVE-2026-13506 https://www.cve.org/CVERecord?id=CVE-2026-13506 Référence CVE CVE-2026-13595 https://www.cve.org/CVERecord?id=CVE-2026-13595 Référence CVE CVE-2026-13757 https://www.cve.org/CVERecord?id=CVE-2026-13757 Référence CVE CVE-2026-14164 https://www.cve.org/CVERecord?id=CVE-2026-14164 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14456 https://www.cve.org/CVERecord?id=CVE-2026-14456 Référence CVE CVE-2026-14457 https://www.cve.org/CVERecord?id=CVE-2026-14457 Référence CVE CVE-2026-15308 https://www.cve.org/CVERecord?id=CVE-2026-15308 Référence CVE CVE-2026-15310 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1256Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-12185 Référence CVE CVE-2026-12590 https://www.cve.org/CVERecord?id=CVE-2026-12590 Référence CVE CVE-2026-12802 https://www.cve.org/CVERecord?id=CVE-2026-12802 Référence CVE CVE-2026-12803 https://www.cve.org/CVERecord?id=CVE-2026-12803 Référence CVE CVE-2026-12816 https://www.cve.org/CVERecord?id=CVE-2026-12816 Référence CVE CVE-2026-12860 https://www.cve.org/CVERecord?id=CVE-2026-12860 Référence CVE CVE-2026-13149 https://www.cve.org/CVERecord?id=CVE-2026-13149 Référence CVE CVE-2026-13204 https://www.cve.org/CVERecord?id=CVE-2026-13204 Référence CVE CVE-2026-13321 https://www.cve.org/CVERecord?id=CVE-2026-13321 Référence CVE CVE-2026-13506 https://www.cve.org/CVERecord?id=CVE-2026-13506 Référence CVE CVE-2026-13586 https://www.cve.org/CVERecord?id=CVE-2026-13586 Référence CVE CVE-2026-13676 https://www.cve.org/CVERecord?id=CVE-2026-13676 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14682 https://www.cve.org/CVERecord?id=CVE-2026-14682 Référence CVE CVE-2026-15055 https://www.cve.org/CVERecord?id=CVE-2026-15055 Référence CVE CVE-2026-15588 https://www.cve.org/CVERecord?id=CVE-2026-15588 Référence CVE CVE-2026-15603 https://www.cve.org/CVERecord?id=CVE-2026-15603 Référence CVE CVE-2026-15816 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1233Multiples vulnérabilités dans les produits IBM

d?id=CVE-2025-71330 Référence CVE CVE-2026-12185 https://www.cve.org/CVERecord?id=CVE-2026-12185 Référence CVE CVE-2026-12590 https://www.cve.org/CVERecord?id=CVE-2026-12590 Référence CVE CVE-2026-12803 https://www.cve.org/CVERecord?id=CVE-2026-12803 Référence CVE CVE-2026-12816 https://www.cve.org/CVERecord?id=CVE-2026-12816 Référence CVE CVE-2026-12860 https://www.cve.org/CVERecord?id=CVE-2026-12860 Référence CVE CVE-2026-13149 https://www.cve.org/CVERecord?id=CVE-2026-13149 Référence CVE CVE-2026-13311 https://www.cve.org/CVERecord?id=CVE-2026-13311 Référence CVE CVE-2026-13505 https://www.cve.org/CVERecord?id=CVE-2026-13505 Référence CVE CVE-2026-13506 https://www.cve.org/CVERecord?id=CVE-2026-13506 Référence CVE CVE-2026-13586 https://www.cve.org/CVERecord?id=CVE-2026-13586 Référence CVE CVE-2026-13676 https://www.cve.org/CVERecord?id=CVE-2026-13676 Référence CVE CVE-2026-13697 https://www.cve.org/CVERecord?id=CVE-2026-13697 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14620 https://www.cve.org/CVERecord?id=CVE-2026-14620 Référence CVE CVE-2026-14631 https://www.cve.org/CVERecord?id=CVE-2026-14631 Référence CVE CVE-2026-14643 https://www.cve.org/CVERecord?id=CVE-2026-14643 Référence CVE CVE-2026-14682 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1165Multiples vulnérabilités dans les produits IBM

d?id=CVE-2026-12143 Référence CVE CVE-2026-12185 https://www.cve.org/CVERecord?id=CVE-2026-12185 Référence CVE CVE-2026-12590 https://www.cve.org/CVERecord?id=CVE-2026-12590 Référence CVE CVE-2026-12802 https://www.cve.org/CVERecord?id=CVE-2026-12802 Référence CVE CVE-2026-12803 https://www.cve.org/CVERecord?id=CVE-2026-12803 Référence CVE CVE-2026-12816 https://www.cve.org/CVERecord?id=CVE-2026-12816 Référence CVE CVE-2026-12860 https://www.cve.org/CVERecord?id=CVE-2026-12860 Référence CVE CVE-2026-13006 https://www.cve.org/CVERecord?id=CVE-2026-13006 Référence CVE CVE-2026-13149 https://www.cve.org/CVERecord?id=CVE-2026-13149 Référence CVE CVE-2026-13506 https://www.cve.org/CVERecord?id=CVE-2026-13506 Référence CVE CVE-2026-13586 https://www.cve.org/CVERecord?id=CVE-2026-13586 Référence CVE CVE-2026-13676 https://www.cve.org/CVERecord?id=CVE-2026-13676 Référence CVE CVE-2026-14257 https://www.cve.org/CVERecord?id=CVE-2026-14257 Référence CVE CVE-2026-14525 https://www.cve.org/CVERecord?id=CVE-2026-14525 Référence CVE CVE-2026-14529 https://www.cve.org/CVERecord?id=CVE-2026-14529 Référence CVE CVE-2026-14682 https://www.cve.org/CVERecord?id=CVE-2026-14682 Référence CVE CVE-2026-14683 https://www.cve.org/CVERecord?id=CVE-2026-14683 Référence CVE CVE-2026-14684 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-030984Bouncy Castleのbc-java等の複数製品における再帰制御に関する脆弱性

1.85より前のBouncy Castle for Javaでは、Lazy ASN.1シーケンスの強制がネスティング深度ガードをリセットしてしまう問題があります。この問題は、2.73.12以前のBouncy Castle for Java LTS、およびbc-fips 1.0.2.7(1.0.Xシリーズ)、2.0.2(2.0.Xシリーズ)、2.1.3(2.1.Xシリーズ)より前のBouncy Castle for Java FIPS(BC-FJA)にも影響を及ぼします。

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0325Kwetsbaarheden verholpen in Atlassian producten

Bouncy Castle for Java versions prior to 1.85, including certain LTS and FIPS releases, contains a vulnerability where lazy ASN.1 sequence forcing resets the nesting-depth guard, potentially compromising security controls.

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
Official vendor articles2 stored documents

Linked articles are downloaded and versioned as source evidence. A CVE mention or approved update relationship does not, by itself, verify a fix for every product branch.

04

Evidence and provenance

Published 3 Aug 2026 · Last source change 3 Aug 2026, 15:09 UTC · CWE-674 · Uncontrolled Recursion

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-52139
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    bcprov-jdk18on as a component of Red Hat AMQ Broker 7; bcprov-jdk18on as a component of Red Hat build of Apache Camel for Spring Boot 4; bcprov-jdk18on as a component of Red Hat build of Apicurio Registry 3; bcprov-jdk18on as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; bcmail-jdk18on as a component of Red Hat Fuse 7; bcprov-jdk18on as a component of Red Hat Fuse 7; bcmail-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 8; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; bcprov-jdk18on as a component of Red Hat Single Sign-On 7
    After
    bcprov-jdk18on as a component of Red Hat AMQ Broker 7; bcprov-jdk18on as a component of Red Hat build of Apache Camel for Spring Boot 4; bcprov-jdk18on as a component of Red Hat build of Apicurio Registry 3; bcprov-jdk18on as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; bcmail-jdk18on as a component of Red Hat Fuse 7; bcprov-jdk18on as a component of Red Hat Fuse 7; bcmail-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 8; bcprov-jdk18on as a component of Red Hat Single Sign-On 7
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    bcmail-jdk18on as a component of Red Hat Fuse 7; bcmail-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7
    After
    bcprov-jdk18on as a component of Red Hat AMQ Broker 7; bcprov-jdk18on as a component of Red Hat build of Apache Camel for Spring Boot 4; bcprov-jdk18on as a component of Red Hat build of Apicurio Registry 3; bcprov-jdk18on as a component of Red Hat Build of Keycloak; rhbk/keycloak-rhel9 as a component of Red Hat Build of Keycloak; bcmail-jdk18on as a component of Red Hat Fuse 7; bcprov-jdk18on as a component of Red Hat Fuse 7; bcmail-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk11-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk17-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; jboss-eap-7/eap74-els-openjdk8-openshift-rhel8 as a component of Red Hat JBoss Enterprise Application Platform 7; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform 8; bcprov-jdk18on as a component of Red Hat JBoss Enterprise Application Platform Expansion Pack; bcprov-jdk18on as a component of Red Hat Single Sign-On 7
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed: added patch: github.com/77454da9b3dcaaa2991412d1c3c1a6e1a338ff84; added remediation: github.com/77454da9b3dcaaa2991412d1c3c1a6e1a338ff84.
    Before
    no authoritative guidance recorded
    After
    patch: github.com/77454da9b3dcaaa2991412d1c3c1a6e1a338ff84 · remediation: github.com/77454da9b3dcaaa2991412d1c3c1a6e1a338ff84
    github.com ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    < 1.85; 2.73.0 < 2.73.12; 1.0.0 < 1.0.2.7; 2.0.0 < 2.0.2; 2.1.0 < 2.1.3 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    < 1.85; 2.73.0 < 2.73.12; 1.0.0 < 1.0.2.7; 2.0.0 < 2.0.2; 2.1.0 < 2.1.3 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
  5. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    github.com ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-13506 · cve.blacktree.nl