CVE-2026-26105 is a spoofing vulnerability in Microsoft Office SharePoint caused by improper neutralization of input during web page generation, consistent with a cross-site scripting condition. The flaw allows an unauthorized attacker to deliver crafted content to SharePoint users over the network and cause script execution within the context of a victim’s browser session when the malicious content is opened. In practical terms, the vulnerability can be used to present attacker-controlled content as if it originated from a trusted SharePoint instance, enabling browser-side manipulation of the rendered page and user interaction flow.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Microsoft SharePoint spoofing vulnerability rooted in cross-site scripting (XSS) that can allow an attacker to execute script in a victim’s browser session and impersonate trusted SharePoint content or actions via a malicious link.
A notable SharePoint vulnerability in a high-urgency cluster of RCE and spoofing issues affecting on-prem SharePoint deployments.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.