Quick answers
- Is CVE-2026-42811 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-42811 being exploited in the wild.
- How severe is CVE-2026-42811?
- Critical severity, with a CVSS score of 9.9, published 4 May 2026.
- Which products and versions are affected?
- org.apache.polaris:polaris-core (Maven) ECOSYSTEM:introduced=0,fixed=1.4.1.
- Is there a fix for CVE-2026-42811?
- Yes. org.apache.polaris:polaris-core (Maven): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-42811 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-42811?
- Check whether you run Apache Polaris or org.apache.polaris:polaris-core (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.polaris:polaris-core (Maven): upgrade to 1.4.1 or later
# set org.apache.polaris:polaris-core to 1.4.1 in your pom.xml or build.gradle
Technical details
Apache Polaris is vulnerable to an expression language injection in its Google Cloud Storage (GCS) credential delegation mechanism. The service constructs Common Expression Language (CEL) strings for Credential Access Boundaries (CAB) by concatenating bucket names and table paths without proper escaping. An attacker with permissions to create or interact with namespaces/tables can use single quotes and URI-safe CEL fragments to break out of the intended string literal. This 'collapses' the path restriction, granting the attacker delegated credentials with full list, read, and write access to the entire GCS bucket. The vulnerability is confirmed in version 1.4.0 and addressed in 1.4.1.
Affected products
- Apache Polaris before 1.4.1
Identifiers
- CVE-2026-42811
- GHSA-fc3h-c6h7-r83j
Timeline
- 2026-05-02: disclosed: Initial disclosure on oss-security mailing list
- 2026-05-04: advisory: NVD publication date
- 2026-05-04: patched: Fix available in version 1.4.1