What is the CVSS score of CVE-2026-41094?

CVE-2026-41094 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Data Formulator are affected by CVE-2026-41094?

Microsoft Data Formulator versions prior to 0.7 contain a remote code execution vulnerability (CVSS 8.8) that allows unauthenticated attackers to execute arbitrary code if users interact with…. A patch is available.

How to fix or mitigate CVE-2026-41094?

Within 24 hours: Identify all systems running Microsoft Data Formulator versions prior to 0.7 and communicate the vulnerability and patching timeline to affected users and teams. Within 7 days: Test vendor patch (Data Formulator 0.7 or later) in non-production environments, then deploy to all affected systems. Reinforce user awareness regarding risks of opening suspicious or unexpected content in Data Formulator. Within 30 days: Conduct a full inventory verification that all instances have been upgraded to version 0.7 or later, review access logs for any suspicious activity during the pre-patch window, and document the patching completion in change management systems.

Data Formulator CVE-2026-41094

EUVD-2026-29682 HIGH

Code Injection (CWE-94)

2026-05-12 microsoft

GHSA-c824-88px-3j6v

RCE Microsoft Code Injection Microsoft Data Formulator

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

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

ENISA EUVD

HIGH

qualitative

vuln.today AI

8.8 HIGH

Network-reachable unauthenticated code injection (AV:N/AC:L/PR:N) but requires a victim to process attacker content (UI:R), yielding full code-execution impact (C/I/A:H).

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

4.0 AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 23, 2026 - 21:56 vuln.today

CVE Published

May 12, 2026 - 16:58 nvd

HIGH 8.8

DescriptionCVE.org

Improper control of generation of code ('code injection') in Microsoft Data Formulator allows an unauthorized attacker to execute code over a network.

AnalysisAI

Remote code execution in Microsoft Data Formulator versions prior to 0.7 lets an unauthorized attacker run arbitrary code by inducing a user to interact with malicious content (CWE-94 code injection). The flaw is network-reachable and requires no authentication, but does require user interaction (CVSS 3.1 8.8, AV:N/UI:R). A vendor patch is available; there is no public exploit identified at time of analysis and EPSS probability is very low (0.06%).

Technical ContextAI

Data Formulator is Microsoft Research's open-source, AI-assisted data-visualization tool that lets users transform and chart tabular data, typically running as a Python/Flask web application backed by an LLM. The root cause is CWE-94, improper control of generation of code - attacker-influenced input is incorporated into a dynamically generated or evaluated code path (for example transformation/data-derivation logic that is compiled or executed server-side), so crafted input becomes executable code rather than inert data. The affected CPE is cpe:2.3:a:microsoft:microsoft_data_formulator, covering all builds below 0.7.

RemediationAI

Upgrade Microsoft Data Formulator to version 0.7 or later, the first fixed release per the vendor (Vendor-released patch: 0.7; consult the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-41094 for exact package guidance). Because exploitation requires user interaction, compensating controls until patching include not loading untrusted datasets, files, or shared session artifacts into Data Formulator; running the application under a low-privilege, sandboxed or containerized account so any code execution is contained; and restricting the app to trusted users rather than binding it to public network interfaces. The trade-off of sandboxing and network restriction is reduced convenience for shared or collaborative use, but it materially limits blast radius and reachability while the upgrade is scheduled.