← Back
CVE-2026-54291
medium
CVSS 5.9
Vulnerability in org.postgresql:postgresql (CVE-2026-54291)
Summary
vulnerability in org.postgresql:postgresql (CVE-2026-54291). Data can be tampered with by attackers. Exploitable via ``Ed25519``. Mitigation: upgrade to `42.7.12` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54291** has been found in org.postgresql:postgresql.
Attackers can target a specific entry point like ``Ed25519`` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade org.postgresql:postgresql to **42.7.12** or later.
If unsure, ask your IT team or search "org.postgresql:postgresql CVE-2026-54291" on the vendor's site.
CVE-2026-54291 (org.postgresql:postgresql) — CWE-636 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `Ed25519` / `Ed448` / `ScramAuthenticator` / `prefer`
Patched: `42.7.12` — 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** (CWE-636) exists in org.postgresql:postgresql. Attackers reach the vulnerable code path via ``Ed25519`` without authentication.
📍 Affected scope
org.postgresql:postgresql — . Attack surface: `Ed25519` / `Ed448` / `ScramAuthenticator` / `prefer`.
🔥 Severity
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers
🔧 How to fix
Update to **42.7.12**.
🛡️ 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 'org.postgresql:postgresql' .` 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 'org.postgresql:postgresql' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `org.postgresql:postgresql` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade org.postgresql:postgresql to 42.7.12ステージング環境で 42.7.12 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
maven
org.postgresql:postgresql
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"42.7.12"}]}]
References
- web https://github.com/ongres/scram/releases/tag/3.3
- web https://github.com/pgjdbc/pgjdbc/commit/77df98e4e66c12936ded3478a0954f6f580bad99
- web https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-j92g-9f8w-j867
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54291
- web https://github.com/advisories/GHSA-j92g-9f8w-j867