CVE-2026-33816

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.0%, top 94% 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: epss, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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)
EPSS
42.7%
KEV
Not listed

Published

April 7, 2026

Last Modified

July 9, 2026

Advisory Details (9)

Auto-updated Jul 9, 2026
Patch available. Sources: redhat.
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

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:19137
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-4772 - Go Packages

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

Vendor Advisories for CVE-2026-33816(17)

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

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhacm2/acm-grafana-rhel9:17809268052026-06-11redhat
redhatrhtas/createtree-rhel9:17800535722026-06-08redhat
redhatrhtas/trillian-logsigner-rhel9:17800535722026-06-08redhat
redhatrhacm2/acm-grafana-rhel9:17806770032026-06-08redhat
redhatrhtas/updatetree-rhel9:17800535722026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-grafana-rhel9:17799252732026-06-08redhat
redhatmulticluster-globalhub/multicluster-globalhub-rhel9-operator:17792099922026-06-02redhat
redhatcryostat/cryostat-storage-rhel9:4.2.0-132026-05-26redhat
redhatgo-fdo-server-0:1.0.1-1.el10_22026-05-19redhat
redhatgo-fdo-server-main-1.0.1-0.1.hum12026-05-06redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:17779866302026-05-05redhat
redhatadvanced-cluster-security/rhacs-scanner-v4-rhel8:17779764892026-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

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/jackc/pgx/v5—5.9.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 40× 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 119 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33816?
CVE-2026-33816 is a critical vulnerability published on April 7, 2026. Memory-safety vulnerability in github.com/jackc/pgx/v5.
When was CVE-2026-33816 disclosed?
CVE-2026-33816 was first published in the National Vulnerability Database on April 7, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33816 actively exploited?
CVE-2026-33816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-33816?
CVE-2026-33816 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-33816?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33816, 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-33816

Explore →

Is Your Infrastructure Affected by CVE-2026-33816?

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

Start Free Scan →Browse All CVEs