CVE-2026-49249

What it is

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[<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 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.

At a glance

Exploitability

Can be exploited over the network with a low-privilege account. High risk of service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-09-02 18:19 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-09-09 21:04 UTC Last updatedMost recent change to the record

Details

Published

2026-09-02 18:19 UTC

Last modified

2026-09-09 21:04 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-400 · Uncontrolled resource consumption

Record status

Deferred

Attack profile CVSS 4.0 · 7.1

Attack vector

Network

Complexity

Low

Attack requirements

None

Privileges needed

Low

User interaction

None

Confidentiality

None

Integrity

None

Availability

High