Security Resilience

CVE-2026-12803

Bouncycastle Bc-Java ≤ 1.85

Published
03 August 2026
Modified
02 September 2026
Patch / advisory
CVSS Score v4 8.7
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/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
EPSS Score 0.0024 15th percentile
Risk Priority 43 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-12803 is a high-severity Improper Validation of Integrity Check Value (CWE-354) vulnerability in Bouncycastle Bc-Java. Its CVSS base score is 8.7 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Compromise Infrastructure (T1584); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Bouncy Castle for Java before 1.85, KCCMBlockCipher MAC does not bind nonce when AAD is absent (cross-nonce AEAD forgery). This issue also affects Bouncy Castle for Java LTS before 2.73.12.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1584 Compromise Infrastructure Resource Development
Adversaries may compromise third-party infrastructure that can be used during targeting.
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
T1542.001 System Firmware Stealth
Adversaries may modify system firmware to persist on systems.
T1542.002 Component Firmware Stealth
Adversaries may modify component firmware to persist on systems.
T1542.004 ROMMONkit Stealth
Adversaries may abuse the ROM Monitor (ROMMON) by loading an unauthorized firmware with adversary code to provide persistent access and manipulate device behavior that is difficult to detect.
T1565.002 Transmitted Data Manipulation Impact
Adversaries may alter data en route to storage or other systems in order to manipulate external outcomes or hide activity, thus threatening the integrity of the data.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-12816Same product: Bouncycastle Bc-Java
CVE-2026-59642Same product: Bouncycastle Bc-Java
CVE-2026-58061Same product: Bouncycastle Bc-Java
CVE-2026-12817Same product: Bouncycastle Bc-Java
CVE-2026-12802Same product: Bouncycastle Bc-Java
CVE-2026-12860Same product: Bouncycastle Bc-Java
CVE-2026-59651Same product: Bouncycastle Bc-Java
CVE-2026-12185Same product: Bouncycastle Bc-Java
CVE-2026-103601Same vendor: Bouncycastle
CVE-2026-59650Same product: Bouncycastle Bc-Java

Affected Assets

bouncycastle
bc-java
≤ 1.85
bouncycastle
bouncy castle for java lts
≤ 2.73.11

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 10 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V10.4.12

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Requires integrity verification tools that detect unauthorized changes when checksum validation is missing or flawed.

Mandates cryptographic mechanisms that include integrity protection, preventing improper checksum validation.

Requires protection of transmitted information integrity, directly mandating correct validation of integrity checks.

Mitigating Controls (NIST CSF 2.0)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.

PR.DS-01 mostly match
blocks

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data at rest.

PR.DS-02 mostly match
blocks

Requires cryptographic hashes and signatures that directly enforce integrity-check validation for data in transit.

ID.RA-09 partial match
blocks

Mandates pre-acquisition integrity assessment, addressing only the initial portion of the weakness lifecycle.

RC.RP-03 partial match
blocks

Requires verification of backup integrity, covering validation only within recovery scenarios.

Mitigating Controls (ISO/IEC 27001:2022 Annex A)

Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.

blocks

Cryptographic controls mandate integrity mechanisms whose correct validation directly prevents CWE-354.

finds

Security testing can detect missing integrity validation but does not itself implement the control.

blocks

A.8.20's network-level controls (encryption in transit per (e), firewalls per (i), disabling vulnerable protocols per (n)) can mask the vulnerability during a portion of transit by preventing in-flight modification or filtering unauthorized sources, but the weakness is an application-layer defect in the receiving product's checksum validation, which remains exploitable once data is decrypted at the network boundary or originates from within a trusted segment.

blocks

A.8.21 mandates security features of network services including encryption and connection controls, and technical parameters for secured connections, which can require integrity-protected transit (e.g., TLS) that blocks exploitation of the missing checksum check during network transmission; however, the application-level checksum validation defect itself remains and can be exploited where data is processed before validation, where the network service is bypassed, or where the checksum serves purposes beyond transit integrity.

prevents

Secure coding standards require proper implementation and validation of checksums or MACs.

prevents

A.8.30 carries its effect through the secure design, coding and testing practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary software implementation weaknesses like missing checksum validation the way those practices do; the owner has declared `partial` as the ceiling for this clause on `prevents`, and the remainder is the fallibility of the referenced practices.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.

Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-354
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
Oracle Linux 9 (1 rule)
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. blocks CWE-354
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
RHEL 8 (2 rules)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354
  • V-230265 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. blocks CWE-354

References