CVE-2026-6469

LOWPre-NVD 3.83.8—
EchelonGraph scoreMEDIUM confidence

Score 3.8 from GitHub Security Advisory (severity: LOW) published 2026-08-13. a secondary CVSS source baseline 3.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
3.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.8Exploit: None knownExposed: 0

A fix is available — apply it.

Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of dependent statistics objects to the current user. This wrongly allows the table owner to run DROP STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the prior statistics object owner. DROP TABLE remains able to remove statistics objects, so this exploit achieves nothing in many ownership arrangements. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
3.8
EG Score
3.8(medium)
EG Risk
17(Track)
EG Risk 17/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
Severity38% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 29, 2026

References (1)

Vendor Advisories for CVE-2026-6469(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-09-18ubuntu

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

(11 across 7 ecosystems)
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions)15.19-0+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)17.11-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)18.6-1—

Weakness Classification(1)

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

All Vendor Advisories

(2)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 59× 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.

  1. 2026-09-18 22:10 UTCEG score recompute
  2. 2026-09-18 22:10 UTCVendor advisory
  3. 2026-09-18 22:10 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-16 14:08 UTCEPSS rescore
  6. 2026-09-16 05:15 UTCEPSS rescore
  7. 2026-09-16 02:44 UTCEG score recompute
  8. 2026-09-16 02:44 UTCVendor advisory
  9. 2026-09-16 02:44 UTCGHSA enrichment
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-13 07:38 UTCEG score recompute
  12. 2026-09-13 07:38 UTCVendor advisory
  13. 2026-09-13 07:38 UTCGHSA enrichment
  14. 2026-09-12 15:02 UTCEPSS rescore
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 09:37 UTCEPSS rescore
  17. 2026-09-10 12:32 UTCEG score recompute
  18. 2026-09-10 12:32 UTCVendor advisory
  19. 2026-09-10 12:32 UTCGHSA enrichment
  20. 2026-09-08 22:01 UTCEPSS rescore
  21. 2026-09-07 16:37 UTCEG score recompute
  22. 2026-09-07 16:37 UTCVendor advisory
  23. 2026-09-07 16:37 UTCGHSA enrichment
  24. 2026-09-07 16:01 UTCEPSS rescore
  25. 2026-09-06 13:47 UTCEPSS rescore
Show 54 more
  1. 2026-09-05 15:31 UTCEPSS rescore
  2. 2026-09-04 13:39 UTCEG score recompute
  3. 2026-09-04 13:39 UTCVendor advisory
  4. 2026-09-04 13:39 UTCGHSA enrichment
  5. 2026-09-04 05:07 UTCEPSS rescore
  6. 2026-09-02 14:12 UTCEPSS rescore
  7. 2026-09-01 18:33 UTCEG score recompute
  8. 2026-09-01 18:33 UTCVendor advisory
  9. 2026-09-01 18:33 UTCGHSA enrichment
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-29 23:26 UTCEG score recompute
  15. 2026-08-29 23:26 UTCVendor advisory
  16. 2026-08-29 23:26 UTCGHSA enrichment
  17. 2026-08-29 23:14 UTCEG score recompute
  18. 2026-08-29 23:14 UTCVendor advisory
  19. 2026-08-29 23:14 UTCGHSA enrichment
  20. 2026-08-28 21:42 UTCEPSS rescore
  21. 2026-08-28 00:49 UTCEG score recompute
  22. 2026-08-28 00:49 UTCVendor advisory
  23. 2026-08-28 00:49 UTCGHSA enrichment
  24. 2026-08-26 14:47 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
  26. 2026-08-25 05:16 UTCEG score recompute
  27. 2026-08-25 05:16 UTCVendor advisory
  28. 2026-08-25 05:16 UTCGHSA enrichment
  29. 2026-08-23 00:19 UTCEPSS rescore
  30. 2026-08-22 10:10 UTCEG score recompute
  31. 2026-08-22 10:10 UTCVendor advisory
  32. 2026-08-22 10:10 UTCGHSA enrichment
  33. 2026-08-21 23:49 UTCEPSS rescore
  34. 2026-08-20 22:56 UTCEPSS rescore
  35. 2026-08-19 17:04 UTCEPSS rescore
  36. 2026-08-19 15:04 UTCGHSA enrichment
  37. 2026-08-18 15:29 UTCEG score recompute
  38. 2026-08-18 15:29 UTCGHSA enrichment
  39. 2026-08-18 13:49 UTCEPSS rescore
  40. 2026-08-18 13:49 UTCEPSS rescore
  41. 2026-08-17 13:47 UTCEPSS rescore
  42. 2026-08-16 14:56 UTCEPSS rescore
  43. 2026-08-16 14:56 UTCEPSS rescore
  44. 2026-08-16 11:35 UTCEG score recompute
  45. 2026-08-16 11:35 UTCGHSA enrichment
  46. 2026-08-16 02:15 UTCEPSS rescore
  47. 2026-08-15 01:31 UTCEPSS rescore
  48. 2026-08-13 16:29 UTCEG score recompute
  49. 2026-08-13 16:29 UTCGHSA enrichment
  50. 2026-08-13 16:01 UTCEG score recompute
  51. 2026-08-13 16:01 UTCGHSA enrichment
  52. 2026-08-13 13:35 UTCEG score recompute
  53. 2026-08-13 13:17 UTCEG score recompute
  54. 2026-08-13 13:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-6469?
CVE-2026-6469 is a low vulnerability published on August 13, 2026. Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of dependent statistics objects to the current user. This wrongly allows the table owner to run DROP STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the…
When was CVE-2026-6469 disclosed?
CVE-2026-6469 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6469 actively exploited?
CVE-2026-6469 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.3% of all scored CVEs.
What is the CVSS score of CVE-2026-6469?
CVE-2026-6469 has a CVSS v3 base score of 3.8 (NVD).
How do I remediate CVE-2026-6469?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6469, 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-6469

Explore →

Is Your Infrastructure Affected by CVE-2026-6469?

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

Start Free Scan →Browse All CVEs