Skip to content
Fencer Intel
low 3.5

CVE-2025-62487 json

Under certain configurations, file artifacts uploaded to the Dossier and Slides apps did not inherit security markings of their parent artifact. This lack of security markings could lead to unintended access to the uploaded files.

published 10mo ago modified 4mo ago also EUVD-2025-206271

cvss
3.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 12%
public exploits
0
none known

Summary

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).

On 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.

On 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.

Patch / fix

  • Palantir com.palantir.acme:gotham-default-apps-bundle 100.30250507.88, 100.30250709.54, 100.30250808.87, 100.30250906.52, 100.30250907.11, 100.30250908.1, 100.30251001.1, 100.30251002.0
  • Palantir com.palantir.acme:stencil-app-bundle 100.30250507.88, 100.30250709.54, 100.30250808.87, 100.30250906.52, 100.30250907.11, 100.30250908.1, 100.30251001.1, 100.30251002.0
  • Palantir com.palantir.acme:dossier-app 100.30250507.88, 100.30250709.54, 100.30250808.87, 100.30250906.52, 100.30250907.11, 100.30250908.1, 100.30251001.1, 100.30251002.0

Is CVE-2025-62487 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
10mo ago

Exploit prediction

0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 3.5 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
CNA 3.1 3.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N

Affected products

  • Palantir com.palantir.acme:gotham-default-apps-bundle
  • Palantir com.palantir.acme:stencil-app-bundle
  • Palantir com.palantir.acme:dossier-app

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.