MAVEN · MAY 2026 · EARLY WARNING

Apache Polaris Improper Input Validation Issue: Early Warning

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.
Severity
HIGH
Affected component
org.apache.polaris:polaris-runtime-service (maven)
Affected versions
< 1.4.1 or >= 1.0.0-incubating, <= 1.0.0-incubating or >= 1.0.1-incubating, <= 1.0.1-incubating or >= 1.1.0-incubating, <= 1.1.0-incubating or >= 1.2.0-incubating, <= 1.2.0-incubating or >= 1.3.0-incubating, <= 1.3.0-incubating or >= 1.4.0, <= 1.4.0 or < 1.4.1 or >= 1.0.0-incubating, <= 1.0.0-incubating or >= 1.0.1-incubating, <= 1.0.1-incubating or >= 1.1.0-incubating, <= 1.1.0-incubating or >= 1.2.0-incubating, <= 1.2.0-incubating or >= 1.3.0-incubating, <= 1.3.0-incubating or >= 1.4.0, <= 1.4.0
Patched version
Not yet available
GHSA-W76P-3CGP-QFCM

An improper input validation issue has been reported in Apache Polaris, potentially allowing unauthorized access to storage areas. Users of affected versions should assess their exposure and take recommended actions.

What happened

Apache Polaris is reportedly affected by an improper input validation issue, tracked as GHSA-W76P-3CGP-QFCM and CVE-2026-42812. This vulnerability allows bypassing storage location validation, which could lead to unauthorized access to storage areas. The issue affects versions of org.apache.polaris:polaris-runtime-service less than 1.4.1 or within specific incubating version ranges. The vulnerability has not been exploited in the wild, and no supply-chain attack has been reported. Users should consult the primary sources for detailed version information and updates.

The vulnerability was first flagged on May 4, 2026. It is under investigation, and a fixed version is expected to be released. In the meantime, users are advised to review their storage location configurations and stay updated with the latest information from the primary sources.

What to do about it

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If org.apache.polaris:polaris-runtime-service is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using org.apache.polaris:polaris-runtime-service in versions less than 1.4.1 or within the specified incubating version ranges.

What should I do right now?

Monitor the primary sources for updates on the fixed version and review your storage location configurations.

When will a fix be available?

A fixed version is under development. Consult the primary sources for updates on its release.

How can I secure my storage locations in the meantime?

Review and secure your storage location configurations to mitigate potential risks.

Sources

Join the 0Day waitlist →

← Back to all threats