{"id":"CVE-2026-19869","state":"PUBLISHED","title":"Privilege Escalation via Dropped Field-Level @authentication","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.","publishedAt":"2026-08-18T16:35:19.878Z","updatedAt":"2026-08-19T16:02:04.528Z","severity":{"score":7.6,"label":"High","version":"4.0","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","source":"Neo4j"},"assigner":"Neo4j","products":["neo4j graphql"],"affected":[{"vendor":"neo4j","product":"graphql","packageName":"@neo4j/graphql","defaultStatus":"unaffected","versions":[{"version":"7.0.0","status":"affected","lessThan":"7.6.0","versionType":"semver"},{"version":"5.2.0","status":"affected","lessThan":"5.12.15","versionType":"semver"},{"version":"6.0.0","status":"affected","lessThanOrEqual":"6.6.4","versionType":"semver"}],"collectionURL":"https://registry.npmjs.org","repo":"https://github.com/neo4j/graphql"}],"references":["https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5","https://neo4j.com/security/CVE-2026-19869"],"weaknesses":["CWE-639"],"ingestedAt":"2026-10-29T20:11:10.572Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2026/19xxx/CVE-2026-19869.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2026-19869","state":"PUBLISHED","datePublished":"2026-08-18T16:35:19.878Z","dateUpdated":"2026-08-19T16:02:04.528Z","assignerShortName":"Neo4j","assignerOrgId":"3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6","dateReserved":"2026-08-14T11:22:26.042Z"},"containers":{"cna":{"title":"Privilege Escalation via Dropped Field-Level @authentication","descriptions":[{"lang":"en","value":"@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."}],"affected":[{"vendor":"neo4j","product":"graphql","packageName":"@neo4j/graphql","defaultStatus":"unaffected","versions":[{"version":"7.0.0","status":"affected","lessThan":"7.6.0","versionType":"semver"},{"version":"5.2.0","status":"affected","lessThan":"5.12.15","versionType":"semver"},{"version":"6.0.0","status":"affected","lessThanOrEqual":"6.6.4","versionType":"semver"}],"collectionURL":"https://registry.npmjs.org","repo":"https://github.com/neo4j/graphql"}],"references":[{"url":"https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5","tags":["third-party-advisory"]},{"url":"https://neo4j.com/security/CVE-2026-19869","tags":["vendor-advisory"]}],"metrics":[{"format":"CVSS","scenarios":[{"lang":"en","value":"GENERAL"}],"cvssV4_0":{"attackVector":"NETWORK","attackComplexity":"LOW","attackRequirements":"PRESENT","privilegesRequired":"LOW","userInteraction":"NONE","vulnConfidentialityImpact":"HIGH","subConfidentialityImpact":"NONE","vulnIntegrityImpact":"HIGH","subIntegrityImpact":"NONE","vulnAvailabilityImpact":"NONE","subAvailabilityImpact":"NONE","exploitMaturity":"NOT_DEFINED","Safety":"NOT_DEFINED","Automatable":"NOT_DEFINED","Recovery":"NOT_DEFINED","valueDensity":"NOT_DEFINED","vulnerabilityResponseEffort":"NOT_DEFINED","providerUrgency":"NOT_DEFINED","version":"4.0","baseSeverity":"HIGH","baseScore":7.6,"vectorString":"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"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-639","lang":"en","description":"CWE-639 Authorization bypass through User-Controlled key","type":"CWE"}]}],"providerMetadata":{"shortName":"Neo4j","orgId":"3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6","dateUpdated":"2026-08-19T16:02:04.528Z"},"impacts":[{"capecId":"CAPEC-233","descriptions":[{"lang":"en","value":"CAPEC-233 Privilege Escalation"}]}],"cpeApplicability":[{"operator":"OR","nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*","versionStartIncluding":"7.0.0","versionEndExcluding":"7.6.0"},{"vulnerable":true,"criteria":"cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*","versionStartIncluding":"5.2.0","versionEndExcluding":"5.12.15"},{"vulnerable":true,"criteria":"cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*","versionStartIncluding":"6.0.0","versionEndIncluding":"6.6.4"}]}]}],"configurations":[{"lang":"en","value":"The application enables features.authorization and defines a root operation type (Query/Mutation) annotated with @authentication that also contains one or more custom-resolver fields carrying their own, stricter @authentication rule.","supportingMedia":[{"type":"text/html","base64":false,"value":"

The application enables features.authorization and defines a root operation type (Query/Mutation) annotated with @authentication that also contains one or more custom-resolver fields carrying their own, stricter @authentication rule.

"}]}],"solutions":[{"lang":"en","value":"Upgrade the library to 7.6.0+ or 5.12.15+. v6 is end-of-life and will not receive a fix. v5 releases prior to 5.2.0 are not affected.\n\n\n\nFor users who cannot upgrade immediately: do not combine a type-level @authentication with a field-level @authentication on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement — instead apply a complete @authentication directive to each root field individually, including the full stricter rule on the sensitive field. Alternatively, enforce the stricter requirement inside the custom resolver's own code.","supportingMedia":[{"type":"text/html","base64":false,"value":"

Upgrade the library to 7.6.0+ or 5.12.15+. v6 is end-of-life and will not receive a fix. v5 releases prior to 5.2.0 are not affected.

For users who cannot upgrade immediately: do not combine a type-level @authentication with a field-level @authentication on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement — instead apply a complete @authentication directive to each root field individually, including the full stricter rule on the sensitive field. Alternatively, enforce the stricter requirement inside the custom resolver's own code.

"}]}],"source":{"discovery":"INTERNAL"},"x_generator":{"engine":"Vulnogram 1.0.4"}},"adp":[{"title":"CISA ADP Vulnrichment","metrics":[{"other":{"type":"ssvc","content":{"timestamp":"2026-08-18T19:09:25.351012Z","id":"CVE-2026-19869","options":[{"Exploitation":"none"},{"Automatable":"no"},{"Technical Impact":"total"}],"role":"CISA Coordinator","version":"2.0.3"}}}],"providerMetadata":{"shortName":"CISA-ADP","orgId":"134c704f-9b21-4f2e-91b3-4a467353bcc0","dateUpdated":"2026-08-18T19:09:31.066Z"}}]}}}