CVE-2026-82753

8.2

ash-project · ash_authentication_oauth2_server

An unauthenticated resource exhaustion vulnerability in ash_authentication_oauth2_server allows attackers to consume excessive database storage and memory via the /authorize endpoint.

Executive summary

An unauthenticated resource exhaustion vulnerability in ash_authentication_oauth2_server poses a high risk of service denial by allowing attackers to overwhelm database and memory resources.

Vulnerability

This is an allocation of resources without limits or throttling (CWE-770) issue within the resolve_client/3 function. Unauthenticated attackers can trigger the storage of unbounded, unvalidated metadata documents by providing distinct URL-based client IDs, leading to uncontrolled memory and storage growth.

Business impact

The vulnerability carries a CVSS score of 8.2, classifying it as high severity. Successful exploitation could lead to a complete denial of service for the authentication server, preventing legitimate users from accessing protected resources and potentially causing cascading failures in dependent systems due to resource exhaustion.

Remediation

Immediate Action: Upgrade to version 0.3.1 or later to implement necessary caching limits and validation constraints for client metadata documents.

Proactive Monitoring: Monitor server memory usage and database storage growth patterns for anomalous spikes that correlate with incoming /authorize requests.

Compensating Controls: Deploy a Web Application Firewall or rate-limiting proxy to restrict the frequency of requests to the /authorize endpoint from individual sources while a patch is being scheduled.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

Given the potential for significant service disruption, organizations running versions of ash_authentication_oauth2_server prior to 0.3.1 should prioritize an immediate update to the patched version. Implementing strict resource constraints is essential to preventing this denial of service vector and ensuring the continued availability of authentication services.

More ash-project CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources

Originally found and disclosed by Peter Ullrich, Peter Ullrich, with Zach Daniel / Ash Project (remediation developer), Jonatan Männchen / EEF (coordinator), per the CVE Program record.