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

Vulnerability in org.apache.polaris:polaris-runtime-service (CVE-2026-42812)

Summary

Vulnerability in org.apache.polaris:polaris-runtime-service (CVE-2026-42812). Successful exploitation can lead to full system takeover. Exploitable via write.metadata.path. Mitigation: upgrade to 1.4.1 or later.

Original description

The description as published by the source.

In Apache Iceberg, the table's metadata files are control files: they tell readers which data files belong to the table and which table version to read.

write.metadata.path is an optional table property that tells Polaris where to write those metadata files. For a table already registered in a Polaris-managed catalog, changing only that property through an ALTER TABLE-style settings change (not a row-level INSERT, SELECT, UPDATE, or DELETE) bypasses the commit-time branch that is supposed to revalidate storage locations.

The full persisted / credential-vending variant requires the affected catalog to have polaris.config.allow.unstructured.table.location=true, with allowedLocations broad enough to include the attacker-chosen target.

allowedLocations is the admin-configured allowlist of storage paths that the catalog is allowed to use. Public project materials suggest that this flag is a real supported compatibility / layout mode, not just a contrived lab-only prerequisite.

In that configuration, a user who can change table settings can cause Apache Polaris itself to write new table metadata to an attacker-chosen reachable storage location before the intended location-validation branch runs.

If the later concrete-path validation also accepts that location, Polaris persists the resulting metadata path into stored table state. Later table-load and credential APIs can then return temporary cloud-storage credentials for the same location without revalidating…

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-42812 has been found in org.apache.polaris:polaris-runtime-service.
Attackers can target a specific entry point like write.metadata.path over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 9.9/10.
What to do: upgrade org.apache.polaris:polaris-runtime-service to 1.4.1 or later.
If unsure, ask your IT team or search "org.apache.polaris:polaris-runtime-service CVE-2026-42812" on the vendor's site.

CVE-2026-42812 (org.apache.polaris:polaris-runtime-service) — CWE-20 / CVSS v3 9.9
Attack vector: remote (network-reachable) / no user interaction
Attack surface: write.metadata.path / INSERT / SELECT / UPDATE
Patched: 1.4.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-20) exists in org.apache.polaris:polaris-runtime-service. Attackers reach the vulnerable code path via write.metadata.path.

📍 Affected scope

Check the vendor advisory for the affected versions of org.apache.polaris:polaris-runtime-service. Attack surface: write.metadata.path / INSERT / SELECT / UPDATE.

🔥 Severity

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

🔧 How to fix

Update to 1.4.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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで org.apache.polaris:polaris-runtime-service を使っているサービスとバージョンを洗い出す。

  2. 2
    Apply patch patch 
    Upgrade org.apache.polaris:polaris-runtime-service to 1.4.1

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

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

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

Affected packages

maven org.apache.polaris:polaris-runtime-service
[{"type":"ECOSYSTEM","events":[{"introduced":"0.9.0"},{"fixed":"1.4.1"}]}]

References

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