cve.bz

CVE-2026-85515 legion of the bouncy castle inc.

8.2 highEPSS 0.2%

High (8.2) in legion of the bouncy castle inc.. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
In Bouncy Castle for Java before 1.86, a truncated OpenPGP encrypted message was accepted with no error reported, and on the SEIPD version 1 path with no integrity check performed at all. RFC 9580 sec. 13.7 permits an implementation to release the cleartext of the fully authenticated chunks when streaming but requires it to indicate a clear error as soon as the truncation is detected, and to report suspect integrity when it discovers malleable ciphertext. The truncation was detected and then discarded: when a message is truncated but the length field of the enclosing packet is left unchanged, BCPGInputStream.PartialInputStream raises an EOFException for the missing ciphertext, and BCPGInputStream.nextPacketTag() reports an EOFException as a clean end of message, so the packet stream above it stopped as though no packets remained. On the AEAD path (SEIPD version 2 and the version 5 AEAD packet), when the literal data packet ended on an AEAD chunk boundary and the consumer read in increments smaller than one chunk, the look-ahead for the packet after the literal triggered the truncated chunk read, so BcAEADUtil and JceAEADUtil never reached the trailing message tag of sec. 5.13.2 that authenticates the total plaintext length; the caller received the plaintext of the fully authenticated chunks, every packet following the literal was silently dropped, and no exception was raised, so a signed and encrypted message read back as a well-formed unsigned one. Every byte released on that path remained individually authenticated, making this a missing truncation error rather than a forgery, and it is a residual of CVE-2026-12817, which closed the same outcome for an attacker who corrects the outer packet length. On the SEIPD version 1 path the consequence was more serious: IntegrityProtectedInputStream verifies the modification detection code from close(), and reached close() only by closing itself when a read of it returned -1, which a truncated message never produces, so PGPEncryptedData.verify() never ran and the recipient was handed CFB-decrypted plaintext on which no integrity check of any kind had been performed. Measured on a message truncated into that shape, 136 distinct single-byte modifications of the ciphertext produced accepted, altered plaintext with no exception raised. Reachability is a property of the message rather than of attacker-supplied input: the AEAD shape held for 3 of 131 consecutive payload lengths measured, and the SEIPD version 1 shape for one payload length in sixteen, at a truncation offset that did not move with the payload length. The low-level API is unaffected, a caller that invokes PGPEncryptedData.verify() directly getting the check regardless, as are consumers reading in increments of a whole AEAD chunk or more. The AEAD decryption streams now re-throw such an EOFException as a plain IOException, which nextPacketTag() does not launder; OpenPGPMessageInputStream.close() now closes its layer's integrity-protected stream itself rather than relying on that stream having seen the end of its data; and IntegrityProtectedInputStream.close() was made idempotent, as java.io.Closeable requires, which that depends on, since the stream is genuinely closed twice on the ordinary path and PGPEncryptedData.verify() consumes the digest state behind it and cannot be run a second time. This issue also affects Bouncy Castle for Java LTS before 2.73.13, on the AEAD route only, as that edition does not ship the high-level OpenPGP API the SEIPDv1 route runs through. It also affects Bouncy Castle for Java FIPS (BC-FJA) before bcpg-fips 1.0.14 (1.0.X series), 2.0.14.1 (2.0.X series) and 2.1.14 (2.1.X series), on the AEAD route only, as those editions do not ship the high-level OpenPGP API.

Severity

CVSS 4.0

8.2 high
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/U:Amber
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-05. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-345 Insufficient Verification of Data Authenticity
CWE-354 Improper Validation of Integrity Check Value
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-85515 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-85515?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-85515?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-85515 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • legion of the bouncy castle inc.:bc-fja
  • legion of the bouncy castle inc.:bc-java
  • legion of the bouncy castle inc.:bc-lts-java

Versions

From the CNA's record in the CVE List.

ProductAffected
Legion of the Bouncy Castle Inc. BC-JAVAfrom 1.74 before 1.86
Legion of the Bouncy Castle Inc. BC-LTS-JAVAfrom 2.73.0 before 2.73.13
Legion of the Bouncy Castle Inc. BC-FJAfrom 1.0.7 before 1.0.14
Legion of the Bouncy Castle Inc. BC-FJAfrom 2.0.7 before 2.0.14.1
Legion of the Bouncy Castle Inc. BC-FJAfrom 2.1.0 before 2.1.14

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13bouncycastleno fix listedDEBIAN-CVE-2026-85515
Debian14bouncycastle1.86-1DEBIAN-CVE-2026-85515
Ubuntu26.04:LTS, 26.10, Pro:16.04:LTS and 4 morebouncycastleno fix listedUBUNTU-CVE-2026-85515
SUSELinux Enterprise High Performance Computing 15 SP4-ESPOS, Linux Enterprise High Performance Computing 15 SP4-LTSS, Linux Enterprise High Performance Computing 15 SP5-ESPOS and 8 morebouncycastle1.86-150200.3.41.1SUSE-SU-2026:4797-1
SUSELinux Enterprise Server 16.0, Linux Enterprise Server for SAP applications 16.0bouncycastle1.86-160000.1.1SUSE-SU-2026:24461-1
openSUSELeap 16.0bouncycastle1.86-160000.1.1openSUSE-SU-2026:22169-1
openSUSETumbleweedbouncycastle1.86-1.1openSUSE-SU-2026:12090-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · SUSE · openSUSE.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because successful exploitation depends on strict message length constraints and requires an adversary positioned to manipulate network traffic in transit. Within Red Hat products embedding Bouncy Castle, applications streaming OpenPGP data through high-level APIs may consume incomplete ciphertext sequences without triggering cryptographic authentication checks. However, low-level decryption routines that explicitly enforce integrity verification remain unaffected, limiting the overall attack surface across typical deployments.

Red Hat's mitigation

Upgrade to Bouncy Castle for Java bcpg 1.86 (or BC-LTS 2.73.13 / BC-FJA bcpg-fips 1.0.14, 2.0.14.1, 2.1.14 as applicable); as a workaround, use the low-level API or whole-chunk readers, which are unaffected, and reject truncated OpenPGP messages.

ProductPackageStateAdvisory
OpenShift Developer Tools and ServicesjenkinsOut of support scope
OpenShift Developer Tools and Servicesjenkins-2-pluginsOut of support scope
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel8Out of support scope
OpenShift Developer Tools and Servicesocp-tools-4/jenkins-rhel9Out of support scope
Red Hat build of Apache Camel 4 for Quarkus 3bcpg-jdk18onFix deferred
Red Hat Enterprise Linux 9jmcFix deferred
Red Hat Fuse 7bcpg-jdk15onOut of support scope
Red Hat Fuse 7bcpg-jdk18onOut of support scope
Red Hat JBoss Enterprise Application Platform 7bcpg-jdk15onOut of support scope
Red Hat JBoss Enterprise Application Platform 7bcpg-jdk18onOut of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk11-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk17-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 7jboss-eap-7/eap74-els-openjdk8-openshift-rhel8Out of support scope
Red Hat JBoss Enterprise Application Platform 8bcpg-jdk18onFix deferred
Red Hat JBoss Enterprise Application Platform Expansion Packbcpg-jdk18onFix deferred
Red Hat Single Sign-On 7bcpg-jdk18onOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-85515.

Attack patterns (CAPEC)

  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-145 Checksum Spoofing Severity: Medium
  • CAPEC-463 Padding Oracle Crypto Attack Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON