{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-19869", "assignerOrgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "state": "PUBLISHED", "assignerShortName": "Neo4j", "dateReserved": "2026-08-14T11:22:26.042Z", "datePublished": "2026-08-18T16:35:19.878Z", "dateUpdated": "2026-08-18T19:09:31.066Z"}, "containers": {"cna": {"providerMetadata": {"orgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "shortName": "Neo4j", "dateUpdated": "2026-08-18T16:35:19.878Z"}, "title": "Privilege Escalation via Dropped Field-Level @authentication", "problemTypes": [{"descriptions": [{"lang": "en", "cweId": "CWE-639", "description": "CWE-639 Authorization bypass through User-Controlled key", "type": "CWE"}]}], "impacts": [{"capecId": "CAPEC-233", "descriptions": [{"lang": "en", "value": "CAPEC-233 Privilege Escalation"}]}], "affected": [{"vendor": "neo4j", "product": "graphql", "collectionURL": "https://registry.npmjs.org", "packageName": "@neo4j/graphql", "repo": "https://github.com/neo4j/graphql", "versions": [{"status": "affected", "version": "7.0.0", "lessThan": "7.6.0", "versionType": "semver"}, {"status": "affected", "version": "5.2.0", "lessThan": "5.12.15", "versionType": "semver"}, {"status": "affected", "version": "6.0.0", "lessThanOrEqual": "6.6.4", "versionType": "semver"}], "defaultStatus": "unaffected"}], "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"}]}]}], "descriptions": [{"lang": "en", "value": "@neo4j/graphql\u00a0from\u00a05.2.0\u00a0until the patched versions fails to enforce field-level\u00a0@authentication\u00a0rules on root custom-resolver fields when a type-level\u00a0@authentication\u00a0rule is also present on the same operation type. When both a type-level\u00a0@authentication\u00a0(on\u00a0Query/Mutation) and a field-level\u00a0@authentication\u00a0(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 \u2014 such as an admin-role JWT claim (jwt: { roles_INCLUDES: \"admin\" }) \u2014 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.\u00a0roles: [\"user\"]) is sufficient.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<code>@neo4j/graphql</code>&nbsp;from&nbsp;<code>5.2.0</code>&nbsp;until the patched versions fails to enforce field-level&nbsp;<code>@authentication</code>&nbsp;rules on root custom-resolver fields when a type-level&nbsp;<code>@authentication</code>&nbsp;rule is also present on the same operation type. When both a type-level&nbsp;<code>@authentication</code>&nbsp;(on&nbsp;<code>Query</code>/<code>Mutation</code>) and a field-level&nbsp;<code>@authentication</code>&nbsp;(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 \u2014 such as an admin-role JWT claim (<code>jwt: { roles_INCLUDES: \"admin\" }</code>) \u2014 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.&nbsp;<code>roles: [\"user\"]</code>) is sufficient."}]}], "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"}}], "source": {"discovery": "INTERNAL"}, "x_generator": {"engine": "Vulnogram 1.0.4"}, "configurations": [{"lang": "en", "value": "The application enables\u00a0features.authorization\u00a0and defines a root operation type (Query/Mutation) annotated with\u00a0@authentication\u00a0that also contains one or more custom-resolver fields carrying their own, stricter\u00a0@authentication\u00a0rule.", "supportingMedia": [{"type": "text/html", "base64": false, "value": "<p>The application enables&nbsp;<code>features.authorization</code>&nbsp;and defines a root operation type (<code>Query</code>/<code>Mutation</code>) annotated with&nbsp;<code>@authentication</code>&nbsp;that also contains one or more custom-resolver fields carrying their own, stricter&nbsp;<code>@authentication</code>&nbsp;rule.</p>"}]}], "solutions": [{"lang": "en", "value": "Upgrade the library to\u00a07.5.7+ or\u00a05.12.15+. v6 is end-of-life and will not receive a fix. v5 releases prior to\u00a05.2.0\u00a0are not affected.\n\n\n\nFor users who cannot upgrade immediately: do not combine a type-level\u00a0@authentication\u00a0with a field-level\u00a0@authentication\u00a0on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement \u2014 instead apply a complete\u00a0@authentication\u00a0directive 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": "<p>Upgrade the library to&nbsp;<code>7.5.7</code>+ or&nbsp;<code>5.12.15</code>+. v6 is end-of-life and will not receive a fix. v5 releases prior to&nbsp;<code>5.2.0</code>&nbsp;are not affected.</p><p>For users who cannot upgrade immediately: do not combine a type-level&nbsp;<code>@authentication</code>&nbsp;with a field-level&nbsp;<code>@authentication</code>&nbsp;on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement \u2014 instead apply a complete&nbsp;<code>@authentication</code>&nbsp;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.</p>"}]}]}, "adp": [{"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"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-08-18T19:09:31.066Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-19869", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-08-18T19:09:25.351012Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-08-18T19:09:28.215Z"}}], "cna": {"title": "Privilege Escalation via Dropped Field-Level @authentication", "source": {"discovery": "INTERNAL"}, "impacts": [{"capecId": "CAPEC-233", "descriptions": [{"lang": "en", "value": "CAPEC-233 Privilege Escalation"}]}], "metrics": [{"format": "CVSS", "cvssV4_0": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 7.6, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "HIGH", "valueDensity": "NOT_DEFINED", "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", "exploitMaturity": "NOT_DEFINED", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "LOW", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "affected": [{"repo": "https://github.com/neo4j/graphql", "vendor": "neo4j", "product": "graphql", "versions": [{"status": "affected", "version": "7.0.0", "lessThan": "7.6.0", "versionType": "semver"}, {"status": "affected", "version": "5.2.0", "lessThan": "5.12.15", "versionType": "semver"}, {"status": "affected", "version": "6.0.0", "versionType": "semver", "lessThanOrEqual": "6.6.4"}], "packageName": "@neo4j/graphql", "collectionURL": "https://registry.npmjs.org", "defaultStatus": "unaffected"}], "solutions": [{"lang": "en", "value": "Upgrade the library to\u00a07.5.7+ or\u00a05.12.15+. v6 is end-of-life and will not receive a fix. v5 releases prior to\u00a05.2.0\u00a0are not affected.\n\n\n\nFor users who cannot upgrade immediately: do not combine a type-level\u00a0@authentication\u00a0with a field-level\u00a0@authentication\u00a0on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement \u2014 instead apply a complete\u00a0@authentication\u00a0directive 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", "value": "<p>Upgrade the library to&nbsp;<code>7.5.7</code>+ or&nbsp;<code>5.12.15</code>+. v6 is end-of-life and will not receive a fix. v5 releases prior to&nbsp;<code>5.2.0</code>&nbsp;are not affected.</p><p>For users who cannot upgrade immediately: do not combine a type-level&nbsp;<code>@authentication</code>&nbsp;with a field-level&nbsp;<code>@authentication</code>&nbsp;on the same root operation type. Because the type-level annotation is what shadows the field-level rule, removing it restores correct enforcement \u2014 instead apply a complete&nbsp;<code>@authentication</code>&nbsp;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.</p>", "base64": false}]}], "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"]}], "x_generator": {"engine": "Vulnogram 1.0.4"}, "descriptions": [{"lang": "en", "value": "@neo4j/graphql\u00a0from\u00a05.2.0\u00a0until the patched versions fails to enforce field-level\u00a0@authentication\u00a0rules on root custom-resolver fields when a type-level\u00a0@authentication\u00a0rule is also present on the same operation type. When both a type-level\u00a0@authentication\u00a0(on\u00a0Query/Mutation) and a field-level\u00a0@authentication\u00a0(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 \u2014 such as an admin-role JWT claim (jwt: { roles_INCLUDES: \"admin\" }) \u2014 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.\u00a0roles: [\"user\"]) is sufficient.", "supportingMedia": [{"type": "text/html", "value": "<code>@neo4j/graphql</code>&nbsp;from&nbsp;<code>5.2.0</code>&nbsp;until the patched versions fails to enforce field-level&nbsp;<code>@authentication</code>&nbsp;rules on root custom-resolver fields when a type-level&nbsp;<code>@authentication</code>&nbsp;rule is also present on the same operation type. When both a type-level&nbsp;<code>@authentication</code>&nbsp;(on&nbsp;<code>Query</code>/<code>Mutation</code>) and a field-level&nbsp;<code>@authentication</code>&nbsp;(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 \u2014 such as an admin-role JWT claim (<code>jwt: { roles_INCLUDES: \"admin\" }</code>) \u2014 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.&nbsp;<code>roles: [\"user\"]</code>) is sufficient.", "base64": false}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-639", "description": "CWE-639 Authorization bypass through User-Controlled key"}]}], "configurations": [{"lang": "en", "value": "The application enables\u00a0features.authorization\u00a0and defines a root operation type (Query/Mutation) annotated with\u00a0@authentication\u00a0that also contains one or more custom-resolver fields carrying their own, stricter\u00a0@authentication\u00a0rule.", "supportingMedia": [{"type": "text/html", "value": "<p>The application enables&nbsp;<code>features.authorization</code>&nbsp;and defines a root operation type (<code>Query</code>/<code>Mutation</code>) annotated with&nbsp;<code>@authentication</code>&nbsp;that also contains one or more custom-resolver fields carrying their own, stricter&nbsp;<code>@authentication</code>&nbsp;rule.</p>", "base64": false}]}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "7.6.0", "versionStartIncluding": "7.0.0"}, {"criteria": "cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.12.15", "versionStartIncluding": "5.2.0"}, {"criteria": "cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndIncluding": "6.6.4", "versionStartIncluding": "6.0.0"}], "operator": "OR"}], "operator": "OR"}], "providerMetadata": {"orgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "shortName": "Neo4j", "dateUpdated": "2026-08-18T16:35:19.878Z"}}}, "cveMetadata": {"cveId": "CVE-2026-19869", "state": "PUBLISHED", "dateUpdated": "2026-08-18T19:09:31.066Z", "dateReserved": "2026-08-14T11:22:26.042Z", "assignerOrgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "datePublished": "2026-08-18T16:35:19.878Z", "assignerShortName": "Neo4j"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"collectionURL": "https://registry.npmjs.org", "defaultStatus": "unaffected", "packageName": "@neo4j/graphql", "product": "graphql", "repo": "https://github.com/neo4j/graphql", "vendor": "neo4j", "versions": [{"lessThan": "7.6.0", "status": "affected", "version": "7.0.0", "versionType": "semver"}, {"lessThan": "5.12.15", "status": "affected", "version": "5.2.0", "versionType": "semver"}, {"lessThanOrEqual": "6.6.4", "status": "affected", "version": "6.0.0", "versionType": "semver"}]}], "source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "@neo4j/graphql\u00a0from\u00a05.2.0\u00a0until the patched versions fails to enforce field-level\u00a0@authentication\u00a0rules on root custom-resolver fields when a type-level\u00a0@authentication\u00a0rule is also present on the same operation type. When both a type-level\u00a0@authentication\u00a0(on\u00a0Query/Mutation) and a field-level\u00a0@authentication\u00a0(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 \u2014 such as an admin-role JWT claim (jwt: { roles_INCLUDES: \"admin\" }) \u2014 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.\u00a0roles: [\"user\"]) is sufficient."}], "id": "CVE-2026-19869", "lastModified": "2026-08-18T20:17:13.830", "metrics": {"cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "attackVector": "NETWORK", "availabilityRequirement": "NOT_DEFINED", "baseScore": 7.6, "baseSeverity": "HIGH", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "LOW", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "version": "4.0", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-19869", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-08-18T19:09:25.351012Z", "version": "2.0.3"}}]}, "published": "2026-08-18T17:16:57.227", "references": [{"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "url": "https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5"}, {"source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "url": "https://neo4j.com/security/CVE-2026-19869"}], "sourceIdentifier": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "vulnStatus": "Received", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-639"}], "source": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[7.0.0,7.6.0)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[5.2.0,5.12.15)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[6.0.0,6.6.4]"}}], "enrichment": {"confidence": 95.0, "confidence_source": "inferred", "scores": [{"score": 95.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "graphql", "source": "cna", "vendor": "neo4j"}, "product": "graphql", "vendor": "neo4j"}], "created": "2026-08-18T19:30:04.212578+00:00", "updated": "2026-08-18T20:00:04.530552+00:00", "vendors": ["neo4j", "neo4j$PRODUCT$graphql"]}