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.
CVE-2026-45581
This medium-severity CVE scores 5.5 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 99% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.5
- EG Score
- 5.5(medium)
- EPSS
- 1.3%
- KEV
- Not listed
Published
May 19, 2026
Last Modified
June 9, 2026
Advisory Details (1)
Auto-updated Jun 16, 2026TLS private key password disclosed in INFO logs when running in chaincode-as-a-service mode · Advisory · hyperledger/fabric-chaincode-java · GitHub
https://github.com/hyperledger/fabric-chaincode-java/security/advisories/GHSA-wg5x-3g47-v38rVendor Advisories for CVE-2026-45581(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Affected Packages
(1 across 1 ecosystem)
Maven(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim | 2.3.1 ... 2.5.9 (14 versions) | 2.5.10 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 34× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-09 19:10 UTCEPSS rescore
- 2026-07-08 15:16 UTCEPSS rescore
- 2026-07-07 13:46 UTCEPSS rescore
- 2026-07-05 02:30 UTCEPSS rescore
- 2026-07-04 06:31 UTCEPSS rescore
- 2026-07-01 15:07 UTCEPSS rescore
- 2026-06-30 23:22 UTCEPSS rescore
- 2026-06-29 20:54 UTCEG score recompute
- 2026-06-28 14:07 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-28 04:56 UTCEPSS rescore
- 2026-06-27 20:25 UTCEG score recompute
- 2026-06-27 03:08 UTCEPSS rescore
- 2026-06-26 19:48 UTCEG score recompute
- 2026-06-25 17:06 UTCEG score recompute
- 2026-06-24 14:05 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-23 21:33 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-22 14:25 UTCEPSS rescore
- 2026-06-21 01:59 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-18 17:52 UTCEPSS rescore
- 2026-06-17 22:44 UTCEG score recompute
- 2026-06-17 17:53 UTCEPSS rescore
Show 26 moreShow fewer
- 2026-06-16 22:42 UTCEG score recompute
- 2026-06-15 23:02 UTCEG score recompute
- 2026-06-15 17:49 UTCEPSS rescore
- 2026-06-14 22:48 UTCEG score recompute
- 2026-06-13 23:15 UTCEG score recompute
- 2026-06-13 23:00 UTCEPSS rescore
- 2026-06-12 23:41 UTCEG score recompute
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 23:12 UTCEPSS rescore
- 2026-06-12 00:08 UTCEG score recompute
- 2026-06-11 14:00 UTCEPSS rescore
- 2026-06-11 00:33 UTCEG score recompute
- 2026-06-10 22:18 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 13:22 UTCEPSS rescore
- 2026-06-10 01:00 UTCEG score recompute
- 2026-06-09 01:27 UTCEG score recompute
- 2026-06-08 01:54 UTCEG score recompute
- 2026-06-07 02:21 UTCEG score recompute
- 2026-06-06 02:47 UTCEG score recompute
- 2026-06-05 03:14 UTCEG score recompute
- 2026-06-04 03:41 UTCEG score recompute
- 2026-06-03 04:07 UTCEG score recompute
- 2026-06-02 04:34 UTCEG score recompute
- 2026-06-01 05:01 UTCEG score recompute
- 2026-05-24 06:14 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-532
- CVE-2016-0898EG 10.0CRITICAL
- CVE-2018-17922EG 9.8CRITICAL
- CVE-2018-1264NVD 9.1EG 9.8CRITICAL
- CVE-2018-16049EG 9.8CRITICAL
- CVE-2018-11717EG 9.8EPSS 94%CRITICAL
- CVE-2018-11716EG 9.8EPSS 96%CRITICAL
- CVE-2018-0042EG 9.8CRITICAL
- CVE-2018-1072NVD 5.0EG 9.8MEDIUM
- CVE-2018-1117NVD 5.0EG 9.8MEDIUM
- CVE-2018-11320EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-45581?
When was CVE-2026-45581 disclosed?
Is CVE-2026-45581 actively exploited?
What is the CVSS score of CVE-2026-45581?
How do I remediate CVE-2026-45581?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45581
Is Your Infrastructure Affected by CVE-2026-45581?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.