CVE-2026-33286

An arbitrary method execution vulnerability has been found which affects Graphiti's JSONAPI write functionality. An attacker can craft a malicious JSONAPI payload with arbitrary relationship names to invoke any public method on the underlying model instance, class or its associations.

Workarounds

If upgrading to v1.10.2 is not immediately possible, consider one or more of the following mitigations:

• Restrict write access: Ensure Graphiti write endpoints (create/update/delete) are not accessible to untrusted users.
• Authentication & authorisation: Apply strong authentication and authorisation checks before any write operation is processed, for example use Rails strong parameters to ensure only valid parameters are processed.

Any application exposing Graphiti write endpoints (create/update/delete) to untrusted users is affected.

The Graphiti::Util::ValidationResponse#all_valid? method recursively calls model.send(name) using relationship names taken directly from user-supplied JSONAPI payloads, without validating them against the resource's configured sideloads. This allows an attacker to potentially run any public method on a given model instance, on the instance class or associated instances or classes, including destructive operations.

CVE-2026-33286 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.10.2); upgrading removes the vulnerable code path.

Kodem intelligence

This is patched in Graphiti v1.10.2. Users should upgrade as soon as possible.

1. What is CVE-2026-33286? CVE-2026-33286 is a critical-severity security vulnerability in graphiti (rubygems), affecting versions <= 1.10.1. It is fixed in 1.10.2.
2. How severe is CVE-2026-33286? CVE-2026-33286 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of graphiti are affected by CVE-2026-33286? graphiti (rubygems) versions <= 1.10.1 is affected.
4. Is there a fix for CVE-2026-33286? Yes. CVE-2026-33286 is fixed in 1.10.2. Upgrade to this version or later.
5. Is CVE-2026-33286 exploitable, and should I be worried? Whether CVE-2026-33286 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-33286 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-33286? Upgrade graphiti to 1.10.2 or later.