{
  "id": "CVE-2026-19869",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-19869",
  "published_at": "2026-08-18T16:35:19.878Z",
  "title": "Privilege Escalation via Dropped Field-Level @authentication",
  "vendor": "neo4j",
  "product": "graphql",
  "cvss": {
    "score": 7.6,
    "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"
  },
  "kev": {
    "in_kev": false,
    "added_at": null,
    "days_after_publication": null
  },
  "first_poc": null,
  "poc_repo_count": 0,
  "exploit_count": 0,
  "suspicious_repo_count": 0,
  "edge_device": null,
  "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.",
  "cwe": "CWE-639",
  "cvss_by_source": {
    "cna": 7.6
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "neo4j",
        "product": "graphql",
        "ranges": [
          "\u003e= 7.0.0, \u003c 7.6.0",
          "\u003e= 5.2.0, \u003c 5.12.15",
          "\u003e= 6.0.0, \u003c= 6.6.4"
        ],
        "fixed_in": [
          "7.6.0",
          "5.12.15"
        ]
      }
    ],
    "solutions": [
      "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."
    ],
    "upgrade": [
      "Upgrade graphql to 7.6.0 or 5.12.15 or later."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://github.com/neo4j/graphql/security/advisories/GHSA-82m8-p9px-c3x5"
      },
      {
        "kind": "Vendor advisory",
        "url": "https://neo4j.com/security/CVE-2026-19869"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
