# CVE-2026-77850: Stored XSS in AshAdmin relationship typeahead via unescaped label_field content

> Stored XSS in AshAdmin allows attackers to execute scripts in admin browsers via unescaped label fields, leading to privilege escalation.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** EEF-CVE-2026-77850, GHSA-m23x-576h-73w8

## What is CVE-2026-77850?

CVE-2026-77850 is a high-severity cross-site scripting vulnerability in ash-project ash_admin, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Stored Cross-site Scripting vulnerability in ash-project ash_admin executes attacker-supplied record content as script in an administrator's browser.

The relationship typeahead components AshAdmin.Components.Resource.RelationshipField and AshAdmin.Components.Resource.ManagedRelationshipSelectField highlight the matched search term by wrapping it in <b> tags and rendering the whole string with Phoenix.HTML.raw/1. The highlighted value is the destination record's label_field, ordinary database content that is often written by lower-privileged users. Because raw/1 disables output escaping for the entire string, a stored label such as <img src=x onerror=...> runs as JavaScript in the admin's session as soon as a matching record appears in the dropdown, giving the attacker the admin's privileges over everything AshAdmin exposes. The fix HTML-escapes the label before inserting the highlight markup.

This issue affects ash_admin: from 0.13.0 before 1.3.1.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-77850?

1 open source package ship an affected version, including ash_admin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash_admin` | Hex | From 0.13.0 | 1.3.1 |

## How do I fix CVE-2026-77850?

Upgrade ash_admin to 1.3.1 or later.

## Is CVE-2026-77850 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77850 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-77850 and fix it if it is affected.

What it is: CVE-2026-77850 is a high-severity cross-site scripting vulnerability in ash-project ash_admin, published on 31 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-77850 exists.

Affected packages and fixed versions:
- ash_admin (Hex): affected from 0.13.0; fixed in 1.3.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-77850/ (Markdown: https://insights.sbomify.com/CVE-2026-77850/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-77850
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-77850
- OSV: https://osv.dev/vulnerability/CVE-2026-77850

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-77850/
Summaries are generated and may contain mistakes; the official description above is the record.
