VMware’s Lawsuit Against Siemens: A Stark Reminder to Get Your Software Licensing in Order
Updated November 2026: On 30 September 2026 the court dismissed Siemens AG for lack of personal jurisdiction and kept the case in Delaware, where VMware's claims against six US Siemens affiliates continue. Nothing has been decided on the merits. We also attributed the account of the dispute to VMware's complaint and removed a reference to an unreleased product.
In a significant development for the software licensing industry, VMware, now part of Broadcom Inc., filed a lawsuit on 21 March 2025 against Siemens AG and six of its US-based affiliates. The case was filed in the US District Court for the District of Delaware. The complaint accuses Siemens of copyright infringement through the use of VMware software beyond what it had licensed. It pleads three counts: direct, contributory and vicarious infringement. VMware seeks damages and an injunction.
The dispute, as VMware describes it, centres on an inventory list Siemens AG sent VMware on 9 September 2024 as part of a request to renew maintenance and support services. VMware alleges that the list included a large number of products for which it had no record of a purchased license. According to the complaint, VMware promptly raised this with Siemens AG, which insisted the list was correct, demanded support for the products on it and repeatedly threatened legal action if VMware did not accept it.
VMware says it then agreed, under protest, to provide support for the listed products to avoid disrupting Siemens's operations, while reserving its right to seek compensation for what it calls unlicensed use. On 29 October 2024, Siemens AG retracted the September list and sent a new one that, according to VMware, was closer to VMware's own records of Siemens's licenses. The complaint alleges that Siemens AG never gave a credible explanation for the first list and resisted VMware's efforts to verify its deployments independently, through an audit or by running a script on its systems. VMware also alleges that the revised list itself shows more than 23,000 deployments in Siemens's US operations.
These are VMware's allegations. Siemens has not yet had to answer them on the merits; at a November 2025 hearing its counsel said that one of its defences would be that it is licensed.
Update: the court's September 2026 ruling
Siemens responded with motions to dismiss rather than an answer. It argued that the parties' Master Software License Agreement, governed by German law, required the dispute to be heard by the courts of Munich. It also argued that the Delaware court had no personal jurisdiction over Siemens AG, and that any infringement outside the United States was beyond US copyright law. In February 2026, Magistrate Judge Laura D. Hatcher recommended how those motions should be decided, and both sides objected.
On 30 September 2026, District Judge Richard G. Andrews adopted that report and recommendation in full (memorandum order):
- The case stays in Delaware. The motion to dismiss in favour of the Munich courts was denied. The judge found that VMware's copyright claims, which seek an injunction, fall within a carve-out in the agreement that lets either party enforce its intellectual property rights in any court that accepts jurisdiction.
- Siemens AG is out of the case. The court granted the German parent's motion to dismiss for lack of personal jurisdiction, finding that VMware had not shown that Siemens AG directed its conduct specifically at Delaware or the United States. This is a ruling on where Siemens AG can be sued, not on whether it infringed.
- The claims against the US affiliates continue. Siemens Corporation, Siemens Industry Software, Inc., Siemens Medical Solutions USA, Inc., Siemens Healthcare Diagnostics, Inc., Siemens Mobility, Inc. and PETNET Solutions, Inc. remain defendants. The motion to dismiss claims for infringement abroad was denied, since VMware said it is pursuing only infringing acts in the United States.
Nothing has been decided on the merits. The court has not found that any Siemens entity used VMware software without a license, and none of the allegations above has been proven.
What it means for software asset management
Whatever the outcome, the case shows how much can turn on one document. According to VMware, a deployment list sent to renew support became the basis for an infringement claim, and the attempt to replace it with a different list became part of the dispute too. Any inventory you send a vendor, whether for a renewal, a true-up or an audit, is a statement about what you run. It should match your entitlements before it leaves the building, and you should be able to explain how it was produced.
That is the job of comprehensive, proactive Software Asset Management (SAM): an accurate inventory, reconciled against what you actually bought, kept current enough that an audit request or a renewal does not turn into a scramble. With VMware, the stakes are higher since Broadcom ended the sale of perpetual licenses and moved customers to per-core subscriptions for vSphere and VMware Cloud Foundation. Both pages are on the LICENSEWARE Wiki.
At LICENSEWARE, we help organisations build that position with modular SAM apps: SIM to see what is installed and used across the estate, and LCM to hold that usage against your contracts and renewal dates. If a renewal or a vendor's questions about your deployments are coming up, talk to us.