Skip to content
Web

CVE-2026-77850

8.4
High
EPSS 0.28%Patch availableSep 1, 2026

Stored XSS in ash_admin typeahead can execute attacker-supplied labels in admin UI.

common questions

Is CVE-2026-77850 being exploited?

Not confirmed. CVE-2026-77850 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.28% probability of exploitation in the next 30 days.

How severe is CVE-2026-77850?

CVE-2026-77850 is rated High with a CVSS score of 8.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-77850?

Yes. A fix has been recorded for CVE-2026-77850. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-77850 affect?

CVE-2026-77850 affects ash-project/ash_admin >=0.13.0 and <1.3.1. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-77850?

Upgrade ash_admin to >=1.3.1 and sanitize/escape user-editable labels; restrict who can edit records.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ash-project/ash_admin >=0.13.0 and <1.3.1
impact

Stored XSS executes attacker-supplied record labels in admin browsers, enabling admin session takeover and full access to AshAdmin-exposed functions.

action required

Immediate action required

affected versions
ash-project ash_admin
  • affected>= 0.13.0 and < 1.3.1
  • affected>= eb940f4d7d857ca49368ae847f586d01c6f5ad35 and < 07289191ccdac27dd70ab7c6413ed057bc7fdade

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free