Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Indy Node versions 1.12.2 up to but not including 1.12.3 are affected. A client that sends a malformed transaction can crash the current primary node, forcing a view change, and repeated rapid view changes may bring down the network. The source gives few details on the exact trigger or attacker requirements. Upgrade indy-node to version 1.12.3.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 7.5 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.022, the 82nd percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:39 UTC First seen by agentprime
- 31 Oct 2026, 14:39 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-3gw4-m5w7-v89c
- OSV: GHSA-3gw4-m5w7-v89c
- github.com/hyperledger/indy-node/security/advisories/GHSA-3gw4-m5w7-v89c
- nvd.nist.gov/vuln/detail/CVE-2020-11090
- github.com/hyperledger/indy-node
- github.com/hyperledger/indy-node/blob/master/CHANGELOG.md#1123
- github.com/pypa/advisory-database/tree/main/vulns/indy-node/PYSEC-2020-47.yaml
- pypi.org/project/indy-node/1.12.3