vantage6 vulnerable to Improper Preservation of Permissions (CVE-2023-22738) | HOL Guard CVE

Medium · CVSS 6.5CVE-2023-22738GHSA-VVJV-97J8-94XH

vantage6 vulnerable to Improper Preservation of Permissions

Answer in brief

CVE-2023-22738 records a Medium severity (CVSS 6.5) vulnerability in vantage6 vulnerable to Improper Preservation of Permissions. The current sources do not mark it as known exploited. The current feed maps 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.

Published Feb 28, 2023Updated Sep 10, 2026Source checked Sep 10, 2026First seen by HOL Sep 10, 2026Material review Sep 10, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 6.5
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 6.5. 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.

Affected scope and exposure questions

The current feed maps vantage6 (pypi). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
vantage6pypi	>=0 <3.8.0	3.8.0

Recommended response

Check inventory. Check lockfiles and deployed manifests for vantage6.
Review the reported fix. Update vantage6 to 3.8.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Feb 28, 2023
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source description

### Impact Assigning existing users to a different organization is currently possible. It may lead to unintended access: if a user from organization A is accidentally assigned to organization B, they will retain their permissions and therefore might be able to access stuff they should not be allowed to access. ### Patches Update to 3.8.0 ### Workarounds None ### References None ### For more information If you have any questions or comments about this advisory: * Email us at [[email protected]](mailto:[email protected])

Quoted source text, attributed separately from HOL analysis.