LiveActive security incident?Get immediate response
CVE Record

CVE-2026-33816: CVE-2026-33816 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-33816 is reported as a critical memory-safety issue in the Go pgx PostgreSQL driver package pgproto3. The provided data rates it 9.8 CVSS, meaning unauthenticated network attack is theoretically possible. The bundle does not provide exploit details, a fixed upstream version, or proof of active exploitation.

Executive priority

Treat this as high-priority inventory and patch validation because the severity is critical and the impact could be full compromise. Urgency should be tempered by the lack of active-exploitation evidence and incomplete affected-version details in the provided bundle.

Technical view

The source bundle identifies github.com/jackc/pgx/v5/pgproto3 with CWE-787 out-of-bounds write and CWE-697 incorrect comparison. CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H indicates possible confidentiality, integrity, and availability impact. Affected version data is limited and lists version "0", so confirm against GO-2026-4772 and vendor advisories.

Likely exposure

Most likely exposure is Go software or vendor products that include github.com/jackc/pgx/v5/pgproto3, directly or transitively through pgx/v5. Red Hat advisories and CSAF/VEX references suggest downstream product impact may vary by packaging and product status.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. CVSS suggests remote, unauthenticated exploitability, but the supplied sources do not include exploit mechanics, public exploitation status, or affected runtime conditions.

Researcher notes

The key uncertainty is affected-version precision: the bundle names pgproto3 and version "0" while defaultStatus is "unaffected". Do not assume all pgx deployments are exploitable. Correlate GO-2026-4772, CVE List data, Red Hat VEX, and product errata before declaring exposure.

Mitigation direction

  • Inventory direct and transitive use of github.com/jackc/pgx/v5 and pgproto3.
  • Check GO-2026-4772 for authoritative Go package remediation guidance.
  • Apply relevant Red Hat errata for affected Red Hat products.
  • If no fixed version is listed, follow vendor guidance before changing versions.
  • Monitor CVE and vendor advisories for revised affected-version data.

Validation and detection

  • Review go.mod, go.sum, SBOMs, and dependency lockfiles for pgx/v5 usage.
  • Compare installed versions against GO-2026-4772 and vendor advisory status.
  • Check Red Hat CSAF/VEX for product-specific affected or not-affected statements.
  • Run approved dependency vulnerability scanners against built artifacts and source.
  • Document exceptions where vendor data says the product is unaffected.
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-697: 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-33816 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
22Source 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-33816Attack 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:14.142Z: Reported to Red Hat.
  • 2026-04-07T15:19:24.529Z: 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-697CWE-787

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

CWE-697 · source CWE mapping

Incorrect Comparison

Incorrect Comparison represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs
CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs