npm package report

Is pg-native safe?

1 known vulnerability, worst severity HIGH.

// reach

1 direct dependencies

none carry a known advisory

    6 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

    Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

    cvss
    7.5
    high

    CVSS v3.1 base score out of 10

    epss
    1.4%
    medium

    chance of exploitation in 30 days, 72nd percentile of all CVEs

    xyz score
    4.0
    medium

    CyberXYZ composite out of 10

    fig. 01 — GHSA-j32j-2hxv-rqf7, the advisory selected below

    // 1 advisories

    GHSA-j32j-2hxv-rqf7

    HIGHGitHub ratingCVE-2022-25852

    pg-native before 3.0.1 and libpq before 1.8.10 are vulnerable to Denial of Service (DoS) when the addons attempt to cast the second argument to an array and fail. This happens for every non-array argument passed. Note: pg-native is a mere binding to npm's libpq library, which in turn has the addons and bindings to the actual C libpq library. This means that problems found in pg-native may transitively impact npm's libpq.

    // cvss v3.1 vector

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

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

    Checked 2026-11-06 at 22:03 UTC. The most recent advisory here was published 2022-06-18. Updated continuously from NVD, GHSA, OSV and CNA feeds.

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