# CVE-2025-31480: aiven-extras allows PostgreSQL Privilege Escalation through format function

> Attackers can escalate privileges to superuser in PostgreSQL databases using the aiven-extras extension due to improper schema qualification.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-33xh-jqgf-6627

## What is CVE-2025-31480?

CVE-2025-31480 is a critical vulnerability in aiven-extras, published on 4 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

aiven-extras is a PostgreSQL extension. This is a privilege escalation vulnerability, allowing elevation to superuser inside PostgreSQL databases that use the aiven-extras package. The vulnerability leverages the format function not being schema-prefixed. Affected users should install 1.1.16 and ensure they run the latest version issuing ALTER EXTENSION aiven_extras UPDATE TO '1.1.16' after installing it. This needs to happen in each database aiven_extras has been installed in.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2025-31480?


## How do I fix CVE-2025-31480?

No fix has been published for CVE-2025-31480 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-31480 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-31480 and fix it if it is affected.

What it is: CVE-2025-31480 is a critical vulnerability in aiven-extras, published on 4 Apr 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-31480 in the wild and no public exploit code.

Affected product: aiven-extras. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2025-31480/ (Markdown: https://insights.sbomify.com/CVE-2025-31480/index.md)
```

## Sources

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

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