CVE-2026-19869 (GCVE-0-2026-19869)
Vulnerability from cvelistv5
Published
2026-08-18 16:35
Modified
2026-08-19 16:02
CWE
  • CWE-639 - Authorization bypass through User-Controlled key
Summary
@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.
Impacted products
Vendor Product Version
neo4j graphql Version: 7.0.0   
Version: 5.2.0   
Version: 6.0.0    6.6.4
Create a notification for this product.
Show details on NVD website


{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-19869",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "total"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-08-18T19:09:25.351012Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-08-18T19:09:31.066Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "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"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eThe application enables\u0026nbsp;\u003ccode\u003efeatures.authorization\u003c/code\u003e\u0026nbsp;and defines a root operation type (\u003ccode\u003eQuery\u003c/code\u003e/\u003ccode\u003eMutation\u003c/code\u003e) annotated with\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;that also contains one or more custom-resolver fields carrying their own, stricter\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;rule.\u003c/p\u003e"
            }
          ],
          "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."
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "7.6.0",
                  "versionStartIncluding": "7.0.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "5.12.15",
                  "versionStartIncluding": "5.2.0",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:a:neo4j:graphql:*:*:*:*:*:*:*:*",
                  "versionEndIncluding": "6.6.4",
                  "versionStartIncluding": "6.0.0",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ],
          "operator": "OR"
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003ccode\u003e@neo4j/graphql\u003c/code\u003e\u0026nbsp;from\u0026nbsp;\u003ccode\u003e5.2.0\u003c/code\u003e\u0026nbsp;until the patched versions fails to enforce field-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;rules on root custom-resolver fields when a type-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;rule is also present on the same operation type. When both a type-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;(on\u0026nbsp;\u003ccode\u003eQuery\u003c/code\u003e/\u003ccode\u003eMutation\u003c/code\u003e) and a field-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;(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 (\u003ccode\u003ejwt: { roles_INCLUDES: \"admin\" }\u003c/code\u003e) \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.\u0026nbsp;\u003ccode\u003eroles: [\"user\"]\u003c/code\u003e) is sufficient."
            }
          ],
          "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."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-233",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-233 Privilege Escalation"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 7.6,
            "baseSeverity": "HIGH",
            "exploitMaturity": "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",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "HIGH",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-639",
              "description": "CWE-639 Authorization bypass through User-Controlled key",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-19T16:02:04.528Z",
        "orgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
        "shortName": "Neo4j"
      },
      "references": [
        {
          "tags": [
            "third-party-advisory"
          ],
          "url": "https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5"
        },
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://neo4j.com/security/CVE-2026-19869"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eUpgrade the library to\u0026nbsp;\u003ccode\u003e7.6.0\u003c/code\u003e+ or\u0026nbsp;\u003ccode\u003e5.12.15\u003c/code\u003e+. v6 is end-of-life and will not receive a fix. v5 releases prior to\u0026nbsp;\u003ccode\u003e5.2.0\u003c/code\u003e\u0026nbsp;are not affected.\u003c/p\u003e\u003cp\u003eFor users who cannot upgrade immediately: do not combine a type-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;with a field-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;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\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;directive to each root field individually, including the full stricter rule on the sensitive field. Alternatively, enforce the stricter requirement inside the custom resolver\u0027s own code.\u003c/p\u003e"
            }
          ],
          "value": "Upgrade the library to\u00a07.6.0+ 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\u0027s own code."
        }
      ],
      "source": {
        "discovery": "INTERNAL"
      },
      "title": "Privilege Escalation via Dropped Field-Level @authentication",
      "x_generator": {
        "engine": "Vulnogram 1.0.4"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "3b236295-4ccd-4a1f-a1c1-a72eecc8d7b6",
    "assignerShortName": "Neo4j",
    "cveId": "CVE-2026-19869",
    "datePublished": "2026-08-18T16:35:19.878Z",
    "dateReserved": "2026-08-14T11:22:26.042Z",
    "dateUpdated": "2026-08-19T16:02:04.528Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "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\u0027s own code.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cp\u003eUpgrade the library to\u0026nbsp;\u003ccode\u003e7.5.7\u003c/code\u003e+ or\u0026nbsp;\u003ccode\u003e5.12.15\u003c/code\u003e+. v6 is end-of-life and will not receive a fix. v5 releases prior to\u0026nbsp;\u003ccode\u003e5.2.0\u003c/code\u003e\u0026nbsp;are not affected.\u003c/p\u003e\u003cp\u003eFor users who cannot upgrade immediately: do not combine a type-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;with a field-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;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\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;directive to each root field individually, including the full stricter rule on the sensitive field. Alternatively, enforce the stricter requirement inside the custom resolver\u0027s own code.\u003c/p\u003e\", \"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\": \"\u003ccode\u003e@neo4j/graphql\u003c/code\u003e\u0026nbsp;from\u0026nbsp;\u003ccode\u003e5.2.0\u003c/code\u003e\u0026nbsp;until the patched versions fails to enforce field-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;rules on root custom-resolver fields when a type-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;rule is also present on the same operation type. When both a type-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;(on\u0026nbsp;\u003ccode\u003eQuery\u003c/code\u003e/\u003ccode\u003eMutation\u003c/code\u003e) and a field-level\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;(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 (\u003ccode\u003ejwt: { roles_INCLUDES: \\\"admin\\\" }\u003c/code\u003e) \\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.\u0026nbsp;\u003ccode\u003eroles: [\\\"user\\\"]\u003c/code\u003e) 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\": \"\u003cp\u003eThe application enables\u0026nbsp;\u003ccode\u003efeatures.authorization\u003c/code\u003e\u0026nbsp;and defines a root operation type (\u003ccode\u003eQuery\u003c/code\u003e/\u003ccode\u003eMutation\u003c/code\u003e) annotated with\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;that also contains one or more custom-resolver fields carrying their own, stricter\u0026nbsp;\u003ccode\u003e@authentication\u003c/code\u003e\u0026nbsp;rule.\u003c/p\u003e\", \"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\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.


Loading…

Loading…