{"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-42810 in the wild and no public exploit code.","fix":"Upgrade org.apache.polaris:polaris-core to 1.4.1 or later.","what":"CVE-2026-42810 is a critical 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-42810 and fix it if it is affected.\n\nWhat it is: CVE-2026-42810 is a critical 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-42810 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-42810/ (Markdown: https://insights.sbomify.com/CVE-2026-42810/index.md)","id":"CVE-2026-42810","markdown":"https://insights.sbomify.com/CVE-2026-42810/index.md","name":"CVE-2026-42810","record":{"aliases":["GHSA-vxgg-mqx2-3w59"],"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 craft wildcard table names to obtain S3 credentials granting unauthorized read and write access to other tables' data.","user_interaction":"not_required","vuln_class":"other"},"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-20","name":"Improper Input Validation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"Apache Polaris accepts literal `*` characters in namespace and table names. When it\nlater builds temporary S3 access policies for delegated table access, those\nsame characters appear to be reused unescaped in S3 IAM resource patterns\nand\n`s3:prefix` conditions.\n\nIn S3 IAM policy matching, `*` is treated as a wildcard rather than as\nordinary text. That means temporary credentials issued for one crafted table\ncan match the storage path of a different table.\n\nIn private testing against Polaris 1.4.0 using Polaris' AWS S3 temporary-\ncredential path on both MinIO and real AWS S3, credentials returned for\ncrafted tables such as `f*.t1`, `f*.*`, `*.*`, and `foo.*` could reach other\ntables' S3 locations.\n\nThe confirmed behavior includes:\n\n- reading another table's metadata control file ([Iceberg metadata JSON]);\n\n- listing another table's exact S3 table prefix ([table prefix]);\n\n- and, when write delegation was returned for the crafted table, creating\nand\ndeleting an object under another table's exact S3 table prefix.\n\nA control case using ordinary different names did not allow the same\ncross-table access.\n\nA least-privilege AWS S3 variant was also confirmed in which the attacker\nprincipal had no Polaris permissions on the victim table and only the\nminimal permissions required to create and use a crafted wildcard table\n(namespace-scoped `TABLE_CREATE` and `TABLE_WRITE_DATA` on `*`). In that\nsetup, direct Polaris access to `foo.t1` remained forbidden, but the\nattacker\ncould still create and load `*.*`, receive delegated S3 credentials, and use\nthose credentials to list, read, create, and delete objects under `foo.t1`.\n\nIn Iceberg, the metadata JSON file is a control file: it tells readers which\ndata files belong to the table, which snapshots exist, and which table\nversion\nto read. So unauthorized access to it is already a meaningful\nconfidentiality\nproblem. The confirmed write-capable variant means the issue is not limited\nto\ndisclosure.","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: could broaden vended S3 credentials through wildcard-bearing namespace or table names","id":"CVE-2026-42810","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Apache Polaris has an Improper Input Validation issue","id":"CVE-2026-42811"},"packages":[{"ecosystem":"Maven","fixed":["1.4.1"],"introduced":["0"],"last_affected":[],"package":"org.apache.polaris:polaris-core","purl":null,"source":"GHSA-vxgg-mqx2-3w59"},{"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-vxgg-mqx2-3w59"}],"prev":{"headline":"Apache Polaris: staged table creation could vend storage credentials for unvalidated locations","id":"CVE-2026-42809"},"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 has an Improper Input Validation issue","id":"CVE-2026-42811","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 craft wildcard table names to obtain S3 credentials granting unauthorized read and write access to other tables' data.","url":"https://insights.sbomify.com/CVE-2026-42810/"}