{"answers":{"affected":"2 open source packages ship an affected version, including parse-dashboard. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27610 in the wild and no public exploit code.","fix":"Upgrade parse-dashboard to 9.0.0-alpha.8 or later.","what":"CVE-2026-27610 is a high-severity vulnerability in parse-community parse-dashboard, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-27610 and fix it if it is affected.\n\nWhat it is: CVE-2026-27610 is a high-severity vulnerability in parse-community parse-dashboard, published on 25 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-27610 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- parse-dashboard (npm): affected from 7.3.0-alpha.42; fixed in 9.0.0-alpha.8\n- parse-dashboard (npm): affected from 7.3.0-alpha.42; fixed in 9.0.0-alpha.8\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-27610/ (Markdown: https://insights.sbomify.com/CVE-2026-27610/index.md)","id":"CVE-2026-27610","markdown":"https://insights.sbomify.com/CVE-2026-27610/index.md","name":"CVE-2026-27610","record":{"aliases":["GHSA-jhp4-jvq3-w5xr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Parse Dashboard","requires_auth":"low_privilege","summary":"A cache key collision in Parse Dashboard allows read-only users to potentially access the full master key, leading to unauthorized data access and privilege escalation.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"parse_dashboard","vendor":"parseplatform"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1289","name":"Improper Validation of Unsafe Equivalence in Input"}],"description":"Parse Dashboard is a standalone dashboard for managing Parse Server apps. In versions 7.3.0-alpha.42 through 9.0.0-alpha.7, the `ConfigKeyCache` uses the same cache key for both master key and read-only master key when resolving function-typed keys. Under specific timing conditions, a read-only user can receive the cached full master key, or a regular user can receive the cached read-only master key. The fix in version 9.0.0-alpha.8 uses distinct cache keys for master key and read-only master key. As a workaround, avoid using function-typed master keys, or remove the `agent` configuration block from your dashboard configuration.","ecosystems":["npm"],"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 Dashboard Has a Cache Key Collision that Leaks Master Key to Read-Only Sessions","id":"CVE-2026-27610","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"FileBrowser Quantum: Password Protection Not Enforced on Shared File Links","id":"CVE-2026-27611"},"packages":[{"ecosystem":"npm","fixed":["9.0.0-alpha.8"],"introduced":["7.3.0-alpha.42"],"last_affected":[],"package":"parse-dashboard","purl":null,"source":"GHSA-jhp4-jvq3-w5xr"},{"ecosystem":"npm","fixed":["9.0.0-alpha.8"],"introduced":["7.3.0-alpha.42"],"last_affected":[],"package":"parse-dashboard","purl":"pkg:npm/parse-dashboard","source":"GHSA-jhp4-jvq3-w5xr"}],"prev":{"headline":"Parse Dashboard Missing CSRF Protection on Agent Endpoint","id":"CVE-2026-27609"},"products":["parse-dashboard"],"published":"2026-02-25","related":[{"cvss_score":9.9,"headline":"Parse Dashboard has incomplete authentication on AI Agent endpoint","id":"CVE-2026-27595","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":9.3,"headline":"Parse Dashboard Missing Authorization on Agent Endpoint","id":"CVE-2026-27608","kev_date_added":null,"published":"2026-02-25"},{"cvss_score":8.3,"headline":"Parse Dashboard Missing CSRF Protection on Agent Endpoint","id":"CVE-2026-27609","kev_date_added":null,"published":"2026-02-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-27","vendors":["parse-community"]},"summary":"A cache key collision in Parse Dashboard allows read-only users to potentially access the full master key, leading to unauthorized data access and privilege escalation.","url":"https://insights.sbomify.com/CVE-2026-27610/"}