cve.bz

CVE-2026-45581 hyperledger fabric-chaincode-java

5.5 mediumEPSS 0.1%Fix available

Medium (5.5) in hyperledger fabric-chaincode-java. EPSS 0.1% estimated probability of exploitation activity in the next 30 days. Fixed in org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim 2.5.10.

On this page
fabric-chaincode-java is a Java based implementation of Hyperledger Fabric chaincode shim APIs. From version 2.3.1 to before version 2.5.10, when chaincode is deployed in chaincode-as-a-service mode with TLS enabled, the chaincode server INFO level logging includes the TLS private key password in plaintext. An attacker with access to the chaincode server logs could recover the TLS private key password. If the attacker can also obtain the TLS private key, they could impersonate the chaincode server. This issue has been patched in version 2.5.10.

Severity

CVSS 3.1

5.5 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.1% (unchanged from 0.1% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-06-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim (Maven): fixed in 2.5.10

Ask an AI about this CVE

Show the promptExplain CVE-2026-45581 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-45581?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-45581?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-45581 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
hyperledger fabric-chaincode-java>= 2.3.1, < 2.5.10

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-wg5x-3g47-v38rMavenorg.hyperledger.fabric-chaincode-java:fabric-chaincode-shim>=2.3.1 <2.5.102.5.10

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON