dbcve.org
Sensitive Information in LogsWeakness · CWE-532

CVE-2026-45581

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In fabric-chaincode-java versions 2.3.1 through 2.5.9, when chaincode runs in chaincode-as-a-service mode with TLS enabled, the INFO-level logging inadvertently outputs the TLS private key password in plaintext. An attacker with access to these logs can extract the password and, if they also obtain the TLS private key file, impersonate the chaincode server.

MitigationUpgrade fabric-chaincode-java to version 2.5.10 or later, and immediately rotate any TLS private key passwords that may have been exposed in logs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify fabric-chaincode-java installation
    Locate the fabric-chaincode-java library in your project dependencies (e.g., check build files like pom.xml, build.gradle, or the classpath for the jar file)
    Affected if fabric-chaincode-java is present in the environment
  2. Determine the installed version
    Inspect the version of fabric-chaincode-java (check Maven/Gradle dependency declaration, or the jar manifest/version metadata)
    Affected if the version falls between 2.3.1 and 2.5.9 inclusive
  3. Verify chaincode-as-a-service mode is enabled
    Review the chaincode deployment configuration to determine if the chaincode is running as an external service (chaincode-as-a-service mode)
    Affected if chaincode-as-a-service mode is configured and in use
  4. Confirm TLS is enabled for chaincode communication
    Examine the chaincode server configuration for TLS settings, including whether a private key password is configured
    Affected if TLS is enabled and a TLS private key password is in use
  5. Inspect chaincode server logs for exposed credentials
    Search chaincode server logs (at INFO level) for occurrences of the TLS private key password in plaintext
    Affected if the TLS private key password appears in plaintext in the logs

A user is affected if fabric-chaincode-java version 2.3.1-2.5.9 is in use with chaincode-as-a-service mode and TLS enabled, and the plaintext password is visible in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade fabric-chaincode-java to version 2.5.10 or later, and immediately rotate any TLS private key passwords that may have been exposed in logs.

Recommended fix High confidence

2.5.10

  1. Identify the fabric-chaincode-java dependency in your project build configuration (e.g., pom.xml, build.gradle, package.json)
  2. Update the version of fabric-chaincode-java to 2.5.10 or later
  3. Rebuild your project with the updated dependency
  4. Redeploy the chaincode with the new version
  5. Verify that TLS private key passwords are no longer logged at INFO level in chaincode server logs
  6. Ensure chaincode-as-a-service deployment uses the upgraded library
Caveat No breaking changes mentioned in the advisory; this is a security patch release

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45581 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data