Is CVE-2026-33815 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33815 being exploited in the wild.

How severe is CVE-2026-33815?

Critical severity, with a CVSS score of 9.8, published 7 April 2026.

Which products and versions are affected?

github.com/jackc/pgx/v5 (Go) < 5.9.0, SEMVER:introduced=0,fixed=5.9.0; github.com/jackc/pgx/v5/pgproto3 (Go) < 5.9.0; Jack Christensen Pgproto3 < 5.9.0; Jack Christensen Pgx < 5.9.0, before v5.9.0.

Is there a fix for CVE-2026-33815?

Yes. github.com/jackc/pgx/v5 (Go): upgrade to 5.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-33815 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-33815?

Check whether you run github.com/jackc/pgx/v5 (Go), github.com/jackc/pgx/v5/pgproto3 (Go), Jack Christensen Pgproto3 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33815: Jackc pgx memory-safety vulnerability in pgproto3

Q: Is there a fix for CVE-2026-33815?

Yes. github.com/jackc/pgx/v5 (Go): upgrade to 5.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-33815 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-33815?

Check whether you run github.com/jackc/pgx/v5 (Go), github.com/jackc/pgx/v5/pgproto3 (Go), Jack Christensen Pgproto3 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33815 · Severity: critical · CVSS 9.8 · Published 2026-04-07

pgx is a widely used software library that allows Go applications to communicate with PostgreSQL databases. A critical security flaw has been identified that could allow an attacker to interfere with the application's memory. This could lead to unauthorized access to sensitive data, system crashes, or the ability for an attacker to take control of the application.

Technologies: github.com/jackc/pgx/v5 (Go), Jack Christensen Pgx. Vendors: Go, Jack Christensen.

Quick answers

Is CVE-2026-33815 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33815 being exploited in the wild.
How severe is CVE-2026-33815?: Critical severity, with a CVSS score of 9.8, published 7 April 2026.
Which products and versions are affected?: github.com/jackc/pgx/v5 (Go) < 5.9.0, SEMVER:introduced=0,fixed=5.9.0; github.com/jackc/pgx/v5/pgproto3 (Go) < 5.9.0; Jack Christensen Pgproto3 < 5.9.0; Jack Christensen Pgx < 5.9.0, before v5.9.0.
Is there a fix for CVE-2026-33815?: Yes. github.com/jackc/pgx/v5 (Go): upgrade to 5.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-33815 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-33815?: Check whether you run github.com/jackc/pgx/v5 (Go), github.com/jackc/pgx/v5/pgproto3 (Go), Jack Christensen Pgproto3 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/jackc/pgx/v5 (Go): upgrade to 5.9.0 or later
```
go get github.com/jackc/pgx/v5@v5.9.0
```

Technical details

A memory-safety vulnerability exists in the pgx toolkit (github.com/jackc/pgx/v5) prior to version 5.9.0. The flaw allows for potential memory corruption or unauthorized memory access via the network without requiring authentication or user interaction. While specific CWE details are not provided in the advisory, the CVSS score of 9.8 and the 'memory-safety' classification suggest a high risk of remote code execution (RCE) or information disclosure. The issue is addressed in version 5.9.0.

Affected products

jackc pgx < 5.9.0

Identifiers

CVE-2026-33815
GHSA-xgrm-4fwx-7qm8
GO-2026-4771

Timeline

2026-04-07: disclosed
2026-04-07: advisory
2026-04-10: other: GitHub reviewed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.