Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82730 – Authorization Bypass / Sensitive Data Exposure – ash_typescript 0.11.0–0.17.x

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82730 is an incorrect authorization vulnerability in ash_typescript, the TypeScript RPC/type-generation library for the Elixir Ash Framework. Attackers can retrieve attribute values that Ash field policies were explicitly configured to deny, because the RPC result-serialization path fails to strip an internal "forbidden field" marker before returning data to the caller. The issue carries a CVSS v4.0 base score of 8.2 (High) due to a high-confidentiality impact reachable over the network without authentication or user interaction.

Technical details

  • Root cause: When Ash’s field policies deny access to an attribute, Ash replaces the value with an %Ash.ForbiddenField{} struct that still internally retains the real value in an original_value field. The normalize_primitive/1 function in lib/ash_typescript/rpc/result_processor.ex had no dedicated clause for this struct type, so it fell through to a generic struct-handling branch that called Map.from_struct/1 and serialized all of the struct’s keys — including original_value — into the JSON RPC response.
  • Trigger conditions: An application must expose AshTypescript-generated RPC endpoints over HTTP and rely on Ash field policies to hide attribute values (including on embedded resources) rather than removing them from the response entirely.
  • Attack vector: Network — any RPC caller permitted to invoke the affected endpoint, including unauthorized or low-privilege callers, can obtain field values they should not be able to see, since no additional privileges or user interaction are required.
  • Impact: High confidentiality impact (disclosure of policy-protected attribute values); no direct impact on integrity or availability.

Affected software

  • ash_typescript (ash-project) versions >= 0.11.0 and < 0.18.0
  • Any deployment built from commits prior to the fix commit aa7f9f1967b0bec806ac1156142267e805d70a55

Severity

  • CVSS v4.0 Base Score: 8.2 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade ash_typescript to version 0.18.0 or later, which adds explicit normalize_primitive/1 clauses that return nil for Ash.ForbiddenField and Ash.NotLoaded values instead of serializing them.
  • If immediate patching is not possible:
    • Audit RPC endpoints generated by ash_typescript that expose resources (especially embedded resources) protected by Ash field policies, and restrict or disable access to those endpoints until patched.
    • Review server logs/response payloads for evidence of original_value or other unexpected struct keys appearing in RPC responses, which would indicate the marker was leaking.
    • Where feasible, apply an output-filtering proxy or serializer to strip any unexpected struct fields (e.g., original_value) from RPC JSON responses as a temporary compensating control.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge