---
id: CVE-2026-49249
title: >-
  Boruta is a standalone authorization server that aims to implement OAuth 2.0
  and Openid Connect up to decentralized identity specifications
summary: >-
  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…
severity: high
cvss: 7.1
cvssVector: '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'
cwe:
  - CWE-400
  - CWE-770
vendor: malach-it
product: boruta-server
affected:
  - boruta-server < 0.10.0
published: '2026-09-02'
updated: '2026-09-09'
sourceUpdated: '2026-09-09T21:04:42.813'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-49249'
references:
  - url: 'https://github.com/malach-it/boruta-server/releases/tag/0.10.0'
    label: security-advisories@github.com
  - url: >-
      https://github.com/malach-it/boruta-server/security/advisories/GHSA-q428-ch8m-94gg
    label: security-advisories@github.com
  - url: >-
      https://github.com/malach-it/boruta-server/security/advisories/GHSA-q428-ch8m-94gg
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2026-09-02T19:12:21.807756Z'
cvssSource: cna
ingestedAt: '2026-09-13T09:45:18.855Z'
epss: 0.00397
epssPercentile: 0.31188
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.