CVE-2024-29027VulnerabilityPublished 21 Mar 2024Updated 8 Sep 2026

CVE-2024-29027: Parse Server crash and RCE via invalid Cloud Function or Cloud Job name

Affects parseSource GCVE Database

Not known to be exploited : upgrade to 6.5.5 as a priority.

Data as of 26 Oct 2026, 06:26 UTC

Severity

Critical

Rated by Threat Radar · No CVSS score from NVD or the CNA

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

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Mar 2024
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

Upgrade parse to 6.5.5.

Patches and advisories

Affected software

Product	Affected	Fixed in
Bitnamiparse`pkg:bitnami/parse`Other threats	Affected <6.5.5	Fixed in 6.5.5

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

AI-suggested

A patch is available in Parse Server versions 6.5.5 and 7.0.0 that adds string sanitation for Cloud Function and Cloud Job names. Users should upgrade to these versions to remediate the vulnerability. As a temporary workaround, sanitize Cloud Function and Cloud Job names before they are processed by Parse Server.

Description

Parse Server versions prior to 6.5.5 and 7.0.0 contain a critical vulnerability where calling an invalid Cloud Function or Cloud Job name can crash the server and potentially allow code injection, internal store manipulation, or remote code execution. The issue is addressed by input string sanitation in versions 6.5.5 and 7.0.0. Users should sanitize Cloud Function and Cloud Job names before they reach Parse Server as a workaround.

References

Community reviews

Loading reviews…