← Back
DEBIAN-CVE-2025-12819
Vulnerability in pgbouncer (DEBIAN-CVE-2025-12819)
Summary
vulnerability in pgbouncer (DEBIAN-CVE-2025-12819). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `1.15.0-1+deb11u2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **DEBIAN-CVE-2025-12819** has been found in pgbouncer.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade pgbouncer to **1.15.0-1+deb11u2** or later.
If unsure, ask your IT team or search "pgbouncer DEBIAN-CVE-2025-12819" on the vendor's site.
DEBIAN-CVE-2025-12819 (pgbouncer) —
Patched: `1.15.0-1+deb11u2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (unclassified) exists in pgbouncer.
📍 Affected scope
pgbouncer — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.15.0-1+deb11u2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pgbouncer' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pgbouncer' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pgbouncer` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pgbouncer to 1.15.0-1+deb11u2ステージング環境で 1.15.0-1+deb11u2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Debian:11
pgbouncer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15.0-1+deb11u2"}]}]
Debian:12
pgbouncer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.0-1+deb12u1"}]}]
Debian:13
pgbouncer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.24.1-1+deb13u1"}]}]
Debian:14
pgbouncer
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.25.1-1"}]}]