{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-30848", "tracking": { "current_release_date": "2026-03-23T01:34:52.424203Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-30848", "initial_release_date": "2026-03-07T16:38:42.917941Z", "revision_history": [ { "date": "2026-03-07T16:38:42.917941Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (2).| References created (1).| CWES updated (1)." }, { "date": "2026-03-07T16:38:44.789692Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-03-07T17:25:05.346979Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (1).| CWES updated (1)." }, { "date": "2026-03-07T17:25:07.999542Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-03-08T14:48:54.137537Z", "number": "5", "summary": "Source created.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-08T14:49:03.264794Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-03-09T18:21:05.961425Z", "number": "7", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (2).| References created (2).| CWES updated (1)." }, { "date": "2026-03-09T18:21:10.734549Z", "number": "8", "summary": "NCSC Score updated." }, { "date": "2026-03-09T18:39:27.056414Z", "number": "9", "summary": "Unknown change." }, { "date": "2026-03-09T18:52:48.127313Z", "number": "10", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (3).| CWES updated (1)." }, { "date": "2026-03-09T18:52:49.362552Z", "number": "11", "summary": "NCSC Score updated." }, { "date": "2026-03-10T17:25:30.399327Z", "number": "12", "summary": "CVSS created.| Products created (9).| Product Identifiers created (9)." }, { "date": "2026-03-10T17:25:33.967430Z", "number": "13", "summary": "NCSC Score updated." }, { "date": "2026-03-19T15:28:56.650842Z", "number": "14", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (3).| CWES updated (1)." }, { "date": "2026-03-19T15:28:58.529978Z", "number": "15", "summary": "NCSC Score updated." }, { "date": "2026-03-20T09:33:51.815234Z", "number": "16", "summary": "Source connected.| CVE status created. (valid)| EPSS created." } ], "status": "interim", "version": "16" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha1", "product": { "name": "vers:unknown/9.5.0-alpha1", "product_id": "CSAFPID-5775209", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha1:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha2", "product": { "name": "vers:unknown/9.5.0-alpha2", "product_id": "CSAFPID-5775210", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha2:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha3", "product": { "name": "vers:unknown/9.5.0-alpha3", "product_id": "CSAFPID-5775211", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha3:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha4", "product": { "name": "vers:unknown/9.5.0-alpha4", "product_id": "CSAFPID-5775212", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha4:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha5", "product": { "name": "vers:unknown/9.5.0-alpha5", "product_id": "CSAFPID-5775213", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha5:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha6", "product": { "name": "vers:unknown/9.5.0-alpha6", "product_id": "CSAFPID-5775214", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha6:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/9.5.0-alpha7", "product": { "name": "vers:unknown/9.5.0-alpha7", "product_id": "CSAFPID-5775215", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:9.5.0:alpha7:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/<8.6.8", "product": { "name": "vers:unknown/<8.6.8", "product_id": "CSAFPID-5775207", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=9.0.0|<9.5.0", "product": { "name": "vers:unknown/>=9.0.0|<9.5.0", "product_id": "CSAFPID-5775208", "product_identification_helper": { "cpe": "cpe:2.3:a:parseplatform:parse-server:*:*:*:*:*:node.js:*:*" } } } ], "category": "product_name", "name": "parse-server" } ], "category": "vendor", "name": "Parse Platform" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/<8.6.8", "product": { "name": "vers:unknown/<8.6.8", "product_id": "CSAFPID-5769893" } }, { "category": "product_version_range", "name": "vers:unknown/<9.5.0-alpha.8", "product": { "name": "vers:unknown/<9.5.0-alpha.8", "product_id": "CSAFPID-5769894" } }, { "category": "product_version_range", "name": "vers:unknown/>=0|<8.6.8", "product": { "name": "vers:unknown/>=0|<8.6.8", "product_id": "CSAFPID-5771930" } }, { "category": "product_version_range", "name": "vers:unknown/>=9.0.0-alpha.1|<9.5.0-alpha.8", "product": { "name": "vers:unknown/>=9.0.0-alpha.1|<9.5.0-alpha.8", "product_id": "CSAFPID-5771931" } } ], "category": "product_name", "name": "parse-server" } ], "category": "vendor", "name": "parse-community" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-30848", "cwe": { "id": "CWE-22", "name": "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')" }, "notes": [ { "category": "description", "text": "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.", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-30848" }, { "category": "description", "text": "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.", "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-30848" }, { "category": "description", "text": "### Impact\n\nThe `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`).\n\nThis 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.\n\n### Patches\n\nThe fix enforces a path separator boundary in the check, ensuring resolved paths must be strictly inside the `pagesPath` directory.\n\n### Workarounds\n\nEnsure 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.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-hm3f-q6rw-m6wh\n- Fix for Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.8\n- Fix for Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.8", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/npm%2FGHSA-hm3f-q6rw-m6wh.json?alt=media" }, { "category": "description", "text": "### Impact\n\nThe `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`).\n\nThis 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.\n\n### Patches\n\nThe fix enforces a path separator boundary in the check, ensuring resolved paths must be strictly inside the `pagesPath` directory.\n\n### Workarounds\n\nEnsure 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.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-hm3f-q6rw-m6wh\n- Fix for Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.8\n- Fix for Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.8", "title": "github - https://github.com/advisories/GHSA-hm3f-q6rw-m6wh" }, { "category": "description", "text": "### Impact\n\nThe `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`).\n\nThis 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.\n\n### Patches\n\nThe fix enforces a path separator boundary in the check, ensuring resolved paths must be strictly inside the `pagesPath` directory.\n\n### Workarounds\n\nEnsure 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.\n\n### References\n\n- GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-hm3f-q6rw-m6wh\n- Fix for Parse Server 9: https://github.com/parse-community/parse-server/releases/tag/9.5.0-alpha.8\n- Fix for Parse Server 8: https://github.com/parse-community/parse-server/releases/tag/8.6.8", "title": "github - https://api.github.com/advisories/GHSA-hm3f-q6rw-m6wh" }, { "category": "other", "text": "0.00068", "title": "EPSS" }, { "category": "other", "text": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N", "title": "CVSSV4" }, { "category": "other", "text": "6.3", "title": "CVSSV4 base score" }, { "category": "other", "text": "3.8", "title": "NCSC Score" }, { "category": "other", "text": "The value of the most recent EPSS score, The value of the most recent CVSS (V3) score, Is related to (a version of) an uncommon product, Is related to an uncommon product vendor", "title": "NCSC Score top decreasing factors" } ], "product_status": { "known_affected": [ "CSAFPID-5769893", "CSAFPID-5769894", "CSAFPID-5771930", "CSAFPID-5771931", "CSAFPID-5775207", "CSAFPID-5775208", "CSAFPID-5775209", "CSAFPID-5775210", "CSAFPID-5775211", "CSAFPID-5775212", "CSAFPID-5775213", "CSAFPID-5775214", "CSAFPID-5775215" ] }, "references": [ { "category": "external", "summary": "Source - cveprojectv5", "url": "https://www.cve.org/CVERecord?id=CVE-2026-30848" }, { "category": "external", "summary": "Source raw - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/30xxx/CVE-2026-30848.json" }, { "category": "external", "summary": "Source - nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-30848" }, { "category": "external", "summary": "Source raw - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-30848" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-30848" }, { "category": "external", "summary": "Source raw - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/npm%2FGHSA-hm3f-q6rw-m6wh.json?alt=media" }, { "category": "external", "summary": "Source - github", "url": "https://github.com/advisories/GHSA-hm3f-q6rw-m6wh" }, { "category": "external", "summary": "Source raw - github", "url": "https://api.github.com/advisories/GHSA-hm3f-q6rw-m6wh" }, { "category": "external", "summary": "Source - github", "url": "https://api.github.com/advisories/GHSA-hm3f-q6rw-m6wh" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Reference - cveprojectv5; github; nvd; osv", "url": "https://github.com/parse-community/parse-server/security/advisories/GHSA-hm3f-q6rw-m6wh" }, { "category": "external", "summary": "Reference - github; osv", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-30848" }, { "category": "external", "summary": "Reference - github", "url": "https://github.com/advisories/GHSA-hm3f-q6rw-m6wh" } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N", "baseScore": 3.7, "baseSeverity": "LOW" }, "products": [ "CSAFPID-5769893", "CSAFPID-5769894", "CSAFPID-5771930", "CSAFPID-5771931", "CSAFPID-5775207", "CSAFPID-5775208", "CSAFPID-5775209", "CSAFPID-5775210", "CSAFPID-5775211", "CSAFPID-5775212", "CSAFPID-5775213", "CSAFPID-5775214", "CSAFPID-5775215" ] } ], "title": "CVE-2026-30848" } ] }