Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-45581: CWE-532: Insertion of Sensitive Information into Log File in hyperledger fabric-chaincode-java

0
Medium
VulnerabilityCVE-2026-45581cvecve-2026-45581cwe-532
Published: Mon Jun 08 2026 (06/08/2026, 16:53:45 UTC)
Source: CVE Database V5
Vendor/Project: hyperledger
Product: fabric-chaincode-java

Description

A vulnerability in fabric-chaincode-java versions from 2. 3. 1 up to but not including 2. 5. 10 causes the TLS private key password to be logged in plaintext at INFO level when chaincode is deployed in chaincode-as-a-service mode with TLS enabled. An attacker with access to these logs could recover the password and, if they also obtain the TLS private key, impersonate the chaincode server. This issue has been addressed in version 2. 5. 10.

CVSS v3.1

Score 5.5medium

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/08/2026, 17:19:03 UTC

Technical Analysis

The fabric-chaincode-java component of Hyperledger Fabric, in versions 2.3.1 through 2.5.9, logs the TLS private key password in plaintext within INFO level logs when operating in chaincode-as-a-service mode with TLS enabled. This exposure of sensitive information (CWE-532) allows an attacker with access to the logs to retrieve the TLS private key password. Combined with possession of the TLS private key, this could enable impersonation of the chaincode server. The vulnerability has a CVSS 3.1 base score of 5.5, reflecting a medium severity. The issue was fixed in version 2.5.10.

Potential Impact

Disclosure of the TLS private key password in logs can lead to compromise of the TLS private key if an attacker obtains both the password and the key. This enables impersonation of the chaincode server, potentially undermining the integrity of communications. The vulnerability does not affect confidentiality, integrity, or availability directly beyond this credential exposure. No known exploits are reported in the wild.

Mitigation Recommendations

Upgrade fabric-chaincode-java to version 2.5.10 or later, where this issue is patched. Until upgrading, restrict access to chaincode server logs to trusted personnel only to prevent exposure of the TLS private key password. Patch status is confirmed by the vendor advisory indicating the fix in version 2.5.10.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-05-12T19:00:14.601Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a26f68ee29bf47b50440d4f

Added to database: 6/8/2026, 5:06:22 PM

Last enriched: 6/8/2026, 5:19:03 PM

Last updated: 6/8/2026, 6:10:13 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses