How severe is GHSA-73jv-44c3-j5p2?

No CVSS score has been assigned to GHSA-73jv-44c3-j5p2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-73jv-44c3-j5p2?

GHSA-73jv-44c3-j5p2 affects the following packages: ajenti-panel (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-73jv-44c3-j5p2?

Update ajenti-panel to 2.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73jv-44c3-j5p2 is resolved across your whole dependency graph.

How do I detect GHSA-73jv-44c3-j5p2 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ajenti-panel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-73jv-44c3-j5p2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-73jv-44c3-j5p2?

O3 pinpoints whether GHSA-73jv-44c3-j5p2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-73jv-44c3-j5p2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-73jv-44c3-j5p2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-73jv-44c3-j5p2?

GHSA-73jv-44c3-j5p2 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-73jv-44c3-j5p2 published, and has it been updated?

GHSA-73jv-44c3-j5p2 was published on April 3, 2026 and was last updated on July 13, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-73jv-44c3-j5p2

GHSA-73jv-44c3-j5p2 is a CWE-862 vulnerability in ajenti-panel. O3 Security confirms whether GHSA-73jv-44c3-j5p2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Ajenti has an authorization bypass during custom package installation

Also known asCVE-2026-35175PYSEC-2026-2339

Published

Apr 3, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍ajenti-panel

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

An authenticated user (using the auth_users plugin authentication method) could install a custom package even if this user is not superuser.

Patches

This is fixed in the version 2.2.15. Users should upgrade to this version as soon as possible.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`ajenti-panel`	all versions	2.2.15

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ajenti-panel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update ajenti-panel to 2.2.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-73jv-44c3-j5p2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-73jv-44c3-j5p2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-73jv-44c3-j5p2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact An authenticated user (using the `auth_users` plugin authentication method) could install a custom package even if this user is not superuser. ### Patches This is fixed in the version 2.2.15. Users should upgrade to this version as soon as possible.

O3 Security · Impact-Aware SCA

Is GHSA-73jv-44c3-j5p2 in your dependencies?

O3 detects GHSA-73jv-44c3-j5p2 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works