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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 is the EPSS score for GHSA-73jv-44c3-j5p2?

GHSA-73jv-44c3-j5p2 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 20th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

Not in CISA KEV

Ajenti has an authorization bypass during custom package installationGHSA-73jv-44c3-j5p2

GHSA-73jv-44c3-j5p2 is a CWE-862 vulnerability in ajenti-panel. A fix is available for ajenti-panel — see the affected versions and patch details below.

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

Published

Apr 3, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-73jv-44c3-j5p2.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs20th percentile — riskier than 20% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

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`pip install --upgrade 'ajenti-panel==2.2.15'`

Affected Products

1 product · 1 configurations

Application

ajentiajenti

< 2.2.15

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works