How severe is GHSA-4v7v-gqf9-ww2g?

No CVSS score has been assigned to GHSA-4v7v-gqf9-ww2g yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-4v7v-gqf9-ww2g?

GHSA-4v7v-gqf9-ww2g affects the following packages: vyper (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-4v7v-gqf9-ww2g?

Update vyper to 0.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4v7v-gqf9-ww2g is resolved across your whole dependency graph.

How do I detect GHSA-4v7v-gqf9-ww2g in my PyPI dependencies?

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

How do I mitigate GHSA-4v7v-gqf9-ww2g 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-4v7v-gqf9-ww2g actively exploited in the wild?

No public exploit code has been indexed for GHSA-4v7v-gqf9-ww2g 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.

When was GHSA-4v7v-gqf9-ww2g published, and has it been updated?

GHSA-4v7v-gqf9-ww2g was published on October 6, 2026 and was last updated on October 6, 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

Vyper: Call stack corruption when passing complex type containing non-base type members as argumentGHSA-4v7v-gqf9-ww2g

Fix: vyperlang/vyper#2184

GHSA-4v7v-gqf9-ww2g is a security vulnerability in vyper. A fix is available for vyper — see the affected versions and patch details below.

Published

Oct 6, 2026

Updated

Oct 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 6, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍vyper

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

When we pass a multi-dimensional array (like [[1, 2], [3, 4]]) as an argument to internal/external functions we get incorrect output. This is due to a stack management issue, because it was assumed that the size of each subtype of an array/struct is 32, which is not always correct.

Example code:

@internal
def test_input(arr: int128[2][1], i: int128) -> (int128[2][1], int128):
    return arr, i

@external
def test_values(arr: int128[2][1], i: int128) -> (int128[2][1], int128):
    return self.test_input(arr, i)

Please see #2183 for further information

Patches

This problem was fixed in #2184, and released as a part of v0.2.6.

Affected Packages

1 total 1 fixed

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

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for vyper, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update vyper to 0.2.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4v7v-gqf9-ww2g 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 When we pass a multi-dimensional array (like `[[1, 2], [3, 4]]`) as an argument to internal/external functions we get incorrect output. This is due to a stack management issue, because it was assumed that the size of each subtype of an array/struct is 32, which is not always correct. Example code: ```python @internal def test_input(arr: int128[2][1], i: int128) -> (int128[2][1], int128): return arr, i @external def test_values(arr: int128[2][1], i: int128) -> (int128[2][1], int128): return self.test_input(arr, i) ``` Please see #2183 for further information ### Patches T

O3 Security · Impact-Aware SCA

Is GHSA-4v7v-gqf9-ww2g in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works