{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.polaris:polaris-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42811 in the wild and no public exploit code.","fix":"Upgrade org.apache.polaris:polaris-core to 1.4.1 or later.","what":"CVE-2026-42811 is a critical code injection vulnerability in Apache Polaris, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42811 and fix it if it is affected.\n\nWhat it is: CVE-2026-42811 is a critical code injection vulnerability in Apache Polaris, published on 4 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-42811 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.polaris:polaris-core (Maven): affected all versions; fixed in 1.4.1\n- org.apache.polaris:polaris-core (Maven): affected all versions; fixed in 1.4.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42811/ (Markdown: https://insights.sbomify.com/CVE-2026-42811/index.md)","id":"CVE-2026-42811","markdown":"https://insights.sbomify.com/CVE-2026-42811/index.md","name":"CVE-2026-42811","record":{"aliases":["GHSA-fc3h-c6h7-r83j"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Polaris","requires_auth":"low_privilege","summary":"Attackers can inject CEL code via crafted identifiers to broaden GCS credentials, allowing unauthorized read and write access to other tables or bucket contents.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"polaris","vendor":"apache"}],"cvss":{"score":9.4,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-917","name":"Improper Neutralization of Special Elements used in an Expression Language Statement"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"In plain terms, Apache Polaris is supposed to issue short-lived GCS credentials\nthat\nonly work for one table's files, but a crafted namespace or table name can\ncause those credentials to work across the configured bucket instead.\n\nApache Polaris builds Google Cloud Storage downscoped credentials by creating a\nCredential Access Boundary (CAB) with CEL conditions that are intended to\nrestrict access to the requested table's storage path.\n\nThe relevant CEL string is built from the bucket name and the table path.\nThat\ntable path is derived from namespace and table identifiers. In current code,\nthat path appears to be inserted into the CEL expression without escaping.\n\nAs a result, a namespace or table identifier containing a single quote and\nother URI-safe CEL fragments can break out of the intended quoted string and\nchange the meaning of the CEL condition.\n\nIn private testing against Polaris 1.4.0 on real Google Cloud Storage, it was confirmed that Polaris accepted a crafted identifier and returned delegated\nGCS\ncredentials whose CEL path restriction had effectively collapsed.\n\nThose delegated credentials could then:\n\n- list another table's object prefix;\n\n- read another table's metadata control file (Iceberg metadata JSON);\n\n- create and delete an object under another table's object prefix;\n\n- and also list, read, create, and delete objects under an unrelated\nexternal\nprefix in the same bucket that was not part of any table path.\n\nThat last point is important. The issue is not limited to \"another table\".\nIn\nthe confirmed setup, once Apache Polaris returned credentials for the crafted\ntable,\nthe path restriction inside the configured bucket was effectively gone.\n\nThe practical effect is that temporary credentials for one crafted table\ncan be\nbroader than the table Polaris was asked to authorize, and can become\neffectively bucket-wide within the configured bucket.\n\nThe current GCS testing used a Polaris principal with broad catalog\nprivileges for setup. A separate least-privilege Polaris RBAC variant\nhas not yet been tested on GCS. However, the storage-credential\nbroadening behavior itself has been confirmed on GCS.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Polaris has an Improper Input Validation issue","id":"CVE-2026-42811","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Apache Polaris: No protection on `write.metadata.path`","id":"CVE-2026-42812"},"packages":[{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.polaris:polaris-core","purl":null,"source":"GHSA-fc3h-c6h7-r83j"},{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.polaris:polaris-core","purl":"pkg:maven/org.apache.polaris/polaris-core","source":"GHSA-fc3h-c6h7-r83j"}],"prev":{"headline":"Apache Polaris: could broaden vended S3 credentials through wildcard-bearing namespace or table names","id":"CVE-2026-42810"},"products":["Apache Polaris"],"published":"2026-05-04","related":[{"cvss_score":9.4,"headline":"Apache Polaris: staged table creation could vend storage credentials for unvalidated locations","id":"CVE-2026-42809","kev_date_added":null,"published":"2026-05-04"},{"cvss_score":9.4,"headline":"Apache Polaris: could broaden vended S3 credentials through wildcard-bearing namespace or table names","id":"CVE-2026-42810","kev_date_added":null,"published":"2026-05-04"},{"cvss_score":9.4,"headline":"Apache Polaris: No protection on `write.metadata.path`","id":"CVE-2026-42812","kev_date_added":null,"published":"2026-05-04"},{"cvss_score":5.3,"headline":"Apache Polaris: register endpoint reads attacker-controlled storage location before allowed-locations validation","id":"CVE-2026-64640","kev_date_added":null,"published":"2026-08-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-04","vendors":["Apache Software Foundation"]},"summary":"Attackers can inject CEL code via crafted identifiers to broaden GCS credentials, allowing unauthorized read and write access to other tables or bucket contents.","url":"https://insights.sbomify.com/CVE-2026-42811/"}