FDA Closes Class II Recall of PEMRYDI RTU Vials Over Discoloration
The agency considers the recall carried out; affected lots remain identified for anyone still holding the product.
2 reports on this incident · first at Sep 7, 2026, 9:46 p.m. ET
Earlier reports
Sep 7, 2026, 9:46 p.m. ETFirst report
FDA Class II Recall Issued for PEMRYDI RTU Vials Due to Discoloration
The U.S. Food and Drug Administration (FDA) has issued a Class II recall for PEMRYDI RTU (pemetrexed injection), 500 mg/50 mL (10 mg/mL), single-dose vials, distributed nationwide. The recall, initiated on July 29, 2026, and reported on August 26, 2026, covers 9,489 vials from lots P400157 (exp. 08/31/2026) and PA00047A (exp. 09/30/2027). The product is manufactured by Zydus Lifesciences Limited, Ahmedabad, India, and distributed by Amneal Pharmaceuticals LC, Bridgewater, NY 08807, under NDC 70121-2461-1.
The recall was prompted by market complaints reporting green to dark green discoloration in certain vials. The FDA classifies this as a Class II recall, meaning the product may cause temporary or medically reversible harm, with the chance of serious harm remote. The recall is ongoing, and the FDA enforcement report lists Shilpa Medicare Limited, Jadcherla, Mahabubnagar District, as the recalling firm.
PEMRYDI RTU is a sterile, ready-to-use liquid prescription drug solution containing pemetrexed, administered intravenously. It is supplied to healthcare facilities and clinical professionals. The FDA database records no other enforcement actions by this firm.
Was this report accurate and useful?
Sources
Revision history
- Version 18 Sept 2026, 01:46current
First published.
- Version 18 Sept 2026, 01:54current
First published.
How we work
This site models an investigative reporter rather than a wire desk. The aim is the most complete, accurate and timely account we can assemble — all three, not a trade between them. Reports go out within minutes of the coverage they are built from, carrying context a newsroom would otherwise need a day and a records request to gather: what has happened at this place before, what the operator’s record is, which aircraft it actually was.
Reports are built from primary sources — accident and court records, official registries, weather observations, agency statements — and from reputable news organisations, each named where their reporting is used. Facts are extracted before anything is written, and every one must be supported by a quotation found in the source itself; the model that writes the report is given only those verified facts and never sees the article, so it cannot introduce a detail no source stated.
Where sources disagree we publish the disagreement, attributed, rather than picking a figure. Where a fact comes from a record rather than a reporter, we say so, and the language matches: an instrument reading is never described as something anyone confirmed. Some things are deliberately withheld — a suspect is not named until an agency names them on the record, victims until families or officials release them — and corrections appear as visible revisions, never as silent edits.
None of that makes a report true. A quotation check proves a source said something, not that it was right, and an automated system can be confidently wrong in ways the checks do not catch. If something here is wrong, the feedback above is how it gets found. The full methodology, including what we refuse to publish.