# CVE-2026-106133: Incorrect Authorization in Telerik Report Server Web Report Designer

Status: published. Published: 2026-11-11. Updated: 2026-11-11.

In Progress® Telerik® Report Server prior to version 12.3.26.1110, an incorrect authorization vulnerability in the Web Report Designer allows an authenticated attacker with low privileges to perform unauthorized operations on shared report resources, affecting their integrity and availability.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Progress Software / Telerik Report Server: ≥ 0; < 12.3.26.1110 (affected, custom). Source: CNA: ProgressSoftware

## Severity and prioritization

- CVSS 3.1: 6.3 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L; source: CNA: ProgressSoftware

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-863

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.telerik.com/report-server/documentation/knowledge-base/kb-security-incorrect-authorization-cve-2026-106133 (CNA: ProgressSoftware; vendor-advisory)

## Provenance

- CNA: ProgressSoftware: https://www.cve.org/CVERecord?id=CVE-2026-106133; retrieved 2026-11-11; source updated 2026-11-11

Revision: 6778a8edd71c3edfbcf136c2642afaaa54916fd62b86c2a8aedce68c407925a6

Canonical: https://y2.dev/cve/CVE-2026-106133

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.