Improper Control of Dynamically-Managed Code Resources Affecting graphiti package, versions <1.10.2
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-RUBY-GRAPHITI-15812219
- published29 Mar 2026
- disclosed24 Mar 2026
- creditdoublevoid
Introduced: 24 Mar 2026
NewCVE-2026-33286 (opens in a new tab)How to fix?
Upgrade graphiti to version 1.10.2 or higher.
Overview
graphiti is an Easily build jsonapi.org-compatible APIs
Affected versions of this package are vulnerable to Improper Control of Dynamically-Managed Code Resources via the Graphiti::Util::ValidationResponse#all_valid? method recursively calls model.send(name). An attacker can execute arbitrary public methods on model instances, classes, or their associations by supplying crafted relationship names in a JSONAPI payload. This can result in destructive operations or unauthorized actions.
Note: This is only exploitable if write endpoints are exposed to untrusted users without sufficient authentication or authorization checks.
Workaround
This vulnerability can be mitigated by restricting access to write endpoints to trusted users only and applying strong authentication and authorization checks, such as using Rails strong parameters to validate input.