VDB
Sign up

EEF-CVE-2026-82753

Unauthenticated authorize requests create unbounded, never-expiring CIMD client rows and cache entries in ash_authentication_oauth2_server

Quick fix

EEF-CVE-2026-82753 — ash_authentication_oauth2_server: upgrade to the fixed version with the command below.

mix deps.update ash_authentication_oauth2_server

Details

## Summary

Allocation of Resources Without Limits or Throttling vulnerability in ash-project ash\_authentication\_oauth2\_server allows an unauthenticated attacker to exhaust database storage and memory.

The /authorize endpoint is unauthenticated by design. With Client ID Metadata Documents enabled, resolve\_client/3 in AshAuthentication.Oauth2Server.CIMD fetches the document for each new URL-shaped client\_id and upserts a client row, with no cap on the number of rows, no expiry or garbage collection, and no length bound on the fetched fields; the document was also placed in CIMD.Cache before validation, so even rejected documents held cache memory until their TTL. An attacker serving valid documents at many distinct URLs creates one permanent client row per URL, each able to carry multi-megabyte strings, growing storage and memory without bound.

This issue affects ash\_authentication\_oauth2\_server: from 0.3.0 before 0.3.1.

## Configuration

Reachable only when the client resource has Client ID Metadata Documents enabled (cimd\_enabled?: true) and the authorize endpoint is exposed. CIMD is off by default.

Are you affected?

Enter the version of the package you're using.

Affected packages

Hex/ash_authentication_oauth2_server
Introduced in: 0.3.0Fixed in: 0.3.1
Fixmix deps.update ash_authentication_oauth2_server

References