VulnerabilityPublished 10 Jul 2025

CVE-2025-53709: com.palantir.secupload:secure-upload · The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.

Affects com.palantir.secupload:secure-uploadSource CVE Database V5

Not known to be exploited · CVSS 5.4 Medium : upgrade to 0.815.0 when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

5.4Medium

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
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: 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: None: The vulnerable system can be exploited without any interaction from any user.
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: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on 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 10 Jul 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 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.secupload/secure-upload to 0.815.0.

Affected software

Product	Affected	Fixed in
Mavencom.palantir.secupload/secure-upload`pkg:maven/com.palantir.secupload/secure-upload`Other threats	Affected <0.815.0	Fixed in 0.815.0

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 verify that their Palantir secure-upload service is updated to version 0.815.0 or later, ensuring the patch addressing CVE-2025-53709 is applied. For self-managed instances, immediate manual patching is critical. Organizations should audit privileged user roles and permissions within the secure-upload environment to enforce the principle of least privilege, limiting the ability to select email templates or redirect submission channels outside their enrollment scope. Implement monitoring and alerting on unusual activities such as channel redirections or access attempts to unauthorized templates. Restrict access to domain validation and resource enumeration endpoints by applying additional authentication or network-level controls (e.g., IP whitelisting, VPN access) to prevent unauthenticated enumeration. Conduct regular security assessments and penetration tests focused on authorization controls within the secure-upload service. Additionally, review and enhance logging to capture detailed access and modification events for forensic analysis. Finally, educate privileged users on secure usage policies to reduce insider risk and ensure compliance with data handling standards.

Description

Secure-upload is a data submission service that validates single-use tokens when accepting submissions to channels. The service only installed on a small number of environments. Under specific circumstances, privileged users of secure-upload could have selected email templates not necessarily created for their enrollment when sending data upload requests. Authenticated and privileged users of one enrollment could have abused an endpoint to redirect existing submission channels to a dataset they control. An endpoint handling domain validation allowed unauthenticated users to enumerate existing enrollments. Finally, other endpoints allowed enumerating if a resource with a known RID exists across enrollments. The affected service has been patched with version 0.815.0 and automatically deployed to all Apollo-managed Foundry instances.

Impact

For European organizations using Palantir Foundry with the secure-upload service, this vulnerability could lead to unauthorized access and manipulation of sensitive data submissions. Privileged users abusing the authorization flaws might redirect data channels to datasets they control, potentially causing data leakage or corruption. The ability for unauthenticated actors to enumerate enrollments and resource existence increases the risk of targeted attacks, reconnaissance, and subsequent exploitation. This could be particularly impactful for sectors handling sensitive or regulated data such as finance, healthcare, and government agencies within Europe. The exposure of enrollment metadata may also facilitate social engineering or insider threat activities. While the vulnerability does not directly cause denial of service, the integrity and confidentiality risks could undermine trust in data submission processes and compliance with data protection regulations like GDPR. Organizations relying on Apollo-managed Foundry instances benefit from automatic patch deployment, but those with self-managed or older versions remain at risk. Overall, the threat could disrupt secure data workflows and expose sensitive information, necessitating prompt remediation to maintain operational security and regulatory compliance.

References

cwe.mitre.org/data/definitions/285.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Jul 2025, 19:01 UTC

Technical details

References

Community reviews

Related threats