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

New CVE Detected

CVE-2026-13189 – SSRF via Path Traversal in Spell Check Handler – Telerik UI for ASP.NET AJAX pri…

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

Summary

CVE-2026-13189 is a high-severity Server-Side Request Forgery (SSRF) vulnerability in Progress Telerik UI for ASP.NET AJAX, affecting all versions from 2011.2.712 through 2026.2.519 (prior to v2026.2.708). The flaw resides in the spell check handler’s DictionaryLanguage parameter, which lacks sufficient input validation, enabling unauthenticated remote attackers to influence server-side file path resolution and trigger unintended server-side network requests. With a CVSS v3.1 score of 7.5 (High) and no authentication or user interaction required, this vulnerability poses significant risk to any internet-exposed deployment.

Technical details

  • Root cause: Insufficient validation of the DictionaryLanguage (language) parameter in the RadSpell spell check HTTP handler (CWE-36: Absolute Path Traversal). The handler resolves file paths on the server based on the attacker-supplied language value without adequately sanitizing or restricting the input.
  • Trigger conditions: An attacker sends a crafted HTTP request to the spell check handler containing a manipulated language parameter. No authentication, privileges, or user interaction are required.
  • Attack vector: Remotely exploitable over the network (AV:N) with low attack complexity (AC:L), no privileges required (PR:N), and no user interaction (UI:N).
  • Impact: Successful exploitation allows the attacker to influence server-side file path resolution and initiate unintended server-side requests (SSRF), resulting in high confidentiality impact (C:H). Integrity and availability are not affected (I:N / A:N).

Affected software

  • Progress Telerik UI for ASP.NET AJAX — all versions from 2011.2.712 through 2026.2.519 (all releases prior to v2026.2.708)

Severity

  • CVSS v3.1 Base Score: 7.5 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: Upgrade to Progress Telerik UI for ASP.NET AJAX v2026.2.708 (2026 Q2 SP1) or later, which contains the vendor-supplied fix for this vulnerability.
  • If immediate patching is not feasible, consider restricting network-level access to the spell check handler endpoint and applying web application firewall (WAF) rules to filter requests containing unsanitized language parameter values.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge