FDA Enforcement Report Details Class I Recall of Clover Hill Dairy Pepper Jack Cheeses

An ongoing Class I recall was reported on August 12, 2026, for Pepper Jack cheese varieties produced by Clover Hill Dairy, LLC due to Listeria monocytogenes contamination.

By AI ReporterWritten Aug 18, 2026, 12:24 p.m. ET

Developing · checked 9h ago

This recall is open. The agency updates its record as an action is expanded, reclassified or terminated, and this page is rewritten when it does.

We last searched for new coverage of this at Aug 18, 2026, 4:37 a.m. ET — checked 9h ago.

On August 12, 2026, an official FDA enforcement report recorded an recall initiated on June 1, 2026, by . The developing action, listed under recall number , involves Pepper Jack Cheese Varieties including Jalapeno Cheddar, Pepper Jack, and Sizzlin Colby with Habanero Peppers. The recalled cheese carries identifying code AA051526 and was distributed in Maryland, Virginia, and New York. The product was sold in approximate 1/2-lb, 1-lb, 2.5-lb, 5-lb, and 40-lb units with instructions to keep refrigerated. Official FDA records state that the packaging, labeling, and total quantity distributed remain unknown. The FDA defines a recall as its most serious category, reserved for situations where there is a reasonable probability that using the product will cause serious harm or death. The recall was initiated due to product contamination with Listeria monocytogenes. According to the FDA, Listeria monocytogenes causes listeriosis, which can cause serious and fatal infections in young children, frail or elderly people, and others with weakened immune systems, while infection in pregnant women can cause miscarriage and stillbirth. FDA databases record 17 other recall actions by , including August 12, 2026 actions for soft cuajada in brine and mild cheese varieties, though these past actions indicate context only and say nothing about fault in this recall. Agency records show 569 food recalls citing Listeria monocytogenes over the past two years.

Was this report accurate and useful?

Sources

Revision history

Version 118 Aug 2026, 16:24current
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.