ZeroHour

CVE-2026-49249

niche

Denial of Service via BEAM Atom Table Exhaustion in Boruta (pre-0.10.0)

CVSS 4.0
7.1 high
EPSS
<1%p14
Published
()
Modified
AI analysis

CVE-2026-49249 is an uncontrolled resource consumption flaw (CWE-400/CWE-770) in Boruta, a standalone open-source authorization server implementing OAuth 2.0 and OpenID Connect: before version 0.10.0, BorutaIdentityWeb.UserSettingsController.update/2 converts every key of the user-supplied request body to an atom via String.to_atom/1, which permanently interns atoms in the Erlang VM's global atom table (default cap 1,048,576 atoms). Any authenticated end user can trigger it by repeatedly sending PUT /users/settings with fresh user[<key>]=... parameters; keys are atomized before validation, so even updates that fail downstream still consume table entries, and the only protections are authentication plus a per-IP rate limit of 10 requests/second. The impact is total denial of service with no confidentiality or integrity loss: once the table fills, the BEAM aborts with 'no more index entries in atom_tab' and crashes the entire umbrella application, including the auth, admin, and gateway apps. Only Boruta deployments running versions prior to 0.10.0 that expose the user settings endpoint to logged-in end users are affected. No public proof-of-concept or in-the-wild exploitation is known; EPSS estimates a 0.2% probability of exploitation in the next 30 days, and the issue is not in CISA KEV.

What to do: Upgrade Boruta to version 0.10.0 or later, which stops permanently interning user-supplied keys. Until you can upgrade, restrict PUT /users/settings to trusted accounts and tighten rate limiting or filter/reject requests with large numbers of user[...] parameter keys at a reverse proxy, since the default 10 req/s per-IP limit only delays exhaustion; monitoring the BEAM atom count (e.g., via erlang:system_info(atom_count) and the ERL_MAX_ATOMS cap) and restarting the node can serve as a stopgap. Given no known exploitation, treat this as a routine priority patch.

Affected
Boruta (open-source project) Boruta standalone OAuth 2.0 / OpenID Connect authorization server (BorutaIdentity UserSettingsController)all versions prior to 0.10.0 (patched in 0.10.0)
Estimated exposure
nichelikely tens to a few hundred self-hosted instances (estimate) — Boruta is a niche, self-hosted open-source Elixir authorization server with no published install, download, or internet-exposure counts in the data, so affected deployments are estimated to be far fewer than mainstream identity providers.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

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.to_atom/1 before any validation. Because String.to_atom interns atoms permanently in the BEAM atom table (default cap 1,048,576 atoms; ERL_MAX_ATOMS), any authenticated end user can send PUT /users/settings with a user[ ]=... 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 atom_tab and the entire OIDC server (auth, admin, gateway apps in the umbrella) crashes. The route is protected only by require_authenticated_user 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.update_user/6 call, so even failing updates contribute to exhaustion. This issue has been patched in version 0.10.0.

Weakness
CWE-400, CWE-770
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

In the news

No ingested article mentions this CVE yet.