Quick answers
- Is CVE-2026-82681 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82681 being exploited in the wild.
- How severe is CVE-2026-82681?
- Informational severity, published 31 August 2026.
- Which products and versions are affected?
- Ash-Project Ash Admin 0.3.0-rc.0 before 1.3.1.
- Is there a fix for CVE-2026-82681?
- A patch was published on 2026-08-31: ash_admin 1.3.1 and later include the fix with URI.encode_query/1 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82681 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-82681?
- Check whether you run Ash-Project Ash Admin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Table, DataTable, and Show components in ash_admin construct row-action URLs using raw string interpolation without URL-encoding the primary key and other interpolated values. Because Elixir/Phoenix's Plug.Conn.Query resolver uses a "last-wins" strategy for duplicate query parameters and the primary_key is interpolated last, a malicious string primary key (e.g., "foo&action_type=destroy") can inject parameters that override the intended link target. Additionally, a "#" character in the key truncates the query into a fragment. The fix implements proper URL encoding using URI.encode_query/1 for all interpolated values. Network reachable; requires ability to control a record's primary key (common in slugs, emails, or user-settable identifiers). An attacker can redirect admin actions to arbitrary targets or operations.
Affected products
- ash-project ash_admin 0.3.0-rc.0 before 1.3.1
Timeline
- 2026-08-31: disclosed
- 2026-08-31: patched: ash_admin 1.3.1 and later include the fix with URI.encode_query/1