How severe is CVE-2022-31121?

CVE-2022-31121 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-31121?

CVE-2022-31121 affects the following packages: github.com/hyperledger/fabric (Go), github.com/hyperledger/fabric (Go). Ecosystems affected: Go.

How do I fix CVE-2022-31121?

Update github.com/hyperledger/fabric to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31121 is resolved across your whole dependency graph.

How do I detect CVE-2022-31121 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hyperledger/fabric, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-31121 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2022-31121 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-31121 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2022-31121?

CVE-2022-31121 has an EPSS (Exploit Prediction Scoring System) score of 2.1%, placing it in the 82th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-31121?

CVE-2022-31121 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2022-31121 published, and has it been updated?

CVE-2022-31121 was published on July 7, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-31121 — fabric

HIGHFix: hyperledger/fabric@0f18359

CVE-2022-31121 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in github.com/hyperledger/fabric. A fix is available for github.com/hyperledger/fabric — see the affected versions and patch details below.

Improper Input Validation in fabric hyperledger

Also known asBIT-hyperledger-fabric-orderer-2022-31121BIT-hyperledger-fabric-peer-2022-31121BIT-hyperledger-fabric-tools-2022-31121GHSA-72x4-cq6r-jp4p

Published

Jul 7, 2022

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-31121.

EPSS Exploitation Probability

via FIRST.org ↗

2.1%probability of exploitation in next 30 days

Lower Risk+0.05%

Lower risk than most CVEs82th percentile — riskier than 82% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

🐹github.com/hyperledger/fabric🐹github.com/hyperledger/fabric

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

If a consensus client sends a malformed consensus request to an orderer it may crash the orderer node. This fix checks for the malformed consensus request and returns an error to the consensus client.

Specific Go Packages Affected

github.com/hyperledger/fabric/orderer/common/cluster

Patches

Fixed in v2.2.7 and v2.4.5.

Workarounds

None, users must upgrade to v2.2.7 or v2.4.5.

References

https://github.com/hyperledger/fabric/releases/tag/v2.2.7 https://github.com/hyperledger/fabric/releases/tag/v2.4.5

For more information

If you have any questions or comments about this advisory:

Open an issue in Hyperledger Fabric repository

Credits

Thank you to Haosheng Wang of OPPO ZIWU Security Lab for this disclosure.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/hyperledger/fabric`	all versions	2.2.7`go get github.com/hyperledger/fabric@v2.2.7`
🐹Go	`github.com/hyperledger/fabric`	≥ 2.3.0&&< 2.4.5	2.4.5`go get github.com/hyperledger/fabric@v2.4.5`

Affected Products

1 product · 2 configurations

Application

fabrichyperledger

≥ 2.3.0 && < 2.4.5

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hyperledger/fabric, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/hyperledger/fabric to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31121 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact If a consensus client sends a malformed consensus request to an orderer it may crash the orderer node. This fix checks for the malformed consensus request and returns an error to the consensus client. ### Specific Go Packages Affected github.com/hyperledger/fabric/orderer/common/cluster ### Patches Fixed in v2.2.7 and v2.4.5. ### Workarounds None, users must upgrade to v2.2.7 or v2.4.5. ### References https://github.com/hyperledger/fabric/releases/tag/v2.2.7 https://github.com/hyperledger/fabric/releases/tag/v2.4.5 ### For more information If you have any questions or comments