Vulnerability in github.com/hyperledger/fabric-ca (CVE-2026-53658)
Summary
Vulnerability in github.com/hyperledger/fabric-ca (CVE-2026-53658). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.5.21 or later.
Original description
The description as published by the source.
When fabric-ca is configured with an LDAP backend, the username from HTTP Basic authentication is included in an LDAP uid search filter without proper escaping. An unauthenticated attacker with network access to the CA enrollment endpoint could exploit this to perform LDAP injection before password validation, and potentially steer authentication attempts toward a victim account.
Recommendation
- All users of fabric-ca with an LDAP backend should update to a fixed version.
- For users not using an LDAP backend, no action is required.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53658 has been found in github.com/hyperledger/fabric-ca.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/hyperledger/fabric-ca to 1.5.21 or later.
If unsure, ask your IT team or search "github.com/hyperledger/fabric-ca CVE-2026-53658" on the vendor's site.
CVE-2026-53658 (github.com/hyperledger/fabric-ca) — CWE-90
Patched: 1.5.21 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-90) exists in github.com/hyperledger/fabric-ca.
Check the vendor advisory for the affected versions of github.com/hyperledger/fabric-ca.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.5.21.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/hyperledger/fabric-ca' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/hyperledger/fabric-ca' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/hyperledger/fabric-caを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/hyperledger/fabric-ca to 1.5.21ステージング環境で 1.5.21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- package github.com
- web github.com
- web github.com
- web github.com
- web security-advisories@github.com
- web security-advisories@github.com