CVE-2026-33815

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cisa-adp, epss
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

April 7, 2026

Last Modified

August 24, 2026

Advisory Details (10)

Auto-updated Aug 24, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24482
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24479
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:24475
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22423
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:17789
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13829
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:13791
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11217
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:11070
generic

GO-2026-4771 - Go Packages

https://pkg.go.dev/vuln/GO-2026-4771

Vendor Advisories for CVE-2026-33815(17)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(15)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatodf4/rook-ceph-rhel9-operator:17836692192026-07-16redhat
redhatflightctl-0:1.1.3-1.el9em2026-07-16redhat
redhatflightctl-0:1.0.3-1.el9em2026-07-08redhat
redhatcustom-metrics-autoscaler/custom-metrics-autoscaler-rhel9-operator:17799535352026-06-17redhat
redhatrhacm2/acm-grafana-rhel9:17809268052026-06-11redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17799252732026-06-08redhat
redhatrhtas/trillian-logsigner-rhel9:17800535722026-06-08redhat
redhatrhtas/updatetree-rhel9:17800535722026-06-08redhat
redhatrhacm2/acm-grafana-rhel9:17806770032026-06-08redhat
redhatrhtas/createtree-rhel9:17800535722026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17792099922026-06-02redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-132026-05-26redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:17779764892026-05-05redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:17779866302026-05-05redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:17773077912026-04-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 2 ecosystems)
Go(2)
PackageVulnerable rangeFixed inDependents
github.com/jackc/pgx/v5—5.9.0—
github.com/jackc/pgx/v5/pgproto3—5.9.0—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
golang-github-jackc-pgx-v55.8.0-15.9.2-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 107× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 232 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-24 13:31 UTCVendor advisory
  4. 2026-08-24 12:27 UTCEG score recompute
  5. 2026-08-24 12:27 UTCVendor advisory
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-21 23:49 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-20 22:55 UTCEPSS rescore
  10. 2026-08-20 13:59 UTCVendor advisory
  11. 2026-08-20 12:45 UTCEG score recompute
  12. 2026-08-20 12:45 UTCVendor advisory
  13. 2026-08-19 17:03 UTCEPSS rescore
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-18 12:21 UTCEG score recompute
  16. 2026-08-18 12:21 UTCVendor advisory
  17. 2026-08-17 13:47 UTCEPSS rescore
  18. 2026-08-17 12:21 UTCVendor advisory
  19. 2026-08-17 12:13 UTCEG score recompute
  20. 2026-08-17 12:13 UTCVendor advisory
  21. 2026-08-16 14:56 UTCEPSS rescore
  22. 2026-08-16 12:27 UTCVendor advisory
  23. 2026-08-16 08:15 UTCEG score recompute
  24. 2026-08-16 08:15 UTCVendor advisory
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-15 01:30 UTCEPSS rescore
  2. 2026-08-14 22:45 UTCVendor advisory
  3. 2026-08-14 18:33 UTCVendor advisory
  4. 2026-08-14 13:28 UTCVendor advisory
  5. 2026-08-14 12:29 UTCVendor advisory
  6. 2026-08-14 09:39 UTCVendor advisory
  7. 2026-08-14 05:27 UTCEG score recompute
  8. 2026-08-14 05:27 UTCVendor advisory
  9. 2026-08-13 22:00 UTCEPSS rescore
  10. 2026-08-13 09:41 UTCVendor advisory
  11. 2026-08-13 04:05 UTCVendor advisory
  12. 2026-08-12 23:53 UTCVendor advisory
  13. 2026-08-12 19:41 UTCEG score recompute
  14. 2026-08-12 19:41 UTCVendor advisory
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-12 12:38 UTCVendor advisory
  17. 2026-08-12 12:13 UTCVendor advisory
  18. 2026-08-12 00:15 UTCVendor advisory
  19. 2026-08-11 19:53 UTCEG score recompute
  20. 2026-08-11 19:53 UTCVendor advisory
  21. 2026-08-11 07:26 UTCVendor advisory
  22. 2026-08-11 03:14 UTCEG score recompute
  23. 2026-08-11 03:14 UTCVendor advisory
  24. 2026-08-11 00:00 UTCEPSS rescore
  25. 2026-08-10 13:22 UTCVendor advisory
  26. 2026-08-10 12:27 UTCVendor advisory
  27. 2026-08-10 10:26 UTCVendor advisory
  28. 2026-08-10 06:14 UTCVendor advisory
  29. 2026-08-10 02:00 UTCVendor advisory
  30. 2026-08-09 21:45 UTCVendor advisory
  31. 2026-08-09 17:33 UTCEG score recompute
  32. 2026-08-09 17:33 UTCVendor advisory
  33. 2026-08-09 13:46 UTCEPSS rescore
  34. 2026-08-09 13:21 UTCVendor advisory
  35. 2026-08-09 09:09 UTCVendor advisory
  36. 2026-08-09 04:57 UTCEG score recompute
  37. 2026-08-09 04:57 UTCVendor advisory
  38. 2026-08-08 16:37 UTCEPSS rescore
  39. 2026-08-08 09:26 UTCVendor advisory
  40. 2026-08-08 05:14 UTCVendor advisory
  41. 2026-08-08 01:02 UTCVendor advisory
  42. 2026-08-07 20:50 UTCVendor advisory
  43. 2026-08-07 16:38 UTCEG score recompute
  44. 2026-08-07 16:38 UTCVendor advisory
  45. 2026-08-07 12:25 UTCVendor advisory
  46. 2026-08-07 12:09 UTCVendor advisory
  47. 2026-08-06 17:36 UTCEG score recompute
  48. 2026-08-06 17:36 UTCVendor advisory
  49. 2026-08-06 13:46 UTCEPSS rescore
  50. 2026-08-06 12:59 UTCVendor advisory
  51. 2026-08-06 08:24 UTCVendor advisory
  52. 2026-08-06 04:12 UTCVendor advisory
  53. 2026-08-06 00:00 UTCEG score recompute
  54. 2026-08-06 00:00 UTCVendor advisory
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-04 15:10 UTCEPSS rescore
  57. 2026-08-04 10:38 UTCEPSS rescore
  58. 2026-08-04 02:35 UTCVendor advisory
  59. 2026-08-03 22:23 UTCVendor advisory
  60. 2026-08-03 13:43 UTCVendor advisory
  61. 2026-08-03 12:49 UTCEG score recompute
  62. 2026-08-03 12:49 UTCVendor advisory
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 02:55 UTCVendor advisory
  65. 2026-08-02 22:43 UTCVendor advisory
  66. 2026-08-02 18:30 UTCVendor advisory
  67. 2026-08-02 14:18 UTCEG score recompute
  68. 2026-08-02 14:18 UTCVendor advisory
  69. 2026-08-02 02:27 UTCEPSS rescore
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-31 13:21 UTCVendor advisory
  72. 2026-07-31 12:35 UTCEG score recompute
  73. 2026-07-31 12:35 UTCVendor advisory
  74. 2026-07-30 16:28 UTCEPSS rescore
  75. 2026-07-30 01:30 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33815?
CVE-2026-33815 is a critical vulnerability published on April 7, 2026. Memory-safety vulnerability in github.com/jackc/pgx/v5.
When was CVE-2026-33815 disclosed?
CVE-2026-33815 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33815 actively exploited?
CVE-2026-33815 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 53.7% of all scored CVEs.
What is the CVSS score of CVE-2026-33815?
CVE-2026-33815 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-33815?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33815, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-33815

Explore →

Is Your Infrastructure Affected by CVE-2026-33815?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs