{"answers":{"affected":"1 open source package ship an affected version, including parse.","exploited":"There is no known exploitation of CVE-2026-100631 in the wild and no public exploit code.","fix":"Upgrade parse to a fixed version for your release line: 8.6.90 or 9.10.1.","what":"CVE-2026-100631 is a high-severity code injection vulnerability in parse-community parse-server, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-100631 and fix it if it is affected.\n\nWhat it is: CVE-2026-100631 is a high-severity code injection vulnerability in parse-community parse-server, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-100631 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- parse (Bitnami): affected all versions; fixed in 8.6.90, 9.10.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-100631/ (Markdown: https://insights.sbomify.com/CVE-2026-100631/index.md)","id":"CVE-2026-100631","markdown":"https://insights.sbomify.com/CVE-2026-100631/index.md","name":"CVE-2026-100631","record":{"aliases":["BIT-parse-2026-100631","GHSA-cc6h-c8m4-hgrx","GHSA-fq69-3pm5-2h3g"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Parse Server backend","requires_auth":"none","summary":"Unauthenticated attackers can inject query operators to delete all device registrations, disrupting push notifications in Parse Server deployments.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-943","name":"Improper Neutralization of Special Elements in Data Query Logic"}],"description":"Parse Server is an open source backend server. In versions prior to 8.6.90 and in versions from 9.0.0 prior to 9.10.1-alpha.9, the device token deduplication logic for installation records does not validate the type of client-supplied installation fields before using them to build database queries. An unauthenticated remote attacker who knows only the public application ID can submit non-string values in these fields to inject query operators, causing the deduplication cleanup — which runs with elevated privileges before class-level permissions are evaluated — to delete every device registration in the application or an attacker-chosen subset of them. No account, session token, master key, or user interaction is required. Deleted registrations cannot be recovered on the server, so push notifications cannot be delivered until every client re-registers. Any deployment that exposes the REST API to clients and uses push notifications is affected in its default configuration. Versions 8.6.90 and 9.10.1-alpha.9 fix the issue by rejecting non-string values with a client error and by scoping the deduplication cleanup to the calling application. No workaround other than upgrading is available.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Parse Server 9.0.0 Unauthenticated Installation Deletion via Operator Injection","id":"CVE-2026-100631","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Parse Server 9.0.0 before 9.10.1 Protected Fields Disclosure via LiveQuery","id":"CVE-2026-100632"},"packages":[{"ecosystem":"Bitnami","fixed":["8.6.90","9.10.1"],"introduced":["0","9.0.0"],"last_affected":[],"package":"parse","purl":"pkg:bitnami/parse","source":"BIT-parse-2026-100631"}],"prev":{"headline":"AVideo before 29.1.0 Stored XSS via HTML Entity Bypass in trailer1 Field","id":"CVE-2026-100630"},"products":["parse-server"],"published":"2026-09-26","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["parse-community"]},"summary":"Unauthenticated attackers can inject query operators to delete all device registrations, disrupting push notifications in Parse Server deployments.","url":"https://insights.sbomify.com/CVE-2026-100631/"}