# CVE-2026-6469: PostgreSQL ALTER TABLE ALTER TYPE resets extended statistics ownership

> PostgreSQL incorrectly reassigns extended statistics ownership during ALTER TABLE, allowing table owners to modify or drop statistics objects they do not own.

- **Severity:** Low 3.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Aug 2026
- **Updated:** 29 Aug 2026
- **Also known as:** ALPINE-CVE-2026-6469, AZL-95714, BELL-CVE-2026-6469, BIT-postgresql-2026-6469, DEBIAN-CVE-2026-6469, ECHO-3f3c-1720-1cf2, GHSA-5qv4-w274-5rpv, MINI-7284-56vc-qcrh, MINI-7r8m-5wvp-h58m, MINI-ccc7-9jjx-rc2f, MINI-f8fv-3gjf-cmpq, MINI-r5q8-pmhp-4gcr, MINI-rrqj-w8fv-8q96, UBUNTU-CVE-2026-6469

## What is CVE-2026-6469?

CVE-2026-6469 is a low-severity missing authorization vulnerability in Postgresql Postgresql, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-708 (Incorrect Ownership Assignment)

## Which versions are affected by CVE-2026-6469?

1 open source package ship an affected version, including postgresql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `postgresql` | Bitnami | All versions | 14.24.0, 15.19.0, 16.15.0, 17.11.0, 18.5.0 |

Products: Postgresql Postgresql.

## How do I fix CVE-2026-6469?

Upgrade postgresql to a fixed version for your release line: 14.24.0, 15.19.0, 16.15.0 or 17.11.0.

## Is CVE-2026-6469 being exploited?

There is no known exploitation of CVE-2026-6469 in the wild and no public exploit code.

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6469 and fix it if it is affected.

What it is: CVE-2026-6469 is a low-severity missing authorization vulnerability in Postgresql Postgresql, published on 13 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6469 in the wild and no public exploit code.

Affected packages and fixed versions:
- postgresql (Bitnami): affected all versions; fixed in 14.24.0, 15.19.0, 16.15.0, 17.11.0, 18.5.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6469/ (Markdown: https://insights.sbomify.com/CVE-2026-6469/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6469
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6469
- OSV: https://osv.dev/vulnerability/CVE-2026-6469

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6469/
Summaries are generated and may contain mistakes; the official description above is the record.