How severe is GHSA-j6g5-p62x-58hw?

No CVSS score has been assigned to GHSA-j6g5-p62x-58hw yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j6g5-p62x-58hw?

GHSA-j6g5-p62x-58hw affects the following packages: vantage6 (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-j6g5-p62x-58hw?

Update vantage6 to 4.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6g5-p62x-58hw is resolved across your whole dependency graph.

How do I detect GHSA-j6g5-p62x-58hw in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vantage6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-j6g5-p62x-58hw 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.

Is GHSA-j6g5-p62x-58hw actively exploited in the wild?

No public exploit code has been indexed for GHSA-j6g5-p62x-58hw 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-j6g5-p62x-58hw?

GHSA-j6g5-p62x-58hw has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 42th 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-j6g5-p62x-58hw?

GHSA-j6g5-p62x-58hw is classified as CWE-307 (CWE-307). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j6g5-p62x-58hw published, and has it been updated?

GHSA-j6g5-p62x-58hw was published on June 12, 2025 and was last updated on June 8, 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

vantage6 lacks brute-force protection on change password functionalityGHSA-j6g5-p62x-58hw

Fix: vantage6/vantage6@e0f1841

GHSA-j6g5-p62x-58hw is a CWE-307 vulnerability in vantage6. A fix is available for vantage6 — see the affected versions and patch details below.

Also known asCVE-2025-43863PYSEC-2025-220

Published

Jun 12, 2025

Updated

Jun 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 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-j6g5-p62x-58hw.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from 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

vantage6 is an open source framework built to enable, manage and deploy privacy enhancing technologies like Federated Learning and Multi-Party Computation. If attacker gets access to an authenticated session, they can try to brute-force the user password by using the change password functionality: they can call that route infinitely which will return the message that password is wrong until it is correct. This vulnerability is fixed in 4.11.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`vantage6`	all versions	4.11.0`pip install --upgrade 'vantage6==4.11.0'`

Affected Products

1 product · 1 configurations

Application

vantage6vantage6

< 4.11.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vantage6, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vantage6 to 4.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j6g5-p62x-58hw 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.

Frequently Asked Questions

### Impact If attacker gets access to an authenticated session, they can try to brute-force the user password by using the change password functionality: they can call that route infinitely which will return the message that password is wrong until it is correct ### Patches This issue has been patched in version 4.11.0 ### Workarounds None

O3 Security · Impact-Aware SCA

Is GHSA-j6g5-p62x-58hw in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works