pypi package report

Is vyper safe?

47 known vulnerabilities, worst severity CRITICAL.

// reach

0 direct dependencies

none carry a known advisory

    1 packages depend on it

    an advisory here reaches each of them

    Create a free accountfor every dependency path, dependent and what to upgrade
    // ai model usage

    No published models are known to use this package.


    cvss
    9.8
    critical

    CVSS v3.1 base score out of 10

    epss
    1.5%
    medium

    chance of exploitation in 30 days, 75th percentile of all CVEs

    xyz score
    4.0
    medium

    CyberXYZ composite out of 10

    fig. 01 — GHSA-52xq-j7v9-v4v2, the advisory selected below

    // 47 advisories

    GHSA-52xq-j7v9-v4v2

    CRITICALGitHub ratingCVE-2024-24563
    // summary

    Arrays can be keyed by a signed integer, while they are defined for unsigned integers only. The typechecker doesn't throw when spotting the usage of an int as an index for an array. Typically, negative integers are filtered out at runtime by the bounds checker, but small enough (i.e. large in magnitude, ex. -2**255 + 5) quantities combined with large enough arrays (at least 2**255 in length) can pass the bounds checker, resulting in unexpected behavior.

    A contract search was performed, and no production contracts were found to be impacted.

    // details

    The typechecker allows the usage of signed integers to be used as indexes to arrays. The vulnerability is present in different forms in all versions. Here is an example from 0.3.10: https://github.com/vyperlang/vyper/blob/c150fc49ee9375a930d177044559b83cb95f7963/vyper/semantics/types/subscriptable.py#L127-L137

    As can be seen, the validation is performed against IntegerT.any().

    // poc

    If the array is sufficiently large, it can be indexed with a negative value:

    arr: public(uint256[MAX_UINT256])
    
    @external
    def set(idx: int256, num: uint256):
        self.arr[idx] = num

    For signed integers, the 2's complement representation is used. Because the array was declared very large, the bounds checking will pass (negative values will simply be represented as very large numbers): https://github.com/vyperlang/vyper/blob/a1fd228cb9936c3e4bbca6f3ee3fb4426ef45490/vyper/codegen/core.py#L534-L541

    // patches

    Patched in https://github.com/vyperlang/vyper/pull/3817.

    // impact

    There are two potential vulnerability classes: unpredictable behavior and accessing inaccessible elements.

    • If it is possible to index an array with a negative integer without reverting, this is most likely not anticipated by the developer and such accesses can cause unpredictable behavior for the contract.
    • If a contract has an invariant in the form assert index < x where both index and x are signed integers, the developer might suppose that no elements on indexes y | y >= x are accessible. However, by using negative indexes this can be bypassed.

    The contract search found no production contracts impacted by these two classes of issues.

    // cvss v3.1 vector

    CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

    Attack vector
    Network
    Attack complexity
    Low
    Privileges required
    None
    User interaction
    None
    Scope
    Unchanged
    Confidentiality
    High
    Integrity
    High
    Availability
    High

    Checked 2026-11-08 at 00:40 UTC. The most recent advisory here was published 2026-10-06. Updated continuously from NVD, GHSA, OSV and CNA feeds.

    Think a verdict here is wrong? Tell us — we respond within 2 business days.