Open source license lawsuits have moved from a niche concern into a steady stream of litigation across the United States, Germany, and France, with courts sorting out who can sue over violations of licenses like the GNU General Public License (GPL), what damages are available, and how those licenses apply to newer problems such as AI code generation. Several major cases are heading to trial or awaiting appellate rulings in 2026 and 2027, and their outcomes will build on a foundation set by roughly two decades of earlier decisions.
SFC v. Vizio Heads to a Jury in 2026
One of the most closely watched cases is Software Freedom Conservancy, Inc. v. Vizio, Inc., filed in October 2021 in Orange County Superior Court in California. The Software Freedom Conservancy (SFC) alleges that Vizio shipped smart TVs running a Linux-based operating system without providing the complete source code required by GPL version 2 and LGPL version 2.1.1Software Freedom Conservancy. Copyleft Compliance – Vizio The SFC is not a copyright holder in the software at issue. Instead, it is suing on a contract theory, arguing that it qualifies as a third-party beneficiary of the GPL and can enforce it in state court.2SonarSource. Will the New Judicial Ruling in the Vizio Lawsuit Strengthen the GPL
A federal court ruled in May 2022 that the SFC’s claims were contract-based rather than copyright-based, defeating Vizio’s preemption argument and keeping the case in state court. Whether the SFC actually qualifies as a third-party beneficiary is a factual question that the court has sent to trial, noting that the GPL’s requirement to provide source code to “any third party” is consistent with third-party enforcement.2SonarSource. Will the New Judicial Ruling in the Vizio Lawsuit Strengthen the GPL
On December 23, 2025, Judge Sandy Leal granted one of Vizio’s motions for summary adjudication. The court ruled that GPLv2 and LGPLv2.1 do not require Vizio to let users reinstall modified software on their TVs or keep the devices working after modification. The obligation is to provide source code in a form that can be “obtained and revised… for use in other applications,” not to support reinstallation on the original hardware.3Software Freedom Conservancy. SFC v. Vizio Minute Order, December 23, 2025 The court distinguished GPLv2 from GPLv3, which explicitly requires manufacturers to provide installation information for “User Products.”4Baker Botts. When Consumers Enforce Open Source
On February 17, 2026, the court ruled that two questions must go to a jury: whether a consumer who bought a Vizio TV has the right to demand source code under the license, and whether Vizio created a separate contractual obligation to provide source code through its customer support interactions and product menus.4Baker Botts. When Consumers Enforce Open Source1Software Freedom Conservancy. Copyleft Compliance – Vizio5Ars Technica. Inside the Fight to Force Vizio to Share Linux-Based Source Code for Its TVs OS
A win for the SFC would expand the pool of potential enforcers of copyleft licenses. Historically, only copyright holders have had clear standing to sue. A ruling that consumers or nonprofits qualify as third-party beneficiaries would open the door to a much wider set of plaintiffs.
GitHub Copilot: AI Training and License Conditions
A class action filed in November 2022 against GitHub, Microsoft, and OpenAI alleges that GitHub Copilot was trained on publicly available open source code without honoring the license conditions attached to that code. The plaintiffs argue that Copilot generates code suggestions that strip out required attribution, copyright notices, and license text demanded by licenses like MIT, GPL, and Apache.6Saverilawfirm.com. GitHub Copilot Intellectual Property Litigation
In July 2024, Judge Jon Tigar dismissed the plaintiffs’ DMCA claims, which required the AI output to be “identical” to the original source code. The court allowed breach-of-license and breach-of-contract claims to move forward, holding that open source licenses are binding agreements and that a company can be liable for ignoring license conditions even when the output is not a verbatim copy.7Yang Law Offices. GitHub Copilot Open Source Licensing for Developers and Startups8Baker Law. The Copilot Litigation9GitHub Copilot Litigation. Case Updates
The case does not include direct copyright infringement claims.8Baker Law. The Copilot Litigation Its importance lies in how courts handle the intersection of AI training practices and the attribution and sharing obligations embedded in open source licenses, a question that grows more pressing as AI coding assistants become standard.
Entr’ouvert v. Orange: France Awards Over €800,000
In February 2024, the Paris Court of Appeal issued one of the largest damages awards ever seen in an open source license case. The court ruled that French telecom Orange violated GPLv2 when it integrated Entr’ouvert’s “Lasso” authentication library into a government portal without providing source code for its modifications or offering access to the code as required by the license.10Heather Meeker. French Court Issues Damages Award for Violation of GPL
Entr’ouvert offered Lasso under a dual-licensing model: free under the GPL, or paid under a commercial license. Orange had inquired about a commercial license but declined, then used the code without meeting the GPL’s requirements for over a decade. Litigation began in 2011. A 2019 lower court dismissed the GPL claims as a contract matter, and a 2021 appellate ruling agreed. In 2022, France’s Court of Cassation overturned that decision and sent the case back to the Court of Appeal.10Heather Meeker. French Court Issues Damages Award for Violation of GPL
The final ruling classified Orange’s GPL violations as “counterfeiting” under French intellectual property law, meaning copyright infringement rather than a mere breach of contract. That classification unlocked stronger remedies. The court ordered Orange to pay over €800,000, comprising €500,000 in compensatory damages, €150,000 in disgorgement of profits, and €150,000 in “moral damages,” an award described as extremely rare in open source disputes.11Vaultinum. Failure to Comply With GNU GPL V2 License – Key Takeaways The court calculated the compensatory damages in part by looking at the price of the commercial license Orange had declined years earlier.12DLA Piper. Wakeup Call for Open Source Users – French Court Awards Damages for GPL Violations
Steck v. AVM: LGPL Enforcement in Germany
In what the SFC has called the first successful litigation specifically enforcing the LGPL, German developer Sebastian Steck sued router manufacturer AVM in a Berlin court in July 2023 over its FRITZ!Box 4020 router. AVM had provided incomplete source code for the device’s FRITZ!OS firmware, which incorporates Linux and several libraries licensed under LGPLv2.1. The missing pieces included the scripts needed to compile and reinstall the software.13The Register. Software Freedom Conservancy Celebrates LGPL Court Win
On June 24, 2024, the Berlin Regional Court ruled in Steck’s favor. AVM provided the missing source code and installation scripts and paid €7,500 in legal expenses.13The Register. Software Freedom Conservancy Celebrates LGPL Court Win AVM did not appeal, and the appeal deadline elapsed in January 2025, making the result final.14Software Freedom Conservancy. AVM Copyleft Lawsuit Resolved With Install
The court required AVM to provide scripts enabling reinstallation of modified software on the device itself, and it ruled that manufacturers must allow changes to be written to permanent flash memory. AVM had argued that providing modification capability only for volatile RAM satisfied the license, and the court rejected that.14Software Freedom Conservancy. AVM Copyleft Lawsuit Resolved With Install The SFC described the outcome as eliminating any doubt that “both GPL and LGPL mandate the device owner’s ability to make changes to the software in the flash memory so those changes persist across reboots.”13The Register. Software Freedom Conservancy Celebrates LGPL Court Win
Neo4j v. Suhy: The Commons Clause Question
The litigation between Neo4j, Inc. and John Mark Suhy’s company PureThink is a test case for what happens when a company adds restrictive terms on top of a copyleft license. Neo4j released its Enterprise database software under AGPLv3 but appended the “Commons Clause,” a restriction limiting commercial use. Suhy and PureThink removed the Commons Clause, arguing that AGPLv3 Section 7 permits users to strip additional restrictions that conflict with the license’s terms.15Software Freedom Conservancy. Neo4j v. PureThink – Open Source Affero GPL
The trial court sided with Neo4j, granting partial summary judgment that the Commons Clause was not removable and issuing a preliminary injunction barring Suhy from stating the software was “free and open source.” The Ninth Circuit affirmed the preliminary injunction, though the SFC has emphasized that this was a ruling on the status quo during litigation, not a final decision on the merits.15Software Freedom Conservancy. Neo4j v. PureThink – Open Source Affero GPL
The case is now on appeal to the Ninth Circuit as Neo4j, Inc. v. Suhy (Case No. 24-5538). The Free Software Foundation filed an amicus brief arguing that adding the Commons Clause to a GNU license creates an “unauthorized derivative of the license” and that GNU licenses were designed to allow users to remove such conflicting restrictions.16Free Software Foundation. FSF Submits Amicus Brief in Neo4j v. Suhy As of March 2026, the Ninth Circuit has not scheduled oral argument or issued a ruling.17CourtListener. Neo4j Inc. et al. v. Suhy et al.
Automattic v. WP Engine: Trademarks and Repository Control
A dispute between Automattic, the company behind WordPress.com, and hosting provider WP Engine erupted in September 2024. Automattic CEO Matt Mullenweg sent WP Engine a cease-and-desist letter on September 23, 2024, alleging that WP Engine’s use of the “WordPress” and “WooCommerce” trademarks misled consumers. Automattic then blocked WP Engine’s access to the WordPress.org plugin and theme repository two days later.18WP Engine. Ensuring Stability and Security
WP Engine filed suit on October 2, 2024, in the Northern District of California, raising claims of defamation, intentional interference, and unfair competition. WP Engine also alleges that WordPress.org unilaterally seized control of its Advanced Custom Fields (ACF) plugin on October 12, 2024.18WP Engine. Ensuring Stability and Security Automattic responded with counterclaims and motions to dismiss and strike portions of the complaint.19Automattic. Legal Response to WP Engine
On December 10, 2024, the court granted a preliminary injunction ordering the restoration of WP Engine’s access to WordPress.org and its plugin functionality. In September 2025, the court allowed most of WP Engine’s claims to proceed against both Automattic and Mullenweg personally.18WP Engine. Ensuring Stability and Security Fact discovery closed on May 14, 2026, followed by more than 20 discovery disputes filed by both sides, including one over allegations that Automattic failed to preserve evidence. A jury trial is set for September 2027.20The Repository. WP Engine and Automattic Trade Accusations of Withheld Evidence in Flurry of Court Filings WP Engine has confirmed that settlement discussions are underway, on confidential terms.
The Earlier Cases That Built the Framework
The current wave of litigation rests on a series of earlier rulings that established how open source licenses are enforced.
Jacobsen v. Katzer (2008)
The Federal Circuit’s 2008 ruling was the first U.S. appellate decision to address the enforceability of an open source license. The court reversed a lower court that had treated the Artistic License’s terms as mere contractual covenants, holding instead that the license’s requirements (like attribution and disclosure of changes) were “conditions” on the copyright grant. Violating those conditions meant acting outside the scope of the license, which constituted copyright infringement rather than a simple breach of contract.21Harvard JOLT. Jacobsen v. Katzer The practical difference is large. Copyright infringement claims unlock preliminary injunctions, statutory damages of up to $150,000 per work, and attorneys’ fees, remedies that are difficult or impossible to obtain under contract law when the software was distributed for free.22Berkeley Technology Law Journal. Open Source Licensing, Jacobsen v. Katzer
FSF v. Cisco (2009)
The Free Software Foundation sued Cisco in December 2008 in the Southern District of New York, alleging that Cisco’s Linksys subsidiary shipped products containing GPL-licensed code without providing the required source code. The case settled in May 2009, with Cisco agreeing to appoint a “Free Software Director” for Linksys to oversee license compliance and report periodically to the FSF. Cisco also committed to making complete source code available on its website, notifying previous customers of their rights, and making a monetary contribution to the FSF.23Free Software Foundation. FSF and Cisco Settlement24Software Freedom Law Center. FSF Cisco Settlement
BusyBox Enforcement Campaign (2007–2010)
Beginning in 2007, the Software Freedom Law Center and later the SFC brought a series of lawsuits against consumer electronics companies for shipping products containing BusyBox, a widely used Linux utility, without providing source code. In December 2009 alone, the SFLC sued 14 companies, including Best Buy, Samsung, Westinghouse, JVC, and Western Digital.25CNET. Best Buy, Samsung, Others Named in GPL Suit Most settled. A July 2010 default judgment against Westinghouse marked the first time a U.S. court issued an injunction ordering a GPL violator to permanently stop distributing non-compliant software.26Software Freedom Conservancy. BusyBox GPL
Hellwig v. VMware (2014–2019)
Linux kernel developer Christoph Hellwig, with SFC support, sued VMware in Germany over its ESXi virtualization product. Hellwig alleged that VMware combined proprietary “vmkernel” code with GPL-licensed Linux kernel code into a single work without releasing the combined source code as required by GPLv2.27Software Freedom Conservancy. VMware Lawsuit FAQ The Hamburg District Court dismissed the case in July 2016 without reaching the merits, ruling that Hellwig had not sufficiently documented his specific copyrighted contributions under German evidentiary rules.28LWN.net. Hellwig v. VMware Ruling The Hamburg Higher Regional Court affirmed in February 2019, and Hellwig chose not to appeal further.29Software Freedom Conservancy. VMware No Appeal VMware later removed the contested “vmklinux” code rather than releasing it under the GPL. The case never established a precedent on the derivative-work question at the heart of the dispute.
Artifex v. Hancom (2017)
Artifex Software sued Hancom in the Northern District of California for using its Ghostscript software without complying with the GPL. When Hancom moved for summary judgment, arguing that its obligations ended once its license was revoked for non-compliance, the court disagreed. The judge found that the GPL’s language suggested obligations persisted beyond termination, because the requirement to provide source code was triggered each time the software was distributed.30Free Software Foundation. Update on Artifex v. Hancom GNU GPL Compliance Case The case settled in December 2017 on confidential terms.31Artifex. Artifex and Hancom Reach Settlement Over Ghostscript Open Source Dispute Before settling, the court’s rulings treated the GPL as an enforceable contract for purposes of the litigation, a position that has influenced later cases.
Why the Trend Matters for Companies
The wave of enforcement reflects a broader compliance problem. According to the 2024 Open Source Security and Risk Analysis report, 53% of audited codebases contained open source license conflicts. A significant source is casual reuse of code snippets, with content from Stack Overflow (automatically licensed under Creative Commons ShareAlike) accounting for about a third of identified conflicts.32Black Duck. OSSRA License Compliance Risks
The exposure is particularly acute during acquisitions, where undisclosed open source dependencies can surface as deal-killers. Copyleft licenses like the GPL can, if triggered, require the disclosure of proprietary source code, and non-compliance discovered after a deal closes can force expensive product re-engineering or halt distribution entirely. The Entr’ouvert ruling, where a French court awarded over €800,000 partly based on the cost of the commercial license the defendant had declined, illustrates how the financial exposure can stack up over years of non-compliance.
AI-assisted development has added a new dimension. The GitHub Copilot lawsuit has put companies on notice that code generated by AI tools may carry licensing obligations from the training data, and that stripping attribution from suggested code snippets may violate the original licenses. Regardless of how the Ninth Circuit rules on the DMCA question, the surviving breach-of-license claims have already established that courts will treat AI-generated code attribution failures as actionable.