VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

indy-node: vulnerability history, versions and safety

indy-node is a package in the PyPI ecosystem. Vulert records 8 vulnerabilities for it across 120 releases, from Jun 2020 to Aug 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded C1 H3 U4
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all indy-node vulnerabilities

Vulert verdict on indy-node 1.13.2 i

Updated on 23 Oct 2026

Careful: 1.13.2 has 3 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Niche
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 1.13.2 — affected i
  • Vulnerabilities on record 8 over 4 years · 0 in the last year i
  • Latest disclosure 30 Aug 2024 i
  • Highest CVSS 7.5 i
  • With no published fix 1 i
  • Stars 703 i
  • OpenSSF scorecard 4/10 i
  • Last release 32 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for indy-node, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
1.13.2.dev1715361505 10 May 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1710192544 11 Mar 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707935836 14 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707934952 14 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707775386 12 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2 09 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707338430 07 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707335680 07 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707328245 07 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1707260564 06 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1706791080 01 Feb 2024 H1 U2 Apache-2.0 No Details →
1.13.2.dev1681932053 19 Apr 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1681906727 19 Apr 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1680092750 29 Mar 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1679927188 27 Mar 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1678987550 16 Mar 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1678195950 07 Mar 2023 H1 U2 Apache-2.0 No Details →
1.13.2rc6 22 Feb 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1677078119 22 Feb 2023 H1 U2 Apache-2.0 No Details →
1.13.2rc5 23 Jan 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1674230696 20 Jan 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1674049094 18 Jan 2023 H1 U2 Apache-2.0 No Details →
1.13.2.dev1667310785 01 Nov 2022 H1 U2 Apache-2.0 No Details →
1.13.2rc4 26 Oct 2022 H1 U2 Apache-2.0 No Details →
1.13.2.dev1666813511 26 Oct 2022 H1 U2 Apache-2.0 No Details →
1.13.2.dev1666804999 26 Oct 2022 H1 U2 Apache-2.0 No Details →
1.13.2rc3 14 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.2.dev1663170231 14 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.2.dev1663169899 14 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.2rc2 12 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.2.dev1663008787 12 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.2rc1 02 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.1.dev1662150751 02 Sep 2022 H1 U2 Apache-2.0 No Details →
1.13.1.dev1661500617 26 Aug 2022 H1 U2 Apache-2.0 No Details →
1.12.6 22 Aug 2022 H1 U1 Apache-2.0 No Details →
1.12.6rc2 18 Aug 2022 H1 U1 Apache-2.0 No Details →
1.12.6rc1 17 Aug 2022 H1 U1 Apache-2.0 No Details →
1.12.5 09 Aug 2022 H1 U1 Apache-2.0 No Details →
1.13.0.dev287 04 Aug 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev286 04 Aug 2022 H1 U2 Apache-2.0 No Details →
1.12.5rc1 22 Jul 2022 H1 U1 Apache-2.0 No Details →
1.13.1rc2 06 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1654534721 06 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1654529956 06 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1654282177 03 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1654270807 03 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1654241043 03 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1654173713 02 Jun 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1653037779 20 May 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1652900067 18 May 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1652812796 17 May 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1652793165 17 May 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev24 05 May 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev19 30 Apr 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev13 20 Apr 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev5 29 Mar 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev282 25 Mar 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev2 07 Mar 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev280 10 Feb 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev279 20 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev275 19 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev269 14 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1257 14 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev267 13 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1256 13 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev266 13 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev1255 13 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev241 03 Jan 2022 H1 U2 Apache-2.0 No Details →
1.13.0.dev238 27 Dec 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev220 30 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1253 29 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev210 25 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1252 25 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev206 11 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev204 11 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev201 11 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev197 09 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1251 09 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev195 09 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1250 09 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev192 08 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev189 04 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1249 04 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev188 04 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1248 04 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev186 03 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev184 03 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1247 03 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1246 03 Nov 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1245 14 Oct 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev144 15 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev142 15 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev133 14 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1244 14 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev128 13 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1243 13 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev127 13 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1242 13 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev123 13 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1241 12 Sep 2021 H1 U2 Apache-2.0 No Details →
1.13.0.dev1240 30 Aug 2021 H1 U2 — No Details →
1.13.0.dev1239 14 Aug 2021 H1 U2 — No Details →
1.13.0.dev1238 10 Aug 2021 H1 U2 — No Details →
1.13.0.dev1237 11 Mar 2021 H1 U2 — No Details →
1.13.0.dev1236 09 Mar 2021 H1 U2 — No Details →
1.13.0.dev1235 09 Mar 2021 H1 U2 — No Details →
1.13.0.dev1234 05 Mar 2021 H1 U2 — No Details →
1.13.0.dev1233 25 Feb 2021 H1 U2 — No Details →
1.13.0.dev1232 25 Feb 2021 H1 U2 — No Details →
1.13.0.dev1231 24 Feb 2021 H1 U2 — No Details →
1.13.0.dev1230 20 Feb 2021 H1 U2 — No Details →
1.13.0.dev1229 19 Feb 2021 H1 U2 — No Details →
1.13.0.dev1228 18 Feb 2021 H1 U2 — No Details →
1.13.0.dev1227 16 Feb 2021 H1 U2 — No Details →
1.13.0.dev1226 16 Feb 2021 H1 U2 — No Details →
1.13.0.dev1225 12 Feb 2021 H1 U2 — No Details →
1.13.0.dev1224 12 Feb 2021 H1 U2 — No Details →
1.13.0.dev1223 10 Feb 2021 H1 U2 — No Details →
1.13.0.dev1222 21 Dec 2020 H1 U2 — No Details →
1.13.0.dev1221 03 Dec 2020 H1 U2 — No Details →

The newest 120 of 559 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 3
  • 2022 4
  • 2024 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 8 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for indy-node

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-11090: Uncontrolled Resource Consumption in Indy Node 7.5 critical 1.12.3 11 Jun 2020
CVE-2022-31006: Hyperledger indy-node Denial of Service Vulnerability 7.5 high No fix published 16 Sep 2022
CVE-2020-11093: Hyperledger Indy's update process of a DID does not check who signs the request 7.5 high 1.12.4 30 Aug 2024
CVE-2022-31020: Remote Code Execution in Indy-Node's NODE_UPGRADE Transaction 6.5 high 1.12.5rc1 02 Sep 2022
CVE-2020-11090: Uncontrolled Resource Consumption in indy-node N/A unrated 1.12.3 11 Jun 2020

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About indy-node

Is indy-node safe to use?

Vulert records 8 vulnerabilities for indy-node in PyPI: 1 critical, 3 high, 0 medium and 0 low, plus 4 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is indy-node's Vulert package health score?

Vulert scores indy-node 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of indy-node affected?

Yes. 1.13.2, the version you would install today, has 3 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of indy-node should I use?

1.13.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does indy-node have?

8 vulnerabilities are recorded for indy-node in the PyPI ecosystem: 1 critical, 3 high, 0 medium and 0 low, plus 4 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new indy-node vulnerabilities disclosed?

0 vulnerabilities were recorded for indy-node in the last 12 months, and the oldest entry in this database dates to 11 Jun 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of indy-node are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor indy-node for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the indy-node version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.