Skip to content

← Public intelligence

Maven package

org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.5MavenPublished

    fabric-chaincode-java: TLS Private Key Password Disclosed in INFO Startup Logs in Chaincode-as-a-Service Mode

    CVE-2026-45581 · GHSA-wg5x-3g47-v38r

    Affected
    • Maven org.hyperledger.fabric-chaincode-java:fabric-chaincode-shim >= 2.3.1, <= 2.5.9
    Fixed in
    2.5.10· Vendor fix available
    Issue
    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. Recommendation - Update to the fixed version of the chaincode runtime. - Redact or remove existing logs that contain the TLS private key password. - Change the TLS private key password. Mitigation Impacted deployments can mitigate the vulnerability by restricting the logging level to WARNING or higher so that INFO level logs are not written.

    Recommended action: Upgrade to 2.5.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →