Legion of the Bouncy Castle BC-JAVA/BC-LTS-JAVA/BC-FJA up to 2.1.2 missing encryption

Summaryinfo

A vulnerability has been found in Legion of the Bouncy Castle BC-JAVA, BC-LTS-JAVA and BC-FJA up to 1.84/2.73.11/1.0.2.6/2.0.1/2.1.2 and classified as problematic. This vulnerability affects unknown code. This manipulation causes missing encryption. This vulnerability is registered as CVE-2026-58061. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability has been found in Legion of the Bouncy Castle BC-JAVA, BC-LTS-JAVA and BC-FJA up to 1.84/2.73.11/1.0.2.6/2.0.1/2.1.2 and classified as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality. The summary by CVE is:

In Bouncy Castle for Java before 1.85, CCM-family modes write plaintext to caller buffer before tag check. 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).

The advisory is shared at github.com. This vulnerability is known as CVE-2026-58061 since 06/28/2026. The exploitation appears to be difficult. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600 for this issue.

Upgrading to version 1.85, 2.73.12, 1.0.2.7, 2.0.2 or 2.1.3 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Programming Language Software

Vendor

• Legion of the Bouncy Castle

Name

• BC-FJA
• BC-JAVA
• BC-LTS-JAVA

Version

• 1.0
• 1.0.2.0
• 1.0.2.1
• 1.0.2.2
• 1.0.2.3
• 1.0.2.4
• 1.0.2.5
• 1.0.2.6
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42
• 1.43
• 1.44
• 1.45
• 1.46
• 1.47
• 1.48
• 1.49
• 1.50
• 1.51
• 1.52
• 1.53
• 1.54
• 1.55
• 1.56
• 1.57
• 1.58
• 1.59
• 1.60
• 1.61
• 1.62
• 1.63
• 1.64
• 1.65
• 1.66
• 1.67
• 1.68
• 1.69
• 1.70
• 1.71
• 1.72
• 1.73
• 1.74
• 1.75
• 1.76
• 1.77
• 1.78
• 1.79
• 1.80
• 1.81
• 1.82
• 1.83
• 1.84
• 2.0.0
• 2.0.1
• 2.1.0
• 2.1.1
• 2.1.2
• 2.73.0
• 2.73.1
• 2.73.2
• 2.73.3
• 2.73.4
• 2.73.5
• 2.73.6
• 2.73.7
• 2.73.8
• 2.73.9
• 2.73.10
• 2.73.11

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion