CVE-2026-45581: fabric-chaincode-java TLS Private Key Password Disclosed Vulnerability
MODERATECVE-2026-45581 is a MODERATE (CVSS 5.5) tls private key password disclosed vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting fabric-chaincode-java libraries in the Maven ecosystem. The issue involves tls private key password disclosed in info startup logs in chaincode-as-a-service mode. Remediation is available by upgrading affected packages to version 2.5.10.
CVE-2026-45581 at a Glance
Security Impact
CVSS: 5.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-45581
To remediate this vulnerability, upgrade all affected fabric-chaincode-java dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.hyperledger.fabric-chaincode-java</groupId>
<artifactId>fabric-chaincode-shim</artifactId>
<version>2.5.10</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.hyperledger.fabric-chaincode-java
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-45581, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.hyperledger.fabric-chaincode-java
Analyze the terminal output to locate any version of fabric-chaincode-java in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 2.5.10), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.hyperledger.fabric-chaincode-java command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In fabric-chaincode-java, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-45581 Affected fabric-chaincode-java Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim
|
Maven |
≥ 2.3.1
< 2.5.10
|
2.5.10
|
References
Frequently Asked Questions
What is CVE-2026-45581?
Which fabric-chaincode-java versions are affected?
What version fixes CVE-2026-45581?
Is fabric-chaincode-shim affected?
What is the CVSS score of CVE-2026-45581?
What CWE is associated with CVE-2026-45581?
How can I check Maven dependencies for CVE-2026-45581?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wg5x-3g47-v38r",
"modified" : "2026-06-09T13:12:11Z",
"published" : "2026-05-19T15:40:13Z",
"aliases" : [ "CVE-2026-45581" ],
"summary" : "fabric-chaincode-java: TLS Private Key Password Disclosed in INFO Startup Logs in Chaincode-as-a-Service Mode",
"details" : "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.\n\n### Recommendation\n\n- Update to the fixed version of the chaincode runtime.\n- Redact or remove existing logs that contain the TLS private key password.\n- Change the TLS private key password.\n\n### Mitigation\n\nImpacted deployments can mitigate the vulnerability by restricting the logging level to WARNING or higher so that INFO level logs are not written.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "2.3.1"
}, {
"fixed" : "2.5.10"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 2.5.9"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/hyperledger/fabric-chaincode-java/security/advisories/GHSA-wg5x-3g47-v38r"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-45581"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/hyperledger/fabric-chaincode-java"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-532" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-05-19T15:40:13Z",
"nvd_published_at" : "2026-06-08T17:16:44Z"
}
}