AIKIDO-2026-458845
guardian is vulnerable to Uncontrolled Resource Consumption
69
Medium Risk
This Affects:
guardianTL;DR
Guardian.Plug.Keys in lib/guardian/plug/keys.ex derives namespace keys by passing arbitrary binaries into String.to_atom with no length, charset, or allow-list check. Higher-level entry points such as Guardian.Plug.current_token thread a caller-supplied key straight into this sink. An application that derives a Guardian key from externally influenced data such as a tenant identifier or request header mints one permanent atom per distinct value, and because the BEAM atom table is fixed in size the node eventually crashes. The fix resolves namespace lookups through String.to_existing_atom and only interns atoms from developer-controlled keys.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and your application derives a Guardian namespace key from externally influenced input such as a tenant identifier or request header.
Background info
guardian is vulnerable to Uncontrolled Resource Consumption in versions 0.1.0 - 2.4.0.
How to fix this
Upgrade the guardian library to the patch version.
Links
GitHub Release
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant