VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

aries-cloudagent: vulnerability history, versions and safety

aries-cloudagent is a package in the PyPI ecosystem. Vulert records 2 vulnerabilities for it across 40 releases, from Jan 2024 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 29 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all aries-cloudagent vulnerabilities

Vulert verdict on aries-cloudagent 1.0.1 i

Updated on 23 Oct 2026

Good news: 1.0.1, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 2.

Package health score 65/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Moderate

What to do: Stay on 1.0.1 or newer. This can change: a vulnerability disclosed tomorrow can affect 1.0.1 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 1.0.1 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 1 in the last year i
  • Latest disclosure 29 Jun 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 0 i
  • Stars 493 i
  • OpenSSF scorecard 5/10 i
  • Last release 24 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 aries-cloudagent, 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
0.12.8 18 Jul 2025 none Apache-2.0 — Details →
0.12.7 18 Jul 2025 none Apache-2.0 — Details →
0.12.7rc2 16 Jul 2025 none Apache-2.0 — Details →
0.12.7rc1 14 Jul 2025 none Apache-2.0 — Details →
0.12.7rc0 26 Jun 2025 none Apache-2.0 — Details →
0.12.6 13 Mar 2025 none Apache-2.0 — Details →
0.12.5 06 Mar 2025 none Apache-2.0 — Details →
0.12.4 30 Jan 2025 none Apache-2.0 — Details →
0.12.3 17 Dec 2024 none Apache-2.0 — Details →
0.12.3rc0 17 Dec 2024 none Apache-2.0 — Details →
1.0.1 08 Oct 2024 none Apache-2.0 — Details →
1.0.1rc1 01 Oct 2024 none Apache-2.0 — Details →
1.0.1rc0 26 Sep 2024 none Apache-2.0 — Details →
1.0.0 16 Aug 2024 none Apache-2.0 — Details →
1.0.0rc6 02 Aug 2024 none Apache-2.0 — Details →
0.12.2 01 Aug 2024 none Apache-2.0 — Details →
0.11.3 01 Aug 2024 none Apache-2.0 — Details →
0.12.2rc1 25 Jul 2024 none Apache-2.0 — Details →
0.11.2 25 Jul 2024 none Apache-2.0 — Details →
1.0.0rc5 23 Jul 2024 none Apache-2.0 — Details →
1.0.0rc4 09 Jul 2024 none Apache-2.0 — Details →
0.11.1 07 May 2024 none Apache-2.0 — Details →
0.12.1 01 May 2024 none Apache-2.0 — Details →
0.12.1rc1 26 Apr 2024 none Apache-2.0 — Details →
0.12.1rc0 24 Apr 2024 none Apache-2.0 — Details →
0.12.0 11 Apr 2024 none Apache-2.0 — Details →
0.12.0rc3 09 Apr 2024 none Apache-2.0 — Details →
0.12.0rc2 06 Mar 2024 none Apache-2.0 — Details →
0.12.0rc1 20 Feb 2024 none Apache-2.0 — Details →
0.12.0rc0 24 Jan 2024 none Apache-2.0 — Details →
0.11.0 25 Nov 2023 none Apache-2.0 — Details →
0.10.5 22 Nov 2023 none Apache-2.0 — Details →
0.11.0rc2 17 Nov 2023 U1 Apache-2.0 Yes Details →
0.11.0rc1 30 Oct 2023 U1 Apache-2.0 Yes Details →
0.10.4 09 Oct 2023 C1 Apache-2.0 Yes Details →
0.10.3 29 Sep 2023 C1 Apache-2.0 Yes Details →
0.10.2 22 Sep 2023 C1 Apache-2.0 Yes Details →
0.10.2rc0 08 Sep 2023 C1 Apache-2.0 Yes Details →
0.10.1 29 Aug 2023 C1 Apache-2.0 Yes Details →
0.10.0 29 Aug 2023 C1 Apache-2.0 Yes Details →
0.10.0rc2 25 Aug 2023 C1 Apache-2.0 Yes Details →
0.10.0rc1 24 Aug 2023 C1 Apache-2.0 Yes Details →
0.10.0rc0 11 Aug 2023 C1 Apache-2.0 Yes Details →
0.9.0 24 Jul 2023 C1 Apache-2.0 Yes Details →
0.9.0rc0 21 Jul 2023 C1 Apache-2.0 Yes Details →
1.0.0rc3 07 Jul 2023 none Apache-2.0 — Details →
0.8.2 29 Jun 2023 C1 Apache-2.0 Yes Details →
0.8.2rc2 28 Jun 2023 C1 Apache-2.0 Yes Details →
0.8.2rc1 27 Jun 2023 C1 Apache-2.0 Yes Details →
0.8.2rc0 08 Jun 2023 C1 Apache-2.0 Yes Details →
1.0.0rc2 05 Jun 2023 none Apache-2.0 — Details →
0.8.1 06 Apr 2023 C1 Apache-2.0 Yes Details →
0.8.1rc2 04 Apr 2023 C1 Apache-2.0 Yes Details →
0.8.1rc1 31 Mar 2023 C1 Apache-2.0 Yes Details →
0.8.1rc0 31 Mar 2023 C1 Apache-2.0 Yes Details →
0.8.0 15 Mar 2023 C1 Apache-2.0 Yes Details →
0.8.0rc0 10 Feb 2023 C1 Apache-2.0 Yes Details →
1.0.0rc1 04 Nov 2022 none Apache-2.0 — Details →
0.7.5 26 Oct 2022 C1 Apache-2.0 Yes Details →
0.7.5rc1 24 Oct 2022 C1 Apache-2.0 Yes Details →
0.7.5rc0 12 Oct 2022 C1 Apache-2.0 Yes Details →
1.0.0rc0 18 Aug 2022 none Apache-2.0 — Details →
0.7.4 30 Jun 2022 C1 Apache-2.0 Yes Details →
0.7.4rc5 24 Jun 2022 C1 Apache-2.0 Yes Details →
0.7.4rc4 21 Jun 2022 C1 Apache-2.0 Yes Details →
0.7.4rc3 16 Jun 2022 C1 Apache-2.0 Yes Details →
0.7.4rc2 11 May 2022 C1 Apache-2.0 Yes Details →
0.7.4rc1 28 Apr 2022 C1 Apache-2.0 Yes Details →
0.7.4rc0 07 Apr 2022 C1 Apache-2.0 Yes Details →
0.7.3 10 Jan 2022 C1 Apache-2.0 Yes Details →
0.7.3rc0 13 Dec 2021 C1 Apache-2.0 Yes Details →
0.7.2 15 Nov 2021 C1 Apache-2.0 Yes Details →
0.7.2rc0 06 Oct 2021 C1 Apache-2.0 Yes Details →
0.7.1 01 Sep 2021 C1 non-standard Yes Details →
0.7.1rc0 24 Aug 2021 C1 non-standard Yes Details →
0.7.0 15 Jul 2021 C1 non-standard Yes Details →
0.7.0rc1 08 Jul 2021 none non-standard — Details →
0.7.0rc0 06 Jul 2021 none non-standard — Details →
0.6.0 25 Feb 2021 none non-standard — Details →
0.6.0rc1 22 Feb 2021 none non-standard — Details →
0.6.0rc0 12 Feb 2021 none non-standard — Details →
0.5.6 19 Oct 2020 none non-standard — Details →
0.5.5 15 Oct 2020 none non-standard — Details →
0.5.4 25 Aug 2020 none non-standard — Details →
0.5.3 25 Jul 2020 none non-standard — Details →
0.5.2 26 Jun 2020 none non-standard — Details →
0.5.1 23 Apr 2020 none non-standard — Details →
0.5.0 21 Apr 2020 none non-standard — Details →
0.4.5 04 Mar 2020 none non-standard — Details →
0.4.4 28 Feb 2020 none non-standard — Details →
0.4.3 26 Feb 2020 none non-standard — Details →
0.4.2 09 Feb 2020 none non-standard — Details →
0.4.1 31 Jan 2020 none non-standard — Details →
0.4.0 11 Dec 2019 none — — Details →
0.3.5 01 Nov 2019 none — — Details →
0.3.4 24 Oct 2019 none — — Details →
0.3.3 27 Sep 2019 none — — Details →
0.3.2 04 Sep 2019 none — — Details →
0.3.1 15 Aug 2019 none — — Details →
0.3.0 09 Aug 2019 none — — Details →
0.2.1 16 Jul 2019 none — — Details →
0.2.0 16 Jul 2019 none — — Details →

All 102 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for aries-cloudagent

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Hyperledger Aries Cloud Agent Python - Presentation Verification Vulnerability 9.9 critical 0.10.5 09 Jan 2024
CVE-2024-21669: Vulnerability in Aries Cloud Agent Python - Presentation Verification Flaw 9.9 critical 0.11.0 29 Jun 2026

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 aries-cloudagent

Is aries-cloudagent safe to use?

Vulert records 2 vulnerabilities for aries-cloudagent in PyPI: 1 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is aries-cloudagent's Vulert package health score?

Vulert scores aries-cloudagent 65/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).

Is the latest version of aries-cloudagent affected?

No. 1.0.1, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of aries-cloudagent should I use?

1.0.1 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 aries-cloudagent have?

2 vulnerabilities are recorded for aries-cloudagent in the PyPI ecosystem: 1 critical, 0 high, 0 medium and 0 low, plus 1 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 aries-cloudagent vulnerabilities disclosed?

1 vulnerability was recorded for aries-cloudagent in the last 12 months, and the oldest entry in this database dates to 09 Jan 2024. 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 aries-cloudagent 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 aries-cloudagent for upcoming vulnerabilities?

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