Memory-safety vulnerability in github.com/jackc/pgx/v5GHSA-9jj7-4m8r-rfcm
CRITICALGHSA-9jj7-4m8r-rfcm is a critical-severity (CVSS 9.8) Out-of-bounds Write vulnerability in github.com/jackc/pgx/v5. A fix is available for github.com/jackc/pgx/v5 — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-9jj7-4m8r-rfcm.
EPSS Exploitation Probability
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
github.com/jackc/pgx/v5Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Memory-safety vulnerability in github.com/jackc/pgx/v5.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/jackc/pgx/v5 | all versions | 5.9.0go get github.com/jackc/pgx/v5@v5.9.0 |
Affected Products
pgxjackcDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jackc/pgx/v5, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/jackc/pgx/v5 to 5.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9jj7-4m8r-rfcm is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.Source: Red Hat security advisory for GHSA-9jj7-4m8r-rfcm (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Cryostat 4 on RHEL 9 | cryostat/cryostat-storage-rhel9:4.2.0-13 | RHSA-2026:17789 |
| Red Hat Enterprise Linux 10 | go-fdo-server-0:1.0.1-1.el10_2 | RHSA-2026:19137 |
| RHEM 1.0 for RHEL 9 | flightctl-0:1.0.3-1.el9em | RHSA-2026:36796 |
| RHEM 1.1 for RHEL 10 | flightctl-0:1.1.3-1.el10em | RHSA-2026:41019 |
| Custom Metric Autoscaler 2.19 | custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel9:1780101236 | RHSA-2026:26636 |
| Custom Metric Autoscaler 2.19 | custom-metrics-autoscaler/custom-metrics-autoscaler-adapter-rhel9:1788361753 | RHSA-2026:62866 |
| Multicluster Global Hub 1.3.4 | multicluster-globalhub/multicluster-globalhub-agent-rhel9:1779210675 | RHSA-2026:22423 |
| Multicluster Global Hub 1.7.4 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779925273 | RHSA-2026:24503 |
Frequently Asked Questions
Is GHSA-9jj7-4m8r-rfcm in your dependencies?
Find it across Go, including transitive dependencies.