VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

astrbot: vulnerability history, versions and safety

astrbot is a package in the PyPI ecosystem. Vulert records 16 vulnerabilities for it across 120 releases, from Jun 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded C1 H2 M2 L3 U8
i
10 with no fix published

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

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

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all astrbot vulnerabilities

Vulert verdict on astrbot 4.29.1 i

Updated on 23 Oct 2026

Careful: 4.29.1 has 10 known vulnerabilities, and 10 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Active

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 4.29.1 — affected i
  • Vulnerabilities on record 16 over 1 year · 15 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 10 i
  • Depended on by 1 packages i
  • Stars 42,255 i
  • Last release this month i
  • Licence AGPL-3.0-or-later 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 astrbot, 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
4.29.1 17 Oct 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.29.0 14 Oct 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.29.0b2 10 Oct 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.29.0b1 01 Oct 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.28.2 27 Sep 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.28.1 14 Sep 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.28.0 07 Sep 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.28.0b1 01 Sep 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.27.5 31 Aug 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.27.4 19 Aug 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.27.3 12 Aug 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.27.2 05 Aug 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.27.1 02 Aug 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.27.0 02 Aug 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.8 28 Jul 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.7 18 Jul 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.6 14 Jul 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.5 07 Jul 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.4 02 Jul 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.3 30 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.2 27 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.1 25 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0 24 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.6 21 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.6rc3 21 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.6rc2 21 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.6rc1 21 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b12 21 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b11 20 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b10 19 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b9 19 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b8 17 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b7 17 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b6 17 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b5 17 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b4 17 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b3 16 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b2 16 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.26.0b1 15 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.5 08 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.4 07 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.3 05 Jun 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.2 30 May 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.1 17 May 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.25.0 15 May 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.24.5 13 May 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.24.4 12 May 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.24.3 12 May 2026 H1 M2 L2 U5 AGPL-3.0-or-later No Details →
4.24.2 03 May 2026 L1 U1 AGPL-3.0-or-later No Details →
4.24.1 03 May 2026 L1 U1 AGPL-3.0-or-later No Details →
4.24.0 03 May 2026 L1 U1 AGPL-3.0-or-later No Details →
4.23.6 27 Apr 2026 L1 U1 AGPL-3.0-or-later No Details →
4.23.5 23 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.23.3 23 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.23.2 19 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.23.1 13 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.23.0 12 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.23.0b1 11 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.22.3 04 Apr 2026 L2 U2 AGPL-3.0-or-later No Details →
4.22.2 28 Mar 2026 L2 U2 — No Details →
4.22.1 25 Mar 2026 L3 U3 — No Details →
4.22.0 22 Mar 2026 L3 U3 — No Details →
4.21.0 21 Mar 2026 L3 U3 — No Details →
4.20.1 16 Mar 2026 L3 U3 — No Details →
4.20.0 12 Mar 2026 L3 U3 — No Details →
4.19.5 10 Mar 2026 L3 U3 — No Details →
4.19.4 09 Mar 2026 L3 U3 — No Details →
4.19.3 08 Mar 2026 L3 U3 — No Details →
4.19.2 05 Mar 2026 L3 U3 — No Details →
4.18.3 26 Feb 2026 L3 U3 — No Details →
4.18.2 24 Feb 2026 L3 U3 — No Details →
4.18.1 22 Feb 2026 L3 U3 — No Details →
4.18.0 21 Feb 2026 L3 U3 — No Details →
4.17.6 20 Feb 2026 L3 U3 — No Details →
4.17.5 18 Feb 2026 L3 U3 — No Details →
4.17.4 17 Feb 2026 L3 U3 — No Details →
4.17.3 17 Feb 2026 L3 U3 — No Details →
4.17.2 16 Feb 2026 L3 U3 — No Details →
4.17.1 15 Feb 2026 L3 U3 — No Details →
4.17.0 15 Feb 2026 L3 U3 — No Details →
4.16.0 12 Feb 2026 M1 L3 U4 — No Details →
4.15.0 10 Feb 2026 M1 L3 U4 — No Details →
4.14.8 08 Feb 2026 M1 L3 U4 — No Details →
4.14.7 08 Feb 2026 M1 L3 U4 — No Details →
4.14.6 07 Feb 2026 M1 L3 U4 — No Details →
4.14.5 06 Feb 2026 M1 L3 U4 — No Details →
4.14.4 04 Feb 2026 M1 L3 U4 — No Details →
4.14.3 04 Feb 2026 M1 L3 U4 — No Details →
4.14.2 04 Feb 2026 M1 L3 U4 — No Details →
4.14.1 03 Feb 2026 M1 L3 U4 — No Details →
4.14.0 03 Feb 2026 M1 L3 U4 — No Details →
4.13.2 31 Jan 2026 M1 L3 U4 — No Details →
4.13.1 29 Jan 2026 M1 L3 U4 — No Details →
4.13.0 28 Jan 2026 M1 L3 U4 — No Details →
4.12.4 24 Jan 2026 M1 L3 U4 — No Details →
4.12.3 17 Jan 2026 M1 L3 U4 — No Details →
4.12.2 17 Jan 2026 M1 L3 U4 — No Details →
4.12.1 15 Jan 2026 M1 L3 U4 — No Details →
4.12.0 15 Jan 2026 M1 L3 U4 — No Details →
4.11.4 12 Jan 2026 M1 L3 U4 — No Details →
4.11.3 12 Jan 2026 M1 L3 U4 — No Details →
4.11.2 08 Jan 2026 M1 L3 U4 — No Details →
4.11.1 05 Jan 2026 M1 L3 U4 — No Details →
4.11.0 05 Jan 2026 M1 L3 U4 — No Details →
4.10.6 02 Jan 2026 M1 L3 U4 — No Details →
4.10.5 31 Dec 2025 M1 L3 U4 — No Details →
4.10.4 31 Dec 2025 M1 L3 U4 — No Details →
4.10.3 26 Dec 2025 M1 L3 U4 — No Details →
4.10.2 24 Dec 2025 M1 L3 U4 — No Details →
4.10.1 23 Dec 2025 M1 L3 U4 — No Details →
4.10.0 22 Dec 2025 M1 L3 U4 — No Details →
4.10.0a2 21 Dec 2025 M1 L3 U4 — No Details →
4.10.0a1 20 Dec 2025 M1 L3 U4 — No Details →
4.9.2 15 Dec 2025 M1 L3 U4 — No Details →
4.9.1 15 Dec 2025 M1 L3 U4 — No Details →
4.9.0 13 Dec 2025 M1 L3 U4 — No Details →
4.8.0 05 Dec 2025 M1 L3 U4 — No Details →
4.7.4 01 Dec 2025 M1 L3 U4 — No Details →
4.7.3 29 Nov 2025 M1 L3 U4 — No Details →
4.7.1 28 Nov 2025 M1 L3 U4 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 4
  • 2026 12

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

03 Vulnerabilities

Recorded vulnerabilities for astrbot

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-55449: AstrBot RCE Vulnerability Due to Hard-Coded JWT Signing Keys 9.8 critical 3.5.18 29 Jun 2026
CVE-2025-55449: AstrBot RCE Vulnerability Due to Hard-Coded JWT Signing Keys 9.8 critical 3.5.18 14 Nov 2025
CVE-2025-57698: AstrBot Directory Traversal Vulnerability in Plugin Upload Functionality 8.7 high No fix published 07 Nov 2025
CVE-2025-57698: AstrBot Directory Traversal Vulnerability in v3.5.22 8.7 high No fix published 07 Jul 2026
CVE-2025-48957: AstrBot Path Traversal Vulnerability Leading to Sensitive Data Exposure 7.5 high 3.5.13 07 Jul 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 astrbot

Is astrbot safe to use?

Vulert records 16 vulnerabilities for astrbot in PyPI: 1 critical, 2 high, 2 medium and 3 low, plus 8 not yet rated. 10 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is astrbot's Vulert package health score?

Vulert scores astrbot 50/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 astrbot affected?

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

Which version of astrbot should I use?

4.29.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 astrbot have?

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

15 vulnerabilities were recorded for astrbot in the last 12 months, and the oldest entry in this database dates to 04 Jun 2025. 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 astrbot 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 astrbot for upcoming vulnerabilities?

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