{
  "id": "CVE-2026-76763",
  "url": "https://poc.griffinguard.io/cve/CVE-2026-76763",
  "published_at": "2026-08-31T13:54:18.49Z",
  "title": "Io.smallrye/smallrye-graphql: smallrye graphql: unauthenticated denial of service via large exponent float literals",
  "vendor": "Red Hat",
  "product": "Red Hat build of Quarkus 3.27.5.SP1",
  "cvss": {
    "score": 7.5,
    "source": "cna",
    "vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  },
  "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": "A flaw was found in SmallRye GraphQL. The number scalar coercion for BigInteger does not properly validate the magnitude of float or string inputs. An unauthenticated remote attacker can exploit this by sending a GraphQL query containing a large exponent float literal. This can lead to the allocation of extremely large BigInteger objects, causing CPU exhaustion or an OutOfMemoryError, resulting in a denial of service.",
  "cwe": "CWE-1284",
  "cvss_by_source": {
    "cna": 7.5
  },
  "repos": [],
  "remediation": {
    "affected": [
      {
        "vendor": "Red Hat",
        "product": "Red Hat build of Quarkus 3.27.5.SP1",
        "ranges": null,
        "fixed_in": [
          "2.14.2.redhat-00002"
        ]
      },
      {
        "vendor": "Red Hat",
        "product": "Red Hat build of Quarkus 3.33.3.SP1",
        "ranges": null,
        "fixed_in": [
          "2.17.0.redhat-00003"
        ]
      }
    ],
    "upgrade": [
      "Upgrade Red Hat build of Quarkus 3.27.5.SP1 to 2.14.2.redhat-00002 or later.",
      "Upgrade Red Hat build of Quarkus 3.33.3.SP1 to 2.17.0.redhat-00003 or later."
    ],
    "workarounds": [
      "To mitigate this issue, applications exposing SmallRye GraphQL endpoints should implement validation and bounding of the precision or exponent for incoming numeric literals before they reach scalar coercion. Additionally, limiting the JVM heap size can help constrain the impact of OutOfMemoryError, though it will not prevent CPU exhaustion. Implementing rate-limiting or timeouts on the GraphQL endpoint can also reduce exposure. Using GraphQL variables instead of inline literals for numeric inputs is a safe alternative, as variables follow a secure parsing path."
    ],
    "references": [
      {
        "kind": "Vendor advisory",
        "url": "https://access.redhat.com/errata/RHSA-2026:62515"
      },
      {
        "kind": "Vendor advisory",
        "url": "https://access.redhat.com/errata/RHSA-2026:62555"
      }
    ]
  },
  "exploit_refs": [],
  "hunt_profile": [],
  "rules": []
}
