Skip to content
major vulnerability· requires attention

Authenticated RCE in Microsoft Power BI (widely used enterprise product) with high CVSS likely to impact many organizations.

Applications

CVE-2026-65811

8.8
High
EPSS 0.53%Patch availableAug 12, 2026

Authenticated remote code execution in Microsoft Power BI via improper input validation.

common questions

Is CVE-2026-65811 being exploited?

Not confirmed. CVE-2026-65811 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.53% probability of exploitation in the next 30 days.

How severe is CVE-2026-65811?

CVE-2026-65811 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-65811?

Yes. A fix has been recorded for CVE-2026-65811. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-65811 affect?

CVE-2026-65811 affects Microsoft Power BI. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-65811?

Apply vendor patch when released; restrict Power BI network access and monitor logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Microsoft Power BI
impact

Authenticated remote code execution over network; attacker can run arbitrary code, access/exfiltrate data, deploy malware, and pivot.

action required

Immediate action required

affected versions
Microsoft Power BI Report Server
  • affected>= 1.6.0 and < 1.26.9682.1442

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free