Not a U.S. government website. NDD is an independent vulnerability database by Volerion and is not affiliated with or endorsed by NIST or NVD.
VOLERION
Volerion Security Research

NOT DEFERRED DATABASE

VULNERABILITIES

CVE-2026-82760 Details

ANALYZED


This CVE record has been analyzed and enriched by NVDAPI.com as an independent party.

Description

Inefficient Algorithmic Complexity vulnerability in team-alembic AshAuthentication allows an unauthenticated attacker to exhaust CPU and memory via an oversized base62 segment in a submitted API key. AshAuthentication.Base.decode62/1 in lib/ash_authentication/base.ex splits its argument into one binary per character and folds it with charval62/2, which recomputes Integer.pow(62, index) at every position instead of accumulating by Horner's method, so cost grows roughly cubically in the input length. bindecode62/1 in the same module is quadratic through Integer.undigits/2 and Integer.digits/2. Neither function caps byte_size/1, and AshAuthentication.Strategy.ApiKey.SignInPreparation passes the underscore-separated segments of the submitted key straight into both, before any key lookup and without prior authentication. The surrounding rescue clauses catch exceptions, not CPU or memory exhaustion. This issue affects ash_authentication: from 4.8.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Metrics

CVSS 3.x Severity and Vector Strings:

References to Advisories, Solutions, and Tools

By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.

Weakness Enumeration

CWE-IDCWE NameSource
CWE-407Inefficient Algorithmic ComplexityEEF

Affected Products

ProductVersions
team-alembic AshAuthentication
>= 4.8.0, < 4.15.0 (semver)
>= 5.0.0-rc.0, < 5.0.0-rc.14 (semver)

CPE

  • No CPEs found in CPE dictionary for this product.

Remediation

  • Upgrade: 4.15.0moderate effort
  • Upgrade: 5.0.0-rc.14moderate effort
  • Mitigation:low effort

    Cap the length of the API key at a proxy, load balancer, or WAF. A legitimate key is under about 80 characters; anything longer can be rejected outright.

  • Mitigation:low effort

    Check whether your application exposes API key sign-in through a request body (e.g., a custom controller, AshJsonApi, or AshGraphql). If it does, you are in a vulnerable configuration and should restrict the action to the header-based plug, which restores the transport bound.

Change History

2 change records found show changes


QUICK INFO

CVE Dictionary Entry:
CVE-2026-82760
NVD Published Date:
Sep 17, 2026
NVD Last Modified:
Sep 18, 2026
Source:
EEF
CVE-2026-82760 Details - Not Deferred