CVE-2026-33815 | CVE-2026-33815 in github.com/jackc/pgx

Memory-safety vulnerability in github.com/jackc/pgx/v5.

Published: 2026-04-07 Last update: 2026-05-21 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-33815 is rated Moderate Risk (41.4/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.02%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-33815

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.06% 0.02% -0.03%
2 2026-04-13 0.02% 0.06% +0.04%
3 2026-04-08 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-33815

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-33815

GitHub Security Advisory for CVE-2026-33815

GHSA-xgrm-4fwx-7qm8 · Severity: critical · Ecosystem: go — pgx contains memory-safety vulnerability

OS Trackers for CVE-2026-33815

vendor priority summary link
debian not yet assigned CVE-2026-33815 not yet assigned priority: Debian including 1 source packages (golang-github-jackc-pgx-v5), 2 status rows across 2 suites (forky, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2026-33815
redhat high — https://access.redhat.com/security/cve/CVE-2026-33815
suse high CVE-2026-33815 severity important: SUSE including 4 source package names (cosign, cosign-bash-completion, cosign-zsh-completion, grafana), 17 product×package rows across 14 product lines (SUSE Linux Enterprise High Performance Computing 15 SP4-LTSS, SUSE Linux Enterprise High Performance Computing 15 SP5-LTSS, … (14 product lines)): Known Not Affected 17. https://www.suse.com/security/cve/CVE-2026-33815/
ubuntu medium CVE-2026-33815 medium priority: Ubuntu including 1 source packages (golang-github-jackc-pgx-v5), 4 status rows across 4 suites (jammy, noble, questing, upstream): DNE 3, needs-triage 1. https://ubuntu.com/security/CVE-2026-33815

Affected software / configurations for CVE-2026-33815

Vendor Product Version Raw CPE
jackc pgx — cpe:2.3:a:jackc:pgx:*:*:*:*:*:go:*:*

References for CVE-2026-33815

URL Tags
https://pkg.go.dev/vuln/GO-2026-4771 Third Party Advisory
cvelogic Threat Intelligence