CVE-2026-30848

Workarounds

Ensure the pagesPath directory has no sibling directories whose names begin with the same prefix. For example, if pagesPath is /srv/pages, ensure no directory like /srv/pages-backup or /srv/pages_old exists alongside it.

References

• GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-hm3f-q6rw-m6wh
• Fix for Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.8
• Fix for Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.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 affects any Parse Server deployment with the pages feature enabled (pages.enableRouter: true). Exploitation requires a sibling directory of pagesPath whose name begins with the same string as the pages directory name.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

Kodem intelligence

The fix enforces a path separator boundary in the check, ensuring resolved paths must be strictly inside the pagesPath directory.

1. What is CVE-2026-30848? CVE-2026-30848 is a medium-severity path traversal vulnerability in parse-server (npm), affecting versions < 8.6.8. It is fixed in 8.6.8, 9.5.0-alpha.8. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
2. Which versions of parse-server are affected by CVE-2026-30848? parse-server (npm) versions < 8.6.8 is affected.
3. Is there a fix for CVE-2026-30848? Yes. CVE-2026-30848 is fixed in 8.6.8, 9.5.0-alpha.8. Upgrade to this version or later.
4. Is CVE-2026-30848 exploitable, and should I be worried? Whether CVE-2026-30848 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
5. What actually determines whether CVE-2026-30848 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
6. How do I fix CVE-2026-30848?
   • Upgrade parse-server to 8.6.8 or later
   • Upgrade parse-server to 9.5.0-alpha.8 or later

Other vulnerabilities in parse-server