Hyperledger indy-node vulnerable to denial of service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2022-31006: 1.16% estimated exploitation activity in the next 30 days; percentile 67.05 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact An attacker can max out the number of client connections allowed by the ledger that was deployed using guidance provided in the indy-node repository, leaving the ledger unable to be used for its intended purpose. The ledger content will not be impacted by the attack, and the ledger will resume servicing valid client requests after the attack. Mitigations This attack exploits the trade-off between resilience and availability. Any protection against abusive client connections will also prevent the network being accessed by certain legitimate users. As a result, validator nodes must tune their firewall rules to ensure the right trade-off for their network's expected users. The guidance previously provided enabled a low-cost DDoS attack. The guidance to network operators for the use of firewall rules in the deployment of Indy networks has been modified to better protect against denial of service attacks by increasing the cost and complexity in mounting such attacks. The mitigation…

Published by the source

16 Sep 2022, 20:28 UTC

Last modified by the source

8 Nov 2023, 04:09 UTC

Source last checked

26 Oct 2026, 13:11 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-x996-7qh9-7ff7

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-x996-7qh9-7ff7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-31006

Advisory: Hyperledger indy-node vulnerable to denial of service
IDs: CVE-2022-31006, GHSA-x996-7qh9-7ff7
Record: https://patchnext.com/advisories/cve-2022-31006 (revision 2, source checked 26 Oct 2026, 13:11 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI indy-node: affected <= 1.12.6

## Suggested inspection (read-only)
- `python -m pip show indy-node`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on indy-node.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-x996-7qh9-7ff7 (OSV record GHSA-x996-7qh9-7ff7 lists affected ranges: PyPI indy-node >=0 <=1.12.6)
- Verified: https://github.com/advisories/GHSA-x996-7qh9-7ff7 (GitHub-reviewed advisory GHSA-x996-7qh9-7ff7 lists affected ranges: PyPI indy-node >=0 <=1.12.6)

Commands are suggestions: review each one before running it.