CVE-2026-45581: hyperledger fabric-chaincode-java · Sensitive Data in Logs
Affects hyperledger fabric-chaincode-javaSource CVE Database V5
Not known to be exploited · CVSS 5.5 Medium : upgrade to 2.5.10 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 8 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade fabric-chaincode-java and org.hyperledger/fabric-chaincode-java/fabric-chaincode-java to 2.5.10.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| hyperledgerfabric-chaincode-java | Affected
| Fixed in
|
Mavenorg.hyperledger/fabric-chaincode-java/fabric-chaincode-javapkg:maven/org.hyperledger/fabric-chaincode-java/fabric-chaincode-javaOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade fabric-chaincode-java to version 2.5.10 or later, where this issue has been patched. Until upgrading, restrict access to chaincode server logs to trusted personnel only to prevent leakage of the TLS private key password.
Description
A vulnerability in fabric-chaincode-java versions 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. This exposure could allow an attacker with access to the logs to recover the password and potentially impersonate the chaincode server if they also obtain the TLS private key. The issue is fixed in version 2.5.10.