Answer in brief
CVE-2024-27928 records a Medium severity (CVSS 5.9) vulnerability in Vantage6: 2FA can be circumvented with hacked email access. The current sources do not mark it as known exploited. The current feed maps vantage6 (pip), vantage6 (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps vantage6 (pip), vantage6 (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vantage6pip | <5.0.0 | 5.0.0 |
| vantage6pypi | >=0 <5.0.0 | 5.0.0 |
Published upstream
Jun 5, 2026
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Jun 11, 2026
### Impact If an attacker hacks into a vantage6 user's email account, they can 1) reset the password via email and then 2) reset the 2FA token via email. This way they reduce 2FA to 1FA (email access). Note that most email providers require 2FA to access email, so this issue is not very likely to cause issues. ### Proposed solution Many web apps do not provide functionality to reset 2FA token (probably for this reason), but provide recovery codes as well. It would be better to provide these recovery codes to the user 1 time and then delete the option to reset it. An alternative may be to only let server administrators reset 2FA token. However, this has as disadvantage that a hacked email account may send messages to the server admin to reset them, which they may fall for. ### Patches No ### Workarounds No
Quoted source text, attributed separately from HOL analysis.