Boruta is a standalone authorization server that aims to implement OAuth 2.0 and Openid Connect up to decentralized identity specifications. Prior to version 0.10.0, BorutaIdentityWeb.UserSettingsController.update/2 atomizes every key of the user-supplied request body via String.toatom/1 before any validation. Because String.toatom interns atoms permanently in the BEAM atom table (default cap 1,048,576 atoms; ERLMAXATOMS), any authenticated end user can send PUT /users/settings with a user[<fresh-key>]=... body containing fresh keys per request and exhaust the global VM atom table. Once the table is full, the BEAM aborts with no more index entries in atomtab and the entire OIDC server (auth, admin, gateway apps in the umbrella) crashes. The route is protected only by requireauthenticateduser and a per-IP rate limit of 10 requests/second; a logged-in end user can hit it. The keys are atomized unconditionally before the downstream Accounts.updateuser/6 call, so even failing updates contribute to exhaustion. This issue has been patched in version 0.10.0.
{
"cwe_ids": [
"CWE-400",
"CWE-770"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/49xxx/CVE-2026-49249.json",
"cna_assigner": "GitHub_M"
}