FirstAlerts

B. Braun Expands Recall of Sodium Chloride Injection to Three Lots

FDA reports the recall now covers three lots of 0.9% Sodium Chloride Injection due to iron oxide particulates.

4 reports on this incident · first at Aug 30, 2026, 10:45 p.m. ET

By AI ReporterFirst reported Aug 28, 2026, 10:40 a.m. ETWritten Aug 30, 2026, 11:22 p.m. ET
has expanded its voluntary nationwide recall of to include three lots, according to the U.S. Food and Drug Administration (FDA). The recall was initiated on August 19, 2026, and is as of the FDA's report dated August 28, 2026. The recall is due to the , which could cause . The FDA reports no injuries or deaths associated with this issue. Customers who have the recalled product should return it to the place of purchase.

Earlier reports

  1. Aug 30, 2026, 10:52 p.m. ET

    FDA Reports Injuries in Ongoing B. Braun Sodium Chloride Recall

    The U.S. Food and Drug Administration (FDA) reports that injuries or illnesses have now been reported in connection with the ongoing recall of three lots of B. Braun 0.9% Sodium Chloride Injection USP, 100 mL, in a 150 mL PAB® Container. The agency states that no reports of serious injury, death, or other adverse events have been associated with this issue, according to fda.gov.

    The recall, initiated on August 19, 2026, was prompted by the presence of particulate matter identified as iron oxide, which the FDA says could cause life-threatening adverse health consequences including pulmonary emboli, occlusions of other blood vessels, and/or phlebitis. The product was distributed nationwide to hospitals and healthcare facilities.

    B. Braun Medical Inc. issued the voluntary recall. The FDA advises customers who have the recalled product to return it to the place of purchase. The recall status is listed as ongoing.

  2. Aug 30, 2026, 10:50 p.m. ET

    FDA Closes Recall of B. Braun Sodium Chloride Injection Lots

    The U.S. Food and Drug Administration has closed the recall action initiated by B. Braun Medical Inc. on August 19, 2026, for three lots of 0.9% Sodium Chloride Injection USP, 100 mL, in a 150 mL PAB® Container. The agency considers the recall carried out, according to the FDA.

    The recall was issued because the product contained particulate matter identified as iron oxide, which could lead to life-threatening adverse health consequences including pulmonary emboli, occlusions of other blood vessels, and/or phlebitis. The FDA reported no serious injuries, deaths, or other adverse events associated with this issue.

    Customers who still have the recalled product should return it to the place of purchase, the FDA said. The recall was distributed nationwide to hospitals and healthcare facilities.

  3. Aug 30, 2026, 10:45 p.m. ETFirst report

    B. Braun Recalls Three Lots of Sodium Chloride Injection Due to Iron Oxide Particulates

    B. Braun Medical Inc. has initiated a voluntary nationwide recall of three lots of 0.9% Sodium Chloride Injection USP, 100 mL, in a 150 mL PAB® Container, according to the U.S. Food and Drug Administration (FDA). The recall, initiated on August 19, 2026, and reported on August 28, 2026, is due to the presence of particulate matter identified as iron oxide, which could cause life-threatening adverse health consequences including pulmonary emboli, occlusions of other blood vessels, and/or phlebitis.

    The FDA reports that there have been no reports of serious injury, death, or other adverse events associated with this issue. The recall is ongoing, and the product was distributed nationwide to hospital and healthcare facilities.

    Customers who have the recalled product should return it to the place of purchase, according to the FDA.

Was this report accurate and useful?

Sources

Revision history

  1. Version 131 Aug 2026, 03:22current

    First published.

  2. Version 131 Aug 2026, 02:45current

    First published.

  3. Version 131 Aug 2026, 02:52current

    First published.

  4. Version 131 Aug 2026, 02:50current

    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.