dbcve.org
Power Bi Report ServerApplication · Microsoft

CVE-2026-21229

HIGH · 8.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 15.0.1120.113 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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
Improper input validation in Power BI allows an authorized attacker to execute code over a network.

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 · moderate confidence

This is an improper input validation vulnerability in Microsoft Power BI that allows an authorized attacker to execute arbitrary code remotely over a network. The vulnerability stems from insufficient validation of user-supplied input within the Power BI platform, likely in report processing, DAX queries, or data import functions.

MitigationApply Microsoft security updates for Power BI when available; restrict Power BI access to trusted users and implement network segmentation to limit exposure.

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
Power Bi Report ServerApplication
Affected:< 15.0.1120.113

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 if Power BI Report Server is installed
    Check for the presence of Power BI Report Server on the system. On Windows, look for the installation directory typically at C:\Program Files\Microsoft Power BI Report Server or check Programs and Features for 'Microsoft Power BI Report Server'.
    Affected if Power BI Report Server is installed on the system
  2. Determine the installed Power BI Report Server version
    Open the Power BI Report Server Configuration Manager, go to the 'Version' section, or check the file properties of PBIRS.exe in the installation directory (usually in \PBIRS\ReportServer\bin\). Compare the version number against 15.0.1120.113.
    Affected if The installed version is lower than 15.0.1120.113
  3. Verify if the Report Server web service is accessible
    Open a web browser and navigate to the Report Server URL (typically http://localhost/reports or http://localhost/PBIRS_ReportServer). Confirm the service responds without authentication errors.
    Affected if The Report Server web service is accessible and responds to requests
  4. Confirm authenticated user access to report execution features
    Check if users have permissions to create, modify, or execute reports within Power BI Report Server. Access the Site Settings in the Report Server web portal and review the roles assigned to users or groups.
    Affected if Authenticated users have permissions to execute or create reports in Power BI Report Server

A system is affected if Power BI Report Server is installed with a version lower than 15.0.1120.113 and the report execution feature is accessible to authenticated users.

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 15.0.1120.113 or later
Fixed in 15.0.1120.113
Interim mitigation

Apply Microsoft security updates for Power BI when available; restrict Power BI access to trusted users and implement network segmentation to limit exposure.

Recommended fix High confidence

Power BI Report Server version 15.0.1120.113 or later

  1. Download the latest Power BI Report Server installation from the official Microsoft Download Center
  2. Ensure you have backups of your existing report server databases and configurations
  3. Run the PowerBIReportServer.exe installer on the report server
  4. Follow the installation wizard to complete the upgrade
  5. After upgrading, verify that all reports and data sources are functioning correctly
  6. Confirm the version by checking Help > About Power BI Report Server shows version 15.0.1120.113 or later
Caveat Review release notes for any deprecated features or configuration changes before upgrading

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

Fix this in Power Bi Report Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-21229 — 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-2026-21229 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