{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119569 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119569 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119569 is a medium-severity vulnerability in parse-community parse-server, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119569 and fix it if it is affected.\n\nWhat it is: CVE-2026-119569 is a medium-severity vulnerability in parse-community parse-server, published on 30 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119569 in the wild and no public exploit code.\n\nAffected product: parse-community parse-server. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-119569/ (Markdown: https://insights.sbomify.com/CVE-2026-119569/index.md)","id":"CVE-2026-119569","markdown":"https://insights.sbomify.com/CVE-2026-119569/index.md","name":"CVE-2026-119569","record":{"aliases":["GHSA-5gp4-jgm9-v67j","GHSA-rx55-fw4j-pvpx"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"Parse Server before 8.6.108 and 9.0.0 before 9.10.5-alpha.9 contains a prototype pollution vulnerability because user-controlled keys are expanded into objects without own-property checks. Clients with class write access can send dot notation field keys or ACL entry names matching built-in object members to corrupt built-in functions, causing all requests to fail until server restart.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Parse Server 9.0.0 before 9.10.5-alpha.9 Prototype Pollution Denial of Service","id":"CVE-2026-119569","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Parse Server 9.7.0 before 9.10.5-alpha.7 Protected Field Exposure in Save Responses","id":"CVE-2026-119570"},"nickname":null,"packages":[],"prev":{"headline":"vsftpd through 3.0.5 require_ssl_reuse Bypass via FTPS Data Channel Hijacking","id":"CVE-2026-119568"},"products":["parse-server"],"published":"2026-10-30","related":[],"sources":[{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-30","vendors":["parse-community"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119569/"}