CVE-2025-64400VulnerabilityPublished 18 Dec 2025

CVE-2025-64400: com.palantir.controlpanel:control-panel · The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affects com.palantir.controlpanel:control-panelSource CVE Database V5

Not known to be exploited · CVSS 4.1 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.1Medium

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

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:N/A:N

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

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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Dec 2025
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 2026-10-25.

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

Affected software

Product	Affected	Fixed in
Mavencom.palantir/control-panel`pkg:maven/com.palantir/control-panel`Other threats	Affected *	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 implement the following specific mitigations: 1) Audit and restrict enrollment-level user directory edit permissions to only trusted administrators with a clear need, minimizing the number of accounts that can exploit this flaw. 2) Implement compensating controls such as monitoring and alerting on user creation events, especially those that add users to organizations outside the requester's normal scope. 3) Apply network segmentation and access controls to limit which systems and users can access the Control Panel API. 4) Engage with Palantir to obtain and deploy patches or updates addressing this vulnerability as they become available. 5) Conduct regular reviews of user provisioning workflows and permissions to detect anomalies. 6) Consider implementing additional application-layer authorization checks or custom policies that enforce organizational boundaries until an official fix is applied. 7) Train administrators on the risks of excessive permissions and the importance of adhering to the principle of least privilege. These measures go beyond generic advice by focusing on permission hygiene, monitoring, and compensating controls tailored to the specific nature of this vulnerability.

Description

CVE-2025-64400 is a medium-severity vulnerability in Palantir's Control Panel product that allows unauthorized actors to pre-register users into organizations without proper access checks. The flaw arises because the API only verifies that the requester has edit permissions on the enrollment-level user directory but fails to confirm that the requester belongs to or has access to the specific organization they are adding users to. This can lead to unauthorized user creation across organizational boundaries, potentially exposing sensitive enrollment data. Exploitation requires network access and privileges to edit the enrollment-level directory but does not require user interaction. While the impact on confidentiality is limited and there is no integrity or availability impact, the vulnerability could facilitate unauthorized access or lateral movement within affected environments. No known exploits are currently in the wild. European organizations using Palantir Control Panel should review and restrict enrollment-level edit permissions and monitor user creation activities. Countries with significant Palantir deployments, such as the UK, Germany, France, and the Netherlands, are most likely to be affected.

Impact

For European organizations using Palantir Control Panel, this vulnerability poses a risk of unauthorized user creation across organizational boundaries, which can lead to unauthorized access to sensitive data or systems. While the direct confidentiality impact is limited, the ability to create users in unauthorized organizations could facilitate lateral movement, privilege escalation, or insider threat scenarios. This is particularly concerning for organizations with strict data segregation requirements or those operating in regulated sectors such as finance, healthcare, or government. The vulnerability does not affect system availability or data integrity directly but could undermine trust in access controls and complicate compliance with data protection regulations like GDPR. The medium severity rating suggests that while the risk is not critical, it warrants timely remediation to prevent potential misuse. Organizations with complex multi-organization deployments or shared enrollment directories are at higher risk. The absence of known exploits reduces immediate threat but does not eliminate the need for proactive mitigation.

Summary

CVE-2025-64400 is a vulnerability identified in Palantir's Control Panel product, specifically within its API responsible for pre-registering users into enrollments and organizations before their first login. The API enforces a permission check to ensure that the requesting account has 'edit' rights on the enrollment-level user directory. However, it lacks a critical authorization check to verify that the enrollment editor is authorized to add users to the specific organization in question. This missing check allows an actor with enrollment-level edit privileges to create users in organizations they do not belong to or have access to, effectively bypassing organizational boundaries. The vulnerability does not require user interaction and can be exploited remotely over the network by an authenticated user with elevated privileges. The CVSS 3.1 score of 4.1 reflects a medium severity, primarily due to the limited confidentiality impact and absence of integrity or availability impacts. The vulnerability's scope is confined to the Palantir Control Panel product, affecting all versions as indicated. Although no public exploits have been reported, the flaw could be leveraged for unauthorized user provisioning, potentially enabling privilege escalation or lateral movement within an enterprise environment. The vulnerability highlights a common authorization design flaw where hierarchical permission checks do not sufficiently enforce organizational boundaries, underscoring the need for granular access controls in multi-tenant or multi-organization systems.

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 25 Dec 2025, 20:02 UTC

Technical details

References

Community reviews

Related threats