VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

ajenti-panel: vulnerability history, versions and safety

ajenti-panel is a package in the PyPI ecosystem. Vulert records 7 vulnerabilities for it across 120 releases, from Mar 2018 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
7 vulnerabilities recorded H1 U6
i
5 with no fix published

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

See the unfixed vulnerabilities →
i
2 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 ajenti-panel vulnerabilities

Vulert verdict on ajenti-panel 2.2.17 i

Updated on 23 Oct 2026

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

Package health score 50/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

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 2.2.17 — affected i
  • Vulnerabilities on record 7 over 8 years · 2 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 7.2 i
  • With no published fix 5 i
  • Last release 1 month ago 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 ajenti-panel, 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
2.2.17 12 Sep 2026 U5 — No Details →
2.2.16 15 Jul 2026 U5 — No Details →
2.2.15 01 Apr 2026 U5 — No Details →
2.2.13 25 Feb 2026 H1 U1 — Yes Details →
2.2.12 17 Feb 2026 H1 U1 — Yes Details →
2.2.11 29 Jul 2025 H1 U1 — Yes Details →
2.2.10 03 Mar 2024 H1 U1 — Yes Details →
2.2.9 29 Feb 2024 H1 U1 — Yes Details →
2.2.8 05 Jan 2024 H1 U1 — Yes Details →
2.2.7 04 Sep 2023 H1 U1 — Yes Details →
2.2.6 20 Jun 2023 H1 U1 — Yes Details →
2.2.5 08 May 2023 H1 U1 — Yes Details →
2.2.4 13 Feb 2023 H1 U6 — No Details →
2.2.3 06 Jan 2023 H1 U6 — No Details →
2.2.1 23 Jul 2022 H1 U6 — No Details →
2.2.0 28 Jun 2022 H1 U6 — No Details →
2.1.44 17 Feb 2022 H1 U6 — No Details →
2.1.43 03 Sep 2021 H1 U6 — No Details →
2.1.42 31 Aug 2021 H1 U6 — No Details →
2.1.40 22 Mar 2021 H1 U6 — No Details →
2.1.39 22 Mar 2021 H1 U6 — No Details →
2.1.38 22 Mar 2021 H1 U6 — No Details →
2.1.37 27 Nov 2020 H1 U6 — No Details →
2.1.36 25 Jun 2020 H1 U6 — No Details →
2.1.35 03 May 2020 H1 U6 — No Details →
2.1.34 13 Apr 2020 H1 U6 — No Details →
2.1.33 13 Feb 2020 H1 U6 — No Details →
2.1.32 05 Oct 2019 H1 U6 — No Details →
2.1.31 24 Sep 2019 H1 U6 — No Details →
2.1.30 15 Aug 2019 H1 U6 — No Details →
2.1.29 14 Aug 2019 H1 U6 — No Details →
2.1.28 12 Aug 2019 H1 U6 — No Details →
2.1.27 12 Aug 2019 H1 U6 — No Details →
2.1.26 11 Jan 2019 H1 U6 — No Details →
2.1.25 23 Oct 2018 H1 U6 — No Details →
2.1.24 22 Nov 2017 H1 U6 — No Details →
2.1.23 05 Sep 2017 H1 U6 — No Details →
2.1.22 05 Sep 2017 H1 U6 — No Details →
2.1.21 19 Jun 2017 H1 U6 — No Details →
2.1.20 08 Jun 2017 H1 U6 — No Details →
2.1.19 02 Jun 2017 H1 U6 — No Details →
2.1.18 21 Apr 2017 H1 U6 — No Details →
2.1.17 02 Nov 2016 H1 U6 — No Details →
2.1.16 01 Nov 2016 H1 U6 — No Details →
2.1.15 25 May 2016 H1 U6 — No Details →
2.1.14 14 May 2016 H1 U6 — No Details →
2.1.13 06 May 2016 H1 U6 — No Details →
2.1.12 06 May 2016 H1 U6 — No Details →
2.1.11 08 Apr 2016 H1 U6 — No Details →
2.1.10 07 Apr 2016 H1 U6 — No Details →
2.1.9 03 Apr 2016 H1 U6 — No Details →
2.1.8 19 Mar 2016 H1 U6 — No Details →
2.1.7 08 Mar 2016 H1 U6 — No Details →
2.1.6 22 Dec 2015 H1 U6 — No Details →
2.1.5 04 Nov 2015 H1 U6 — No Details →
2.1.4 25 Oct 2015 H1 U6 — No Details →
2.1.3 21 Oct 2015 H1 U6 — No Details →
2.1.2 19 Oct 2015 H1 U6 — No Details →
2.1.1 17 Oct 2015 H1 U6 — No Details →
2.1.0 30 Sep 2015 H1 U6 — No Details →
2.0.71 18 Sep 2015 H1 U6 — No Details →
2.0.70 18 Sep 2015 H1 U6 — No Details →
2.0.69 18 Sep 2015 H1 U6 — No Details →
2.0.68 18 Sep 2015 H1 U6 — No Details →
2.0.67 11 Sep 2015 H1 U6 — No Details →
2.0.66 08 Sep 2015 H1 U6 — No Details →
2.0.65 30 Aug 2015 H1 U6 — No Details →
2.0.64 30 Aug 2015 H1 U6 — No Details →
2.0.63 28 Aug 2015 H1 U6 — No Details →
2.0.62 18 Aug 2015 H1 U6 — No Details →
2.0.61 18 Aug 2015 H1 U6 — No Details →
2.0.60 26 Jul 2015 H1 U6 — No Details →
2.0.59 21 Jul 2015 H1 U6 — No Details →
2.0.58 21 Jul 2015 H1 U6 — No Details →
2.0.57 20 Jun 2015 H1 U6 — No Details →
2.0.56 12 Jun 2015 H1 U6 — No Details →
2.0.55 12 Jun 2015 H1 U6 — No Details →
2.0.54 12 Jun 2015 H1 U6 — No Details →
2.0.53 12 Jun 2015 H1 U6 — No Details →
2.0.52 12 Jun 2015 H1 U6 — No Details →
2.0.51 12 Jun 2015 H1 U6 — No Details →
2.0.50 12 Jun 2015 H1 U6 — No Details →
2.0.49 06 Jun 2015 H1 U6 — No Details →
2.0.48 05 Jun 2015 H1 U6 — No Details →
2.0.47 29 May 2015 H1 U6 — No Details →
2.0.46 20 May 2015 H1 U6 — No Details →
2.0.45 05 May 2015 H1 U6 — No Details →
2.0.44 05 May 2015 H1 U6 — No Details →
2.0.43 04 May 2015 H1 U6 — No Details →
2.0.42 04 May 2015 H1 U6 — No Details →
2.0.41 04 May 2015 H1 U6 — No Details →
2.0.40 04 May 2015 H1 U6 — No Details →
2.0.39 04 May 2015 H1 U6 — No Details →
2.0.38 04 May 2015 H1 U6 — No Details →
2.0.37 04 May 2015 H1 U6 — No Details →
2.0.36 22 Apr 2015 H1 U6 — No Details →
2.0.35 20 Apr 2015 H1 U6 — No Details →
2.0.34 16 Apr 2015 H1 U6 — No Details →
0.33.0 12 Apr 2015 H1 U6 — No Details →
0.32.0 07 Apr 2015 H1 U6 — No Details →
0.31.0 23 Mar 2015 H1 U6 — No Details →
0.30.0 19 Mar 2015 H1 U6 — No Details →
0.29.0 16 Mar 2015 H1 U6 — No Details →
0.28.0 12 Mar 2015 H1 U6 — No Details →
0.27.0 04 Mar 2015 H1 U6 — No Details →
0.26.0 01 Mar 2015 H1 U6 — No Details →
0.25.0 25 Feb 2015 H1 U6 — No Details →
0.23.0 15 Feb 2015 H1 U6 — No Details →
0.22.0 15 Feb 2015 H1 U6 — No Details →
0.21.0 14 Feb 2015 H1 U6 — No Details →
0.20.0 14 Feb 2015 H1 U6 — No Details →
0.19.0 14 Feb 2015 H1 U6 — No Details →
0.18.0 14 Feb 2015 H1 U6 — No Details →
0.17.0 14 Feb 2015 H1 U6 — No Details →
0.16.0 14 Feb 2015 H1 U6 — No Details →
0.15.0 13 Feb 2015 H1 U6 — No Details →
0.14.0 13 Feb 2015 H1 U6 — No Details →
0.13.0 13 Feb 2015 H1 U6 — No Details →
0.12.0 13 Feb 2015 H1 U6 — No Details →
0.11.0 08 Feb 2015 H1 U6 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 5
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for ajenti-panel

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-35175: Ajenti Panel Authorization Bypass During Custom Package Installation 7.2 high 2.2.15 03 Apr 2026
CVE-2026-35175: Ajenti Panel Authorization Bypass During Custom Package Installation 7.2 high 2.2.15 13 Jul 2026
CVE-2018-1000080: Insecure Permissions in Ajenti-Panel N/A unrated No fix published 13 Mar 2018
CVE-2018-1000081: Ajenti-Panel Input Validation Vulnerability N/A unrated No fix published 13 Mar 2018
CVE-2018-1000082: Ajenti-Panel Cross-Site Request Forgery (CSRF) Vulnerability N/A unrated No fix published 13 Mar 2018

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 ajenti-panel

Is ajenti-panel safe to use?

Vulert records 7 vulnerabilities for ajenti-panel in PyPI: 0 critical, 1 high, 0 medium and 0 low, plus 6 not yet rated. 5 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is ajenti-panel's Vulert package health score?

Vulert scores ajenti-panel 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 ajenti-panel affected?

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

Which version of ajenti-panel should I use?

2.2.17 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 ajenti-panel have?

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

2 vulnerabilities were recorded for ajenti-panel in the last 12 months, and the oldest entry in this database dates to 13 Mar 2018. 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 ajenti-panel 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 ajenti-panel for upcoming vulnerabilities?

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