VulnerabilityPublished 9 Jan 2026Updated 14 Jan 2026

CVE-2025-62487: com.palantir.acme:gotham-default-apps-bundle · The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions.

Affects com.palantir.acme:gotham-default-apps-bundleSource CVE Database V5

Not known to be exploited · CVSS 3.5 Low : upgrade to 100.30251002.0 when convenient.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score

3.5Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 100.30251002.0

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Environmental metrics

Confidentiality Requirement: High
Integrity Requirement: High
Availability Requirement: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Confidentiality Requirement: High: Loss of Confidentiality is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
Integrity Requirement: High: Loss of Integrity is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).
Availability Requirement: High: Loss of Availability is likely to have a catastrophic adverse effect on the organization or individuals associated with the organization (e.g., employees, customers).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade com.palantir.acme:gotham-default-apps-bundle and com.palantir.acme:stencil-app-bundle and com.palantir.acme:dossier-app to 100.30251002.0.

Affected software

Product	Affected	Fixed in
Palantircom.palantir.acme:gotham-default-apps-bundle	Affected >=100.30250502.0 <100.30251002.0	Fixed in 100.30251002.0
Palantircom.palantir.acme:stencil-app-bundle	Affected >=100.30250502.0 <100.30251002.0	Fixed in 100.30251002.0
Palantircom.palantir.acme:dossier-app	Affected >=100.30250502.0 <100.30251002.0	Fixed in 100.30251002.0
Mavencom.palantir.acme/gotham-default-apps-bundle`pkg:maven/com.palantir.acme/gotham-default-apps-bundle`Other threats	Affected =100.30250502.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify whether their Palantir Gotham deployments use CBAC configurations. If not configured, they should enable CBAC to ensure the security picker dialog appears and correct security levels are assigned to uploads. Review and tighten the default authorization rules in the Auth Chooser configuration to avoid overly permissive access such as granting Everyone group rights by default. Implement strict role-based access controls and audit logs to monitor file uploads and access patterns. Conduct thorough testing after applying any patches or configuration changes to confirm that security markings are correctly applied. Additionally, restrict upload privileges to trusted users and consider network segmentation to limit exposure of sensitive data. Engage with Palantir support for any available patches or updates addressing this regression. Finally, provide user training to raise awareness about the importance of correctly setting security levels on uploaded content.

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

Impact

For European organizations using Palantir Gotham Default Apps Bundle, this vulnerability could lead to unauthorized disclosure of sensitive or confidential information contained in uploaded images. Since the default authorization rules often grant access to the Everyone group, files intended to be restricted could be exposed broadly within the organization or even to external users if network segmentation is weak. This exposure risks violating data protection regulations such as GDPR, potentially resulting in legal and reputational damage. The impact is primarily on confidentiality, with no direct effect on data integrity or system availability. Organizations relying on CBAC configurations are less affected, but those without it or with misconfigured authorization policies face increased risk. The requirement for some privileges and user interaction limits the threat to insider actors or users with limited access, rather than external unauthenticated attackers. However, given Palantir's use in critical sectors including government, defense, and intelligence across Europe, even limited unauthorized access could have serious operational and strategic consequences.

References

palantir.safebase.us (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Jan 2026, 07:35 UTC

Technical details

References

Community reviews

Related threats