Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-33815 critical CVSS 9.8

Out-of-Bounds Write in github.com/jackc/pgx/v5 (CVE-2026-33815)

Summary

Out-of-bounds write in github.com/jackc/pgx/v5 (CVE-2026-33815). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 5.9.0 or later.

Original description

The description as published by the source.

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

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2026-33815 was discovered in github.com/jackc/pgx/v5.
In plain terms, it is an out-of-bounds write that can let attackers hijack the program.
Severity is Critical (CVSS 9.8/10). If exploited, attackers can fully take over the affected system.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "github.com/jackc/pgx/v5 CVE-2026-33815".

CVE-2026-33815 (github.com/jackc/pgx/v5). Severity: Critical / CVSSv3 9.8. Category: CWE-787.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2026-33815) in github.com/jackc/pgx/v5. In plain words, it is an out-of-bounds write that can let attackers hijack the program.

📍 Affected scope

Target versions of github.com/jackc/pgx/v5 (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Critical (CVSS 9.8/10). If exploited, attackers can fully take over the affected system.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-787)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/jackc/pgx/v5' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/jackc/pgx/v5 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/jackc/pgx/v5 to 5.9.0

    ステージング環境で 5.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/jackc/pgx/v5
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"5.9.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details