CVE-2024-49587VulnerabilityPublished 19 Dec 2025Updated 26 Feb 2026

CVE-2024-49587: com.palantir.gotham:glutton · The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.

Affects com.palantir.gotham:gluttonSource CVE Database V5

Not known to be exploited · CVSS 9.1 Critical.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score

9.1Critical

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
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: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 19 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-26.

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

AI-suggested

To mitigate CVE-2024-49587, organizations should immediately verify that all Gotham instances, especially those managed via Apollo, have received and applied the official patch from Palantir. Network segmentation should be enforced to restrict access to Glutton service endpoints only to authorized internal systems and users. Implement additional layers of authentication and authorization controls around critical backend services to prevent direct unauthenticated access. Conduct thorough audits of access logs and monitor for any unusual activity targeting Glutton endpoints. Employ runtime application self-protection (RASP) or web application firewalls (WAF) to detect and block unauthorized requests. Review and enhance secure development lifecycle (SDLC) practices to prevent similar implementation weaknesses in future releases. Coordinate with Palantir support for guidance on patch deployment and incident response. Finally, maintain up-to-date inventory of affected systems and conduct regular vulnerability assessments to ensure no residual exposure remains.

Description

Glutton V1 service endpoints were exposed without any authentication on Gotham stacks, this could have allowed users that did not have any permission to hit glutton backend directly and read/update/delete data. The affected service has been patched and automatically deployed to all Apollo-managed Gotham Instances

Impact

The impact of CVE-2024-49587 is severe for organizations using Palantir Gotham, especially those relying on the Glutton service for sensitive data processing. Unauthorized access to backend services can lead to data breaches, unauthorized data manipulation, and potential disruption of critical operations. Confidential information could be exposed or altered, undermining trust and compliance with data protection regulations. Since the vulnerability requires no authentication or user interaction, exploitation can be automated and executed remotely over the network, increasing the risk of widespread attacks. Organizations in sectors such as government, defense, intelligence, and large enterprises that use Gotham stacks are particularly at risk. The compromise of such systems could have cascading effects on national security, operational integrity, and business continuity. Although no exploits are currently known in the wild, the high CVSS score and critical severity indicate that attackers will likely target this vulnerability rapidly if not remediated promptly.

References

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

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 06:25 UTC

Technical details

References

Community reviews

Related threats