# vantage6 vulnerable to Observable Response Discrepancy

Advisory record · `GHSA-36gx-9q6h-g429`

- **Identifiers:** `GHSA-36gx-9q6h-g429` · `CVE-2022-39228` · `PYSEC-2023-313` · `PYSEC-2023-52`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-203](https://cwe.mitre.org/data/definitions/203.html) · [CWE-204](https://cwe.mitre.org/data/definitions/204.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-204](https://agentprime.io/advisories/tag/cwe-204.md)
- **Published:** 28 Feb 2023
- **Updated:** 9 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 28 Feb 2023, 23:18 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `vantage6` (PyPI): affected `<3.8.0`; fixed in `3.8.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> vantage6 versions before 3.8.0 are vulnerable to an observable response discrepancy in login. The login error for a wrong username or password is the same, but a user account is temporarily blocked after repeated wrong passwords, so an attacker can still determine which usernames exist. Upgrade to vantage6 3.8.0 or later. The source lists no workaround.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0060, the 48th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-36gx-9q6h-g429)

## Sources

- [GitHub Advisory Database: GHSA-36gx-9q6h-g429](https://github.com/advisories/GHSA-36gx-9q6h-g429)
- [OSV: GHSA-36gx-9q6h-g429](https://osv.dev/vulnerability/GHSA-36gx-9q6h-g429)
- <https://github.com/vantage6/vantage6/security/advisories/GHSA-36gx-9q6h-g429>
- <https://nvd.nist.gov/vuln/detail/CVE-2022-39228>
- <https://github.com/vantage6/vantage6/issues/59>
- <https://github.com/vantage6/vantage6/pull/281>
- <https://github.com/vantage6/vantage6/commit/ab4381c35d24add06f75d5a8a284321f7a340bd2>
- <https://github.com/pypa/advisory-database/tree/main/vulns/vantage6/PYSEC-2023-313.yaml>
- <https://github.com/pypa/advisory-database/tree/main/vulns/vantage6/PYSEC-2023-52.yaml>
- <https://github.com/vantage6/vantage6>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-36gx-9q6h-g429>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-36gx-9q6h-g429/>. Everything for agents: <https://agentprime.io/llms.txt>.