CVE-2026-30848: parse-server · Path Traversal
Affects parse-serverSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 9.5.0-alpha.8 or 8.6.8 when convenient.
Data as of 30 Oct 2026, 06:59 UTC
- 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.
- Patch
- Available – fixed in 9.5.0-alpha.8, 8.6.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 Oct 2026.
What to do
Upgrade parse-server to 9.5.0-alpha.8 or 8.6.8; parse-community/parse-server to 8.6.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| parse-communityparse-server | Affected
| Fixed in
|
| parse-communityparse-server | Affected
| Fixed in
|
npmparse-community/parse-serverpkg:npm/parse-community/parse-serverOther 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
Organizations should immediately upgrade parse-server to version 8.6.8 or later, or 9.5.0-alpha.8 or later, where the vulnerability is patched. If upgrading is not immediately feasible, implement strict access controls on the server filesystem to restrict read permissions to only necessary directories and files, minimizing the impact of potential traversal. Additionally, configure web server or reverse proxy rules to limit access to sensitive directories and files outside the intended pagesPath. Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with rules to detect and block path traversal patterns in HTTP requests. Conduct thorough audits of directory structures to avoid sibling directories with similar prefixes that could be exploited. Monitor logs for suspicious requests containing traversal sequences. Finally, review and harden file serving logic in custom deployments to ensure proper boundary checks that enforce directory separators and canonical path validation.
Description
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.8 and 9.5.0-alpha.8, the PagesRouter static file serving route is vulnerable to a path traversal attack that allows unauthenticated reading of files outside the configured pagesPath directory. The boundary check uses a string prefix comparison without enforcing a directory separator boundary. An attacker can use path traversal sequences to access files in sibling directories whose names share the same prefix as the pages directory (e.g.pages-secret starts with pages). This issue has been patched in versions 8.6.8 and 9.5.0-alpha.8.