dbcve.org
Telerik Report ServerApplication · Progress

CVE-2025-0556

MEDIUM · 6.5 CVSS v3.1 Published 2025-02-12
Fix available
A fix is available. Upgrade to 11.0.25.211 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In Progress® Telerik® Report Server, versions prior to 2025 Q1 (11.0.25.211) when using the older .NET Framework implementation, communication of non-sensitive information between the service agent process and app host process occurs over an unencrypted tunnel, which can be subjected to local network traffic sniffing.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Progress Telerik Report Server versions prior to 2025 Q1 (11.0.25.211), the older .NET Framework implementation uses an unencrypted tunnel for communication between the service agent process and app host process. This allows an attacker with local network access to sniff non-sensitive traffic traveling between these two processes.

MitigationUpgrade to Telerik Report Server version 2025 Q1 (11.0.25.211) or later which implements encrypted communication between the service agent and app host processes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Telerik Report ServerApplication
Affected:< 11.0.25.211

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Telerik Report Server installation
    Locate the Report Server installation directory, typically under C:\Program Files\Telerik\Report Server or check Windows Programs and Features for 'Telerik Report Server'
    Affected if Telerik Report Server is installed on the system
  2. Determine installed version
    Open Windows Programs and Features, find Telerik Report Server, and note the version column, or check the About page in the Report Server web interface
    Affected if Version is lower than 11.0.25.211 (or 2025 Q1 release)
  3. Verify .NET Framework implementation is in use
    Check which implementation the Report Server is configured to use - the vulnerability affects the .NET Framework implementation, not .NET Core. Inspect the running processes or configuration files in the installation directory to identify the active implementation.
    Affected if The .NET Framework implementation is in use (vulnerability applies only to .NET Framework builds)
  4. Check network accessibility
    Verify if the Report Server is accessible on the local network or if untrusted users have local network access to the machine
    Affected if Untrusted users can access the local network segment where Report Server traffic travels

You are affected if Telerik Report Server is installed with a version lower than 11.0.25.211 and uses the .NET Framework implementation, allowing local network attackers to sniff inter-process communication traffic.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 11.0.25.211 or later
Fixed in 11.0.25.211
Interim mitigation

Upgrade to Telerik Report Server version 2025 Q1 (11.0.25.211) or later which implements encrypted communication between the service agent and app host processes.

Recommended fix High confidence

Telerik Report Server 11.0.25.211 (2025 Q1)

  1. Back up your current Telerik Report Server installation and database
  2. Download Telerik Report Server version 11.0.25.211 (2025 Q1) or later from the official Telerik website
  3. Review the official Telerik upgrade documentation at docs.telerik.com for version-specific upgrade instructions
  4. Execute the upgrade installer following the documented upgrade procedure
  5. After upgrade, verify the service agent to app host communication is now encrypted
  6. Confirm the Report Server is functioning correctly post-upgrade
Caveat Review release notes for any configuration or feature changes between your current version and 11.0.25.211

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Telerik Report Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-0556 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-0556 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data