Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
LOW severity

GHSA-99r4-cjp4-3hmx

LOWFix: vantage6/vantage6@27f4ee3

GHSA-99r4-cjp4-3hmx is a low-severity (CVSS 2.7) CWE-284 vulnerability in vantage6. O3 Security confirms whether GHSA-99r4-cjp4-3hmx is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

vantage6 collaboration admins can extend their influence by expanding the collaboration

Also known asCVE-2024-32969PYSEC-2026-2007
Published
May 22, 2024
Updated
Jul 7, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Jul 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐍vantage6

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

Collaboration administrators can add extra organizations to their collaboration. When doing that, they extend their influence: for instance, for organizations that they include, they can then create new users for which they know the passwords, and use that to read task results of other collaborations that that organization is involved in.

Only relatively trusted users - with access to manage a collaboration - are able to do this, which reduces the impact.

Patches

No

Workarounds

No

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIvantage6all versions4.5.0rc3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vantage6. 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.

  2. Fix

    Update vantage6 to 4.5.0rc3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-99r4-cjp4-3hmx is resolved across your whole dependency graph.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-99r4-cjp4-3hmx 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-99r4-cjp4-3hmx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Collaboration administrators can add extra organizations to their collaboration. When doing that, they extend their influence: for instance, for organizations that they include, they can then create new users for which they know the passwords, and use that to read task results of other collaborations that that organization is involved in. Only relatively trusted users - with access to manage a collaboration - are able to do this, which reduces the impact. ### Patches No ### Workarounds No
O3 Security · Impact-Aware SCA

Is GHSA-99r4-cjp4-3hmx in your dependencies?

O3 detects GHSA-99r4-cjp4-3hmx across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-99r4-cjp4-3hmx: vantage6 (Low 2.7) | O3 Security