LiveActive security incident?Get immediate response
CVE Record

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

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

CriticalCVSS 9.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-33815 is a critical memory-safety issue in the Go pgx PostgreSQL protocol package. The source bundle rates it CVSS 9.8, meaning a network attacker could potentially cause serious confidentiality, integrity, and availability impact if an exposed application uses the vulnerable component.

Executive priority

Treat this as urgent for any business-critical Go service using pgx in exposed or multi-tenant paths. The severity is critical, but exploitation is not confirmed in the supplied evidence, so prioritize rapid inventory and vendor-guided patching over emergency assumptions.

Technical view

The bundle identifies github.com/jackc/pgx/v5/pgproto3 with CWE-129 and CWE-787, indicating improper array indexing and out-of-bounds write risk. Public details provided here do not include vulnerable version ranges beyond the package entry, exploit mechanics, or exact upstream fixed version.

Likely exposure

Exposure is most likely in Go services that import github.com/jackc/pgx/v5/pgproto3 directly or through pgx and process untrusted PostgreSQL protocol traffic. Red Hat references suggest downstream packaged products may also need vendor-specific review.

Exploitation context

The bundle lists KEV as false and provides no cited evidence of active exploitation. The CVSS vector indicates remote, unauthenticated, low-complexity exploitation is considered possible, but no exploit status or operational details are substantiated here.

Researcher notes

Evidence is limited to high-level vulnerability metadata, CWE categories, Go vulnerability entry, and Red Hat references. Avoid assuming exact vulnerable ranges, exploit primitives, or affected downstream products without consulting the linked advisories and package metadata.

Mitigation direction

  • Inventory Go applications for github.com/jackc/pgx/v5/pgproto3 dependency use.
  • Review GO-2026-4771 and upstream pgx guidance for fixed versions.
  • Apply applicable Red Hat errata for affected Red Hat products.
  • Prioritize internet-facing services and services handling untrusted database protocol traffic.
  • Use vendor guidance where exact affected and fixed versions are unclear.

Validation and detection

  • Check software bills of materials for github.com/jackc/pgx/v5 references.
  • Review go.mod and dependency lock data for pgx module versions.
  • Map affected services to exposed network paths and trust boundaries.
  • Confirm whether applicable Red Hat CSAF VEX entries mark products affected or fixed.
  • Verify remediation by comparing deployed dependency versions against vendor advisories.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-129: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-33815 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
19Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP
8.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L2.85.5redhat-SADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-33815Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
redhat-SADPgithub.com/jackc/pgx/v5: github.com/jackc/pgx: Memory-safety vulnerability
other:Red Hat severity ratingcvssV3_1
  • 2026-04-07T16:01:25.130Z: Reported to Red Hat.
  • 2026-04-07T15:19:24.344Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
github.com/jackc/pgx/v5github.com/jackc/pgx/v5/pgproto3github.com/jackc/pgx/v5/pgproto3, 0unaffected
Weakness

CWE details

CWE-129CWE-787

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.