Cyber Resilience

CVE-2026-13183

Published
22 July 2026
Modified
22 July 2026
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0030 22th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2026-13183 is a high-severity Observable Timing Discrepancy (CWE-208) vulnerability in Telerik (inferred from references). Its CVSS base score is 7.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

In Progress® Telerik® UI for AJAX prior to v2026.2.708, RadAsyncUpload upload metadata processing may leak cryptographic validity through measurable timing differences, enabling remote attackers to recover protected metadata values.

CWE(s)
CWE-208

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
Why these techniques?

Remote timing side-channel leak in web upload component directly enables exploitation of a public-facing application to recover protected values.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-40972Shared CWE-208
CVE-2026-44061Shared CWE-208
CVE-2025-68621Shared CWE-208
CVE-2026-33006Shared CWE-208
CVE-2024-42512Shared CWE-208
CVE-2026-26717Shared CWE-208
CVE-2026-27882Shared CWE-208
CVE-2026-28464Shared CWE-208
CVE-2026-5086Shared CWE-208
CVE-2026-28475Shared CWE-208

Affected Assets

Telerik
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SC-13 Cryptographic Protection
  • SI-2 Flaw Remediation
Detect
Catch it (NIST detect / respond)
  • SI-4 System Monitoring
Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V11.2.4

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match
prevent

Mandates cryptographic protection mechanisms that must employ constant-time implementations, directly eliminating the timing side-channel leakage of metadata validity in RadAsyncUpload.

SI-2 Flaw Remediation good match
prevent

Requires timely remediation of identified flaws, directly addressed by upgrading Telerik UI for AJAX to the fixed v2026.2.708 release.

SI-4 System Monitoring partial match
detect

Enables monitoring of system behavior that can identify anomalous timing patterns or repeated upload metadata probes indicative of this attack.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require constant-time implementations that eliminate observable timing discrepancies.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.17 Clock synchronization none match
none

Consistent reference clocks limit the attacker's ability to measure or manipulate timing differences that could reveal internal state or processing paths.

References