{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-62487 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-62487 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-62487 is a low-severity missing authorization vulnerability in com.palantir.acme:dossier-app, published on 9 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-62487 and fix it if it is affected.\n\nWhat it is: CVE-2025-62487 is a low-severity missing authorization vulnerability in com.palantir.acme:dossier-app, published on 9 Jan 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-62487 in the wild and no public exploit code.\n\nAffected product: com.palantir.acme:dossier-app. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2025-62487/ (Markdown: https://insights.sbomify.com/CVE-2025-62487/index.md)","id":"CVE-2025-62487","markdown":"https://insights.sbomify.com/CVE-2025-62487/index.md","name":"CVE-2025-62487","record":{"aliases":["GHSA-4wq3-r6vg-34q5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Palantir Dossier app","requires_auth":"low_privilege","summary":"Attackers can access uploaded files without proper security markings in Palantir Dossier deployments lacking CBAC configuration.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Palantir","cpe":[],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N/CR:H/IR:H/AR:H","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"On October 1, 2025, Palantir discovered that images uploaded through the Dossier front-end app were not being marked correctly with the proper security levels. The regression was traced back to a change in May 2025, which was meant to allow file uploads to be shared among different artifacts (e.g. other dossiers and presentations).\n\nOn deployments configured with CBAC, the front-end would present a security picker dialog to set the security level on the uploads, thereby mitigating the issue.\n\nOn deployments without a CBAC configuration, no security picker dialog appears, leading to a security level of CUSTOM with no markings or datasets selected. The resulting markings and groups for the file uploads thus will be only those added by the default authorization rules defined in the Auth Chooser configuration. On most environments, it is expected that the default authorization rules only add the Everyone group.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in com.palantir.acme:dossier-app","id":"CVE-2025-62487","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Use-after-free in js_print_object in QuickJS","id":"CVE-2025-62490"},"packages":[],"prev":{"headline":"Zoom Workplace Clients - Inefficient Regular Expression Complexity","id":"CVE-2025-62484"},"products":["com.palantir.acme:dossier-app","com.palantir.acme:gotham-default-apps-bundle","com.palantir.acme:stencil-app-bundle"],"published":"2026-01-09","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"partial"},"state":"PUBLISHED","updated":"2026-01-14","vendors":["Palantir"]},"summary":"Attackers can access uploaded files without proper security markings in Palantir Dossier deployments lacking CBAC configuration.","url":"https://insights.sbomify.com/CVE-2025-62487/"}