Skip to main content
VulnerabilityPublished

CVE-2026-45581: hyperledger fabric-chaincode-java · Sensitive Data in Logs

Affects hyperledger fabric-chaincode-javaSource CVE Database V5

0
Compare

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

CVSS 3.1 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
hyperledgerfabric-chaincode-javaAffected
  • >=2.3.1 <2.5.10
Fixed in
  • 2.5.10
Mavenorg.hyperledger/fabric-chaincode-java/fabric-chaincode-javapkg:maven/org.hyperledger/fabric-chaincode-java/fabric-chaincode-javaOther threatsAffected
  • >=2.3.1 <2.5.10
Fixed in
  • 2.5.10

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.

References

Community reviews

Loading reviews…