# CVE-2025-46801: Auth bypass in Pgpool-II

> Attackers can bypass authentication to log in as arbitrary users, enabling data theft, modification, or database denial of service.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2025-46801, DLA-4334-1, GHSA-9559-hpf7-pqv3, UBUNTU-CVE-2025-46801

## What is CVE-2025-46801?

CVE-2025-46801 is a critical authentication bypass vulnerability in Pgpool-II, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pgpool-II provided by PgPool Global Development Group contains an authentication bypass by primary weakness vulnerability. if the vulnerability is exploited, an attacker may be able to log in to the system as an arbitrary user, allowing them to read or tamper with data in the database, and/or disable the database.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

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


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

Apply the vendor's patch.

## Is CVE-2025-46801 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46801 is a critical authentication bypass vulnerability in Pgpool-II, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-46801 in the wild and no public exploit code.

Affected product: Pgpool-II. 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-46801/ (Markdown: https://insights.sbomify.com/CVE-2025-46801/index.md)
```

## Sources

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

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