GHSA-jqcq-xjh3-6g23 — v2
HIGHGHSA-jqcq-xjh3-6g23 is a high-severity (CVSS 7.5) CWE-129 vulnerability in github.com/jackc/pgproto3/v2. No vendor fix is recorded yet; mitigation options are listed below.
Denial of service in github.com/jackc/pgproto3/v2
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for GHSA-jqcq-xjh3-6g23.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-jqcq-xjh3-6g23 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
github.com/jackc/pgproto3/v2Real-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
The DataRow.Decode function fails to properly validate field lengths. A malicious or compromised PostgreSQL server can send a DataRow message with a negative field length, causing a slice bounds out of range panic.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/jackc/pgproto3/v2 | ≥ 2.0.0 | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/jackc/pgproto3/v2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of github.com/jackc/pgproto3/v2 has shipped for GHSA-jqcq-xjh3-6g23 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jqcq-xjh3-6g23 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-jqcq-xjh3-6g23. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
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.
The PostgreSQL server multicluster-globalhub-manager connects to is either provisioned by the operator itself or specified by the admin managing the deployment. To successfully exploit the vulnerability in this context the attacker would need to compromise the operator-deployed PostgreSQL server to force a crafted…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Enterprise Linux 10 | osbuild-composer-0:165.1-2.el10_2 | RHSA-2026:22450 |
| Red Hat Enterprise Linux 9 | osbuild-composer-0:165.1-2.el9_8 | RHSA-2026:22714 |
| Multicluster Global Hub 1.3.4 | multicluster-globalhub/multicluster-globalhub-agent-rhel9:1779210675 | RHSA-2026:22423 |
| Multicluster Global Hub 1.4.5 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1779579439 | RHSA-2026:22347 |
| Multicluster Global Hub 1.6.5 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1780167118 | RHSA-2026:23345 |
| Red Hat Advanced Cluster Security 4.8 | advanced-cluster-security/rhacs-main-rhel8:1777307791 | RHSA-2026:11070 |
| Red Hat Advanced Cluster Security 4.8 | advanced-cluster-security/rhacs-main-rhel8:1777307791 | RHSA-2026:11217 |
| Red Hat multicluster global hub 1.5.3 | multicluster-globalhub/multicluster-globalhub-grafana-rhel9:1778867753 | RHSA-2026:21769 |
Frequently Asked Questions
Is GHSA-jqcq-xjh3-6g23 in your dependencies?
O3 Security finds GHSA-jqcq-xjh3-6g23 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.