CVE
External Control of Configuration Setting in Telerik Report Server
- Exploited
- No known exploitation
- Fix
- Fixed in 12.3.26.1110
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Affects Telerik Report Server versions before 12.3.26.1110; embedded Telerik Reporting is not affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Progress Software's Telerik Report Server contains a flaw in which an unauthenticated attacker over the network can change the server address the software uses when generating links and notifications. If a user interacts with the crafted link or notification, the attacker can gain access to sensitive information and take over the account.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
In Progress® Telerik® Report Server prior to version 12.3.26.1110, an external control of a system configuration setting vulnerability allows an unauthenticated remote attacker to influence the server address used by Report Server when generating links and notifications. With user interaction, this can lead to disclosure of sensitive information and account takeover.
Who should check
Teams running Progress Telerik Report Server before 12.3.26.1110 (not embedded Telerik Reporting).
Read the source excerpt
“Progress® Telerik® Report Server versions >= 0 and < 12.3.26.1110 .”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Affects Telerik Report Server versions before 12.3.26.1110; embedded Telerik Reporting is not affected.Upgrade to a fixed version: 12.3.26.1110.
Workaround: Administrators should verify that the Server URL in the Report Server configuration contains the correct public address of the server and set it explicitly if necessary.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-106152 (External Control of Configuration Setting in Telerik Report Server), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-106152 (entry last updated 2026-11-11):
Affected:
- Progress Software Telerik Report Server: fixed in 12.3.26.1110
Fixed versions: 12.3.26.1110.
Conditions (all must be true for the bug to be hit):
- Affects Telerik Report Server versions before 12.3.26.1110; embedded Telerik Reporting is not affected. (source: https://www.telerik.com/report-server/documentation/knowledge-base/kb-security-external-control-of-system-or-configuration-setting-cve-2026-106152)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
Workaround: Administrators should verify that the Server URL in the Report Server configuration contains the correct public address of the server and set it explicitly if necessary. (source: https://www.telerik.com/report-server/documentation/knowledge-base/kb-security-external-control-of-system-or-configuration-setting-cve-2026-106152)
CISA KEV: CVE-2026-106152 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-106152 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.telerik.com/report-server/documentation/knowledge-base/kb-security-external-control-of-system-or-configuration-setting-cve-2026-106152
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-106152
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-106152"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- Progress Software Telerik Report Server
fixed in 12.3.26.1110
Evidence 3
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-106152
Is CVE-2026-106152 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets a attacker-influenced server address be used when Telerik Report Server generates links and notifications. With user interaction, this can lead to disclosure of sensitive information and account takeover.Source: telerik.com
Which versions are affected by CVE-2026-106152?
Telerik Report Server: before 12.3.26.1110.Source: cve.now feed data
Am I affected, and how do I check?
Telerik Report Server versions before 12.3.26.1110 are affected. Embedded Telerik Reporting is not affected. To check a deployment, look at the Report Server version and at the Server URL setting in its configuration.Source: telerik.com
How do I fix CVE-2026-106152?
Upgrade Telerik Report Server to version 12.3.26.1110 or later, which contains the fix. Until then, verify that the Server URL in the Report Server configuration contains the correct public address of the server and set it explicitly if necessary.Source: telerik.com