
The French Computer Emergency Response Team (CERT-FR) has issued a warning regarding Microsoft SharePoint Server, citing two critical vulnerabilities that can be exploited without authentication. Over the past month, four product vulnerabilities have come under active exploitation, according to counts from CISA and various security vendors. To complicate matters, the 2016 and 2019 editions, which are most commonly found on servers exposed to the internet, have just received their final security updates.
This alert is referenced as CERTFR-2026-ALE-008 and targets two deserialization vulnerabilities, CVE-2026-50522 and CVE-2026-58644. Both vulnerabilities allow “an unauthenticated attacker to execute arbitrary code” on an accessible server, without any user interaction. These vulnerabilities share a critical score of 9.8 on the Common Vulnerability Scoring System (CVSS) scale. Three on-premises editions are affected: SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition. Fortunately, SharePoint Online has been patched by Microsoft without requiring client action.
Tenable released a notice on July 16 that encompasses five SharePoint vulnerabilities along with the version numbers that address all of them. Four of these vulnerabilities were already being actively exploited as of that date, ranging from impersonation with a severity score of 6.5 to privilege escalation and remote code execution, both rated at 9.8. The list of known exploited vulnerabilities maintained by CISA now includes thirteen issues with the product, five of which have been added since January. The most high-profile, CVE-2026-45659, has been associated with the deployment of the Warlock ransomware. This series dates back to the ToolShell campaign in 2025, which had previously raised alarms about other Microsoft service vulnerabilities.
Six days from patch release to successful exploit
CVE-2026-50522 was disclosed to Microsoft through the Pwn2Own competition, courtesy of the Zero Day Initiative. The patch was released on July 14, and Defused detected the first exploitation attempts just three days later, on July 17. WatchTowr documented successful exploit attempts on their honeypot network on July 20, just hours after a proof-of-concept code was published. Hence, it only took six days for attackers to transition from patch release to a successful exploit.
Attackers exploited CVE-2026-58644 even before any public disclosure, and it was added to the CISA catalog on July 15. These attackers were able to steal machine keys from IIS servers, giving them persistent access that would bypass the patch. “The patch alone is not enough; defenders need to rotate credentials on any potentially exposed assets,” cautioned WatchTowr. CISA advises checking that AMSI (Antimalware Scan Interface) is enabled for each web application and to look for signs of intrusion before renewing any keys.
CVE-2026-56164, a privilege escalation vulnerability rated 9.8, was added to the CISA catalog on July 14, coinciding with the day it was patched, leaving just hours between the patch publication and its cataloging. CVE-2026-58644 joined the list the following day. CVE-2026-55040, a security function bypass rated 9.1, remains patched with no known exploits to date. All five references share the same version numbers, allowing for simultaneous deployment without the need for prioritization.
A post-patch attack on SharePoint Server 2016 and 2019
Extended support for the 2016 and 2019 editions officially ended on the same date, July 14, 2026. Microsoft has not announced any plans for extended security updates for these two versions. The patches released on this date are the last they will receive, meaning any vulnerabilities discovered thereafter will remain unpatched on servers that stay unchanged. SharePoint 2016 had already exited mainstream support in 2021, and analysts from Directions on Microsoft deem it “extremely unlikely” that the publisher will extend the deadline.
Censys reports approximately 1,500 on-premises SharePoint instances exposed to the Internet globally, with the majority running on the 2019 edition. The United States tops the list of affected countries, followed by Germany, France, and Canada. France ranks third in this exposed landscape just as these systems are no longer receiving support.
Three potential paths forward, and a hardening strategy in the meantime
Microsoft offers SharePoint Online, the cloud-based service that it manages and updates itself. There is also SharePoint Server Subscription Edition, the current on-premises version that follows a modern lifecycle and requires users to remain within two versions of the current one, with a subscription license for access. Finally, hybrid deployment combines both models and allows for gradual transition over several stages. However, the Subscription Edition is still only a temporary solution, as the publisher continues to phase out legacy features with a twelve-month notice. Remaining on-site creates a continued obligation to keep pace with the publisher rather than alleviating it.
Immediate hardening measures involve reducing exposure by removing direct Internet access or filtering it through an application firewall, enabling AMSI on a per-application basis, and renewing secrets after investigating for signs of breach. The burden of timely response will shift to manufacturers as the Cyber Resilience Act mandates the notification of exploited vulnerabilities within twenty-four hours.
An exposed SharePoint 2019 server now combines an unsupported product, a sustained rate of vulnerability discovery, and a narrow exploitation window of just a few days. The product’s release date now weighs heavier than the monthly patch. It is essential to catalog the existing environment, decide between migration and exposure removal, and schedule these decisions on a clear timeline.
Servers that a business unit deployed for a specific project and later removed from IT oversight escape regular inventory. Censys tracks exposure via the Internet without distinguishing between actively managed servers and those left behind. The key questions to pose regarding these servers boil down to three points: What edition are they running? What patch level are they at? What is their exposure level to the Internet?



