CVE-2026-82730
Authorization bypass in ash_typescript leaks denied field values via RPC.
Is CVE-2026-82730 being exploited?
Not confirmed. CVE-2026-82730 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-82730?
CVE-2026-82730 is rated High with a CVSS score of 8.2. 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-82730?
Yes. A fix has been recorded for CVE-2026-82730. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82730 affect?
CVE-2026-82730 affects ash_typescript 0.11.0 - before 0.18.0, Applications using Ash framework with ash_typescript RPC. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82730?
Upgrade to ash_typescript >=0.18.0; audit RPC endpoints and rotate exposed secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthorized RPC callers can read attribute values denied by field policies, causing sensitive data disclosure via RPC responses.
Immediate action required
- affected>= 0.11.0 and < 0.18.0
- affected>= 9cade7661a01b6e4d940386f482f48d148dbb1e6 and < aa7f9f1967b0bec806ac1156142267e805d70a55
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.