{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-19869 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-19869 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-19869 is a high-severity missing authorization vulnerability in neo4j graphql, published on 18 Aug 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-19869 and fix it if it is affected.\n\nWhat it is: CVE-2026-19869 is a high-severity missing authorization vulnerability in neo4j graphql, published on 18 Aug 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-19869 in the wild and no public exploit code.\n\nAffected product: neo4j graphql. 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-19869/ (Markdown: https://insights.sbomify.com/CVE-2026-19869/index.md)","id":"CVE-2026-19869","markdown":"https://insights.sbomify.com/CVE-2026-19869/index.md","name":"CVE-2026-19869","record":{"aliases":["GHSA-82m8-p9px-c3x5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"Neo4j GraphQL library","requires_auth":"low_privilege","summary":"Attackers with valid non-admin tokens can access restricted fields because field-level authentication rules are ignored when type-level rules exist.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Neo4j","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"@neo4j/graphql from 5.2.0 until the patched versions fails to enforce field-level @authentication rules on root custom-resolver fields when a type-level @authentication rule is also present on the same operation type. When both a type-level @authentication (on Query/Mutation) and a field-level @authentication (on a root custom-resolver field within that type) are declared, only the type-level rule is evaluated and the field-level rule is silently discarded. As a result a stricter per-field requirement — such as an admin-role JWT claim (jwt: { roles_INCLUDES: \"admin\" }) — is never checked, and any client that satisfies the coarser type-level requirement can invoke the more-restricted field. No token forgery is involved: a legitimately issued, correctly signed non-admin token (e.g. roles: [\"user\"]) is sufficient.","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":"Privilege Escalation via Dropped Field-Level @authentication","id":"CVE-2026-19869","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"IDOR in Prospero Flow CRM allows cross-tenant payroll disclosure and creation","id":"CVE-2026-19870"},"packages":[],"prev":{"headline":"Uncapped mention keys in user notification properties allow CPU exhaustion during post processing","id":"CVE-2026-19867"},"products":["graphql"],"published":"2026-08-18","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":"total"},"state":"PUBLISHED","updated":"2026-08-19","vendors":["neo4j"]},"summary":"Attackers with valid non-admin tokens can access restricted fields because field-level authentication rules are ignored when type-level rules exist.","url":"https://insights.sbomify.com/CVE-2026-19869/"}