Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44477 critical CVSS 9.9

Vulnerability in github.com/cloudnative-pg/cloudnative-pg (CVE-2026-44477)

Summary

Vulnerability in github.com/cloudnative-pg/cloudnative-pg (CVE-2026-44477). Successful exploitation can lead to full system takeover. Exploitable via postgres. Mitigation: upgrade to 1.29.1 or later.

Original description

The description as published by the source.

Impact

The CloudNativePG metrics exporter opens its PostgreSQL connection as the postgres superuser via the pod-local Unix socket, then demotes the session with SET ROLE pg_monitor. SET ROLE changes only current_user; session_user remains postgres. That residual superuser identity is the foothold for the rest of the chain.

Any SQL expression evaluated inside the scrape session can invoke RESET ROLE to recover real superuser privileges, then use COPY ... TO PROGRAM to spawn an OS-level subprocess as the postgres user inside the primary pod. The READ ONLY transaction flag does not block this; it gates writes to database state, not external processes.

Two exploitation paths follow from this root cause.

Path 1: custom metric queries with unqualified identifiers (all supported releases)

A database user who owns a schema on the search_path of any scraped database can plant a shadow object whose name matches an unqualified identifier in a custom metric query. When the exporter next evaluates that query, the shadow expression executes inside the session_user = postgres scrape session, giving the attacker PostgreSQL superuser privileges and OS command execution inside the primary pod within one scrape interval (≤30 s). Exploitability requires a custom metric query that contains an unqualified relation or function reference.

Although search_path shadowing of unqualified identifiers is the most direct case, the underlying bug is that any expressi…

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-44477 has been found in github.com/cloudnative-pg/cloudnative-pg.
Attackers can target a specific entry point like postgres over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade github.com/cloudnative-pg/cloudnative-pg to 1.29.1 or later.
If unsure, ask your IT team or search "github.com/cloudnative-pg/cloudnative-pg CVE-2026-44477" on the vendor's site.

CVE-2026-44477 (github.com/cloudnative-pg/cloudnative-pg) — CWE-250 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: postgres / current_user / session_user / search_path
Patched: 1.29.1 — 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-250) exists in github.com/cloudnative-pg/cloudnative-pg. Attackers reach the vulnerable code path via postgres.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/cloudnative-pg/cloudnative-pg. Attack surface: postgres / current_user / session_user / search_path.

🔥 Severity

Severity: Critical (CVSS 9.9/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.29.1.

🛡️ 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 'github.com/cloudnative-pg/cloudnative-pg' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/cloudnative-pg/cloudnative-pg' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/cloudnative-pg/cloudnative-pg を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/cloudnative-pg/cloudnative-pg to 1.29.1

    ステージング環境で 1.29.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/cloudnative-pg/cloudnative-pg
[{"type":"SEMVER","events":[{"introduced":"1.29.0"},{"fixed":"1.29.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details