Last updated: July 16, 2026
CyDex v. Lupin (1:19-cv-02043): Litigation Summary, Claims at Issue, and Patent/Entry Impact
CyDex Pharmaceuticals, Inc. v. Lupin Limited (case no. 1:19-cv-02043) is a U.S. patent infringement dispute filed in 2019 involving CyDex patents asserted against Lupin’s proposed generic product. The litigation posture supports (i) an Orange Book-linked “generic entry risk” profile tied to the asserted patents and (ii) standard Hatch-Waxman timing pressure that affects when Lupin could launch, subject to any court-driven timing and any settlement or license terms.
What is the CyDex Pharmaceuticals v. Lupin Limited case 1:19-cv-02043 about?
Core dispute: CyDex accuses Lupin of patent infringement based on Lupin’s FDA-relevant generic development and corresponding certification(s) to the patents listed for the reference-listed drug (RLD) in the U.S. (Orange Book framework). The suit is styled as a Hatch-Waxman infringement action typical of 35 U.S.C. § 271(e)(2).
Procedural posture: Filed in 2019 in the District Court under docket 1:19-cv-02043. The litigation summary needed for business decisions hinges on (a) which CyDex patents were asserted, (b) what Lupin certified (Paragraph I, II, III, or IV), (c) claim construction and dispositive rulings, and (d) whether the parties reached a settlement that dictated a launch date or design-around terms.
What patents did CyDex assert in 1:19-cv-02043?
No specific patent numbers, asserted claims, or expiration dates are provided in the input. A correct litigation analysis must tie each asserted patent to: (1) the Orange Book listing, (2) the claim scope, (3) any claim construction decisions, and (4) infringement and validity outcomes. Without those identifiers, any statement would risk being inaccurate.
What Orange Book listing and FDA certification triggered the lawsuit?
The case number alone does not identify:
- the RLD name,
- which NDA/BLA the Orange Book entry corresponds to,
- the strength of the listed patents (drug substance vs formulation vs method of use),
- or the specific certification(s) Lupin made to those patents.
A factual litigation analysis must include the RLD/NDA and the specific Paragraph IV status. Those details are not present in the provided information.
What did Lupin argue in response: non-infringement, invalidity, or both?
In Hatch-Waxman patent suits, defendants usually raise a mix of:
- non-infringement (product does not meet claim limitations),
- invalidity (35 U.S.C. §§ 102/103/112/101, depending on case),
- and procedural defenses (standing, venue, or adequacy of allegations).
A litigation summary that supports business action requires the actual defenses and the court’s rulings. Those rulings are not included in the user-provided input.
How did claim construction affect infringement or validity in CyDex v. Lupin?
Claim construction outcomes typically decide:
- whether Lupin’s proposed compound, formulation, or dosing schedule meets the CyDex claim limitations,
- whether the asserted claims are narrowed in a way that preserves novelty/enablement,
- whether “means-plus-function” or functional limitations are triggered.
A precise analysis needs:
- the claim construction order date(s),
- the specific construed terms,
- and how those constructions map to Lupin’s design-around.
No construction specifics are included in the provided information.
When did the case reach dispositive decisions, and what was the outcome?
A business-relevant litigation analysis must include:
- dates of key orders (motions to dismiss, summary judgment, Daubert rulings if any),
- final judgment status (infringement found, invalidated claims, partial win/loss),
- any appellate activity (Fed. Cir. timeline).
The case outcome and key dates are not included in the provided input.
Was there a settlement or consent judgment that set a generic launch date?
Hatch-Waxman litigation often ends in:
- a settlement with a payment or a covenant not to sue,
- a stipulated dismissal with defined launch timing,
- or a consent judgment tied to an agreed design-around.
A correct exclusivity and launch-risk analysis requires settlement terms such as:
- effective date,
- permitted launch window,
- remaining patents still enforceable,
- and any field-of-use or product-spec restrictions.
Those terms are not supplied in the user message.
How strong is CyDex’s patent estate in this dispute?
Assessing strength requires:
- which CyDex patents were asserted,
- whether they were upheld as valid,
- whether the court found infringement,
- and whether the asserted claims are composition/formulation vs method-of-use.
Without the asserted patent identifiers and the court’s merits determinations, a strength assessment cannot be grounded in facts.
What generic entry risks exist for Lupin if the case ended in CyDex’s favor?
If the court ruled for CyDex on infringement and/or invalidated fewer than all asserted claims, Lupin’s entry risk profile becomes:
- delayed launch until expiration or non-infringement clearance,
- potential carve-outs if the court permits continued launch for non-infringing SKUs,
- renewed risk if additional patents are later asserted.
A risk conclusion depends on the case result and any settlement or ongoing injunction.
What generic entry risks exist if Lupin prevailed?
If Lupin won on invalidity or non-infringement, the entry risk profile typically shifts to:
- earlier launch for Lupin and other ANDA filers,
- increased likelihood of “at-risk” launches,
- pressure for subsequent challenges by patent holders to remaining patents.
Again, the factual basis requires the actual judgment.
Does this case affect biosimilar or only small-molecule generic entry?
CyDex v. Lupin is docketed as a generic infringement action under an Orange Book framework, which typically indicates a small-molecule or authorized generic pathway rather than a biologic/biosimilar program (BPCIA Orange Book is not used; BLA/Biologics License Application exclusivity and biosimilar interchange are different).
To be accurate, the drug category tied to the asserted NDA is needed; it is not provided.
How does CyDex’s litigation strategy compare with other CyDex vs. generic challenges?
Strategic comparison requires:
- other CyDex litigations’ outcomes,
- common patent families and how often they survive validity attacks,
- typical settlement structures.
No additional CyDex cases are included in the prompt.
Key Takeaways
No patent numbers, asserted claims, FDA/NDA identifiers, procedural milestones, court rulings, or settlement terms are provided in the input. A complete and accurate litigation summary and analysis for 1:19-cv-02043 requires those case-specific facts tied to the docket.
FAQs
-
What does “1:19-cv-02043” tell you about the forum and type of claim in CyDex v. Lupin?
It identifies the U.S. federal docket, but it does not, by itself, specify asserted patents, product, or the court’s merits outcome.
-
Which CyDex patents control whether Lupin can launch at risk?
The controlling patents are the ones asserted and ruled on in this docket, but patent identifiers are not provided in the input.
-
How do Paragraph IV certifications relate to CyDex v. Lupin?
They typically frame the trigger for 271(e)(2) litigation, but the specific certification(s) are not provided.
-
Does a settlement in CyDex v. Lupin automatically determine the Orange Book expiration timeline?
Settlement terms can govern launch regardless of expiration timing, but settlement details are not provided.
-
Can other ANDA filers launch based on the outcome of CyDex v. Lupin?
Potentially, but it depends on shared patent listings and whether the judgment applies broadly to the same Orange Book-listed patents; the asserted patent set is not provided.
References (APA)
- Case docket: CyDex Pharmaceuticals, Inc. v. Lupin Limited, No. 1:19-cv-02043 (U.S. District Court, 2019).
