NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2018-18482 — pg-query

MEDIUM

CVE-2018-18482 is a medium-severity (CVSS 6.5) CWE-772 vulnerability in pg-query. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for pg-query — see the affected versions and patch details below.

libpg_query memory leak

Also known asGHSA-vm3q-58wm-2r2xPYSEC-2018-154PYSEC-2026-895
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk
0.00%0.55%1.11%1.66%0.3%1.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐍pg-query🐍pglast

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

An issue was discovered in libpg_query 10-1.0.2. There is a memory leak in pg_query_raw_parse in pg_query_parse.c, which might lead to a denial of service.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIpg-queryall versions0.28pip install --upgrade 'pg-query==0.28'
🐍PyPIpglastall versions0.28pip install --upgrade 'pglast==0.28'

Affected Products

1 product · 1 configurations
Application
libpg querylibpg_query_project
1 version
10-1.0.2
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

An issue was discovered in libpg_query 10-1.0.2. There is a memory leak …

github.comNVDOct 2019

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update pg-query to 0.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-18482 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

An issue was discovered in libpg_query 10-1.0.2. There is a memory leak in pg_query_raw_parse in pg_query_parse.c, which might lead to a denial of service.
O3 Security · Impact-Aware SCA

Is CVE-2018-18482 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2018-18482: pg-query DoS — Fixed in 0.28