US7326708B2 Patent litigation record

Patent 10 cases

US7326708B2 has been asserted in 10 cases on record. Each row links to that case’s full docket record.

Litigation indexPatsnap Litigation Data··Docket source: PACER

10 cases on record

Cases on record
10
Asserted by
Merck Sharp & Dohme · Mylan Pharmaceuticals · Par Pharmaceutical
Asserted against
Aurobindo Pharma · Biocon Pharma · Merck Sharp & Dohme · Prinston Pharmaceutical · Torrent Pharmaceuticals · Mylan · Alvogen Pine Brook · Mylan Pharmaceuticals
Courts
D. Del. · Fed. Cir. · N.D. W. Va. · D.N.J.
Technology
medicinal preparations
Case no.PartiesCourtFiledDurationOutcome
1:25-cv-00449 Merck Sharp & Dohme, LLC v. Aurobindo Pharma, Ltd. D. Del. 11 Apr 2025 81 d Consent Judgment
1:23-cv-00683 Merck Sharp & Dohme, LLC v. Biocon Pharma, Ltd. D. Del. 23 Jun 2023 52 d Consent Judgment
23-1013 Mylan Pharmaceuticals, Inc. v. Merck Sharp & Dohme, LLC Fed. Cir. 5 Oct 2022 218 d Voluntary dismissal
1:22-cv-01300 Merck Sharp & Dohme, LLC v. Prinston Pharmaceutical, Inc. D. Del. 3 Oct 2022 137 d Consent Judgment
1:19-cv-00872 Merck Sharp & Dohme Corp. v. Torrent Pharmaceuticals Limited D. Del. 9 May 2019 286 d Other
1:19-cv-00101 Merck Sharp & Dohme Co., Inc. v. Mylan, NV N.D. W. Va. 2 May 2019 1461 d Case Settled
1:19-cv-00310 Merck Sharp & Dohme Corp. v. Alvogen Pine Brook, LLC D. Del. 13 Feb 2019 519 d Other
1:19-cv-00315 Merck Sharp & Dohme Corp. v. Mylan Pharmaceuticals, Inc. D. Del. 13 Feb 2019 89 d Voluntary dismissal
1:19-cv-00320 Merck Sharp & Dohme Corp. v. Torrent Pharmaceuticals Limited D. Del. 13 Feb 2019 371 d Other
2:19-cv-04432 Par Pharmaceutical, Inc. v. Merck Sharp & Dohme Corp. D.N.J. 1 Feb 2019 20 d Voluntary dismissal
Source: Patsnap Litigation Data. Cases asserting US7326708B2 in the current snapshot. Run this in Eureka
Patsnap Eureka

How strong is US7326708B2?

Closest prior art, compared claim by claim, with every reference rated for how hard it hits.

Run a novelty search
10,000 free credits to start

About this summary. This page summarises the litigation records within the coverage and snapshot dates stated here. Counts describe records in that dataset and do not, by themselves, establish the conduct, litigation success or legal position of any person or organisation.

Docket data has limits. Records are drawn from a snapshot and may lag the live docket. Sealed filings, amended complaints, counterclaims and post-closure motions may not be reflected. Party names, attorney names and firm affiliations are reproduced as recorded and may contain omissions. Where a field is absent from the record, this page marks it as not recorded rather than inferring a value.

No characterisation of the parties or the outcome. This page reports what the record contains. Nothing here should be read as an assertion that any party infringed, that any patent is valid or invalid, that any settlement occurred, or that any party prevailed. The filing of a claim is not a court finding, and a docket marked “closed” does not by itself establish infringement, validity, settlement or a decision on the merits.

No FTO or validity opinion. Nothing on this page constitutes a freedom-to-operate, novelty, validity or infringement opinion. Any decision touching a live patent dispute should be verified independently and reviewed with qualified patent counsel.

Third-party names and marks. Party, attorney, judge and company names appear for identification only. Company names may be trademarks of their owners; their appearance does not, by itself, imply affiliation with or endorsement by Patsnap.

Corrections and privacy requests. To report an inaccurate record or attribution, use the “Report an incorrect record” link on this page. For requests concerning your personal information, including, where applicable, the rights to access, rectify, erase, restrict or object to processing, use the “Privacy request” link. We assess requests under applicable law. See our Privacy Policy for details of this processing.

Help us improve

Something wrong, out of date, or missing on this page? Tell us and it goes straight to the team that maintains it.