Monitor vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
Graphiti: Unvalidated Input Lets Attackers Run Any Function
GHSA-3m5v-4xp5-gjg2
CVE-2026-33286
Summary
An attacker can exploit a security weakness in Graphiti's API to run any function on a database, potentially causing harm. This affects any Graphiti application that allows untrusted users to create, update, or delete data. To fix this, update to the latest version of Graphiti, or limit who can make changes to your database.
What to do
- Update lee richmond graphiti to version 1.10.2.
Affected software
| Vendor | Product | Affected versions | Fix available |
|---|---|---|---|
| lee richmond | graphiti | <= 1.10.1 | 1.10.2 |
Original title
Graphiti is a framework that sits on top of models and exposes them via a JSON:API-compliant interface. Versions prior to 1.10.2 have an arbitrary method execution vulnerability that affects Graphi...
Original description
Graphiti is a framework that sits on top of models and exposes them via a JSON:API-compliant interface. Versions prior to 1.10.2 have an arbitrary method execution vulnerability that 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. 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. This is patched in Graphiti v1.10.2. Users should upgrade as soon as possible. Some workarounds are available. Ensure Graphiti write endpoints (create/update) are not accessible to untrusted users and/or apply strong authentication and authorization checks before any write operation is processed, for example use Rails strong parameters to ensure only valid parameters are processed.
ghsa CVSS3.1
9.1
Vulnerability type
CWE-913
Published: 24 Mar 2026 · Updated: 24 Mar 2026 · First seen: 20 Mar 2026