{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.polaris:polaris-runtime-service. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-42812 in the wild and no public exploit code.","fix":"Upgrade org.apache.polaris:polaris-runtime-service to 1.4.1 or later.","what":"CVE-2026-42812 is a critical missing authorization 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-42812 and fix it if it is affected.\n\nWhat it is: CVE-2026-42812 is a critical missing authorization 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-42812 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.polaris:polaris-runtime-service (Maven): affected from 0.9.0; fixed in 1.4.1\n- org.apache.polaris:polaris-runtime-service (Maven): affected from 0.9.0; 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-42812/ (Markdown: https://insights.sbomify.com/CVE-2026-42812/index.md)","id":"CVE-2026-42812","markdown":"https://insights.sbomify.com/CVE-2026-42812/index.md","name":"CVE-2026-42812","record":{"aliases":["GHSA-w76p-3cgp-qfcm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Apache Polaris catalog","requires_auth":"low_privilege","summary":"Attackers can bypass storage location validation to write metadata to arbitrary locations, potentially exposing or corrupting data via credential vending.","user_interaction":"not_required","vuln_class":"missing_authorization"},"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-863","name":"Incorrect Authorization"},{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"},{"id":"CWE-284","name":"Improper Access Control"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"In Apache Iceberg, the table's metadata files are control files: they tell readers\nwhich data files belong to the table and which table version to read.\n\n`write.metadata.path` is an optional table property that tells Polaris\nwhere to\nwrite those metadata files. \nFor a table already registered in a\nPolaris-managed\ncatalog, changing only that property through an `ALTER TABLE`-style settings\nchange (not a row-level `INSERT`, `SELECT`, `UPDATE`, or `DELETE`) bypasses\nthe commit-time branch that is supposed to revalidate storage locations.\n\nThe full persisted / credential-vending variant requires the affected\ncatalog\nto have `polaris.config.allow.unstructured.table.location=true`, with\n`allowedLocations` broad enough to include the attacker-chosen target.\n\n`allowedLocations` is the admin-configured allowlist of storage paths that\nthe\ncatalog is allowed to use. Public project materials suggest that this flag\nis a\nreal supported compatibility / layout mode, not just a contrived lab-only\nprerequisite.\n\nIn that configuration, a user who can change table settings can cause Apache Polaris\nitself to write new table metadata to an attacker-chosen reachable storage\nlocation before the intended location-validation branch runs.\n\nIf the later concrete-path validation also accepts that location, Polaris\npersists the resulting metadata path into stored table state. Later\ntable-load\nand credential APIs can then return temporary cloud-storage credentials for\nthe\nsame location without revalidating it. In plain terms, Polaris can later\nhand\nout temporary storage access for the same attacker-chosen area.\n\nThat attacker-chosen area does not need to be limited to the poisoned\ntable's\nown files. If it is a broader storage prefix, another table's prefix, or,\ndepending on configuration or provider behavior, even a bucket/container\nroot,\nthe resulting disclosure or corruption scope can extend to any data and\nmetadata Polaris can reach there.\n\nThe practical consequences are therefore similar to the staged-create\ncredential-vending issue already discussed: data and metadata reachable in\nthat\nstorage scope can be exposed and, if write-capable credentials are later\nissued, modified, corrupted, or removed. Even before that later credential\nstep, Polaris itself performs the metadata write to the unchecked location.\n\nSo the core issue is not only later credential vending. \n\nThe primary defect\nis\nthat Polaris skips its intended location checks before performing a\nsecurity-\nsensitive metadata write when only `write.metadata.path` changes.\n\nWhen `polaris.config.allow.unstructured.table.location=false`, current code\nreview suggests the later `updateTableLike(...)` validation usually rejects\nout-of-tree metadata locations before the unsafe path is persisted. That may\nreduce the persisted / credential-vending variant, but it does not prevent\nthe\nunderlying defect: Polaris still skips the intended pre-write location check\nwhen only `write.metadata.path` changes.","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: No protection on `write.metadata.path`","id":"CVE-2026-42812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Azure Local Disconnected Operations (ALDO) Elevation of Privilege Vulnerability","id":"CVE-2026-42822"},"packages":[{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0.9.0"],"last_affected":[],"package":"org.apache.polaris:polaris-runtime-service","purl":null,"source":"GHSA-w76p-3cgp-qfcm"},{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0.9.0"],"last_affected":[],"package":"org.apache.polaris:polaris-runtime-service","purl":"pkg:maven/org.apache.polaris/polaris-runtime-service","source":"GHSA-w76p-3cgp-qfcm"}],"prev":{"headline":"Apache Polaris has an Improper Input Validation issue","id":"CVE-2026-42811"},"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 has an Improper Input Validation issue","id":"CVE-2026-42811","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 bypass storage location validation to write metadata to arbitrary locations, potentially exposing or corrupting data via credential vending.","url":"https://insights.sbomify.com/CVE-2026-42812/"}