_ ___ ___ _ _ _____ __ ___ _____ ___ _ _ /_\ / __| __| \| |_ _|___ \ \ / /_\_ _/ __| || | / _ \ (_ | _|| .` | | | |___| \ \/\/ / _ \| || (__| __ | /_/ \_\___|___|_|\_| |_| \_/\_/_/ \_\_| \___|_||_|
items disclosed in the window, by track and severity. select a count to filter the feed.
—
agent incidents and ai vulnerabilities in the window. bars are stacked by severity on one scale; select a name to filter the feed.
items per week by disclosure date, stacked by severity. track and vendor filters apply.
the latest run's summary appears here
A run collects what was disclosed since the previous run. Each item is dated by when its source first published it, which can be days or months after the event. Windows count back from the latest run's date, not from today, so a missed run does not empty the page.
A vulnerability with a published CVSS score takes that score's band. Status says who stands behind an incident or vulnerability: confirmed means the affected vendor, operator or an official body confirmed it; reported means a researcher or the press reported it; disputed means the named party disputes it.
Sources: the GitHub Advisory Database for AI-ecosystem packages, the AI Incident Database, security researchers' and vendors' disclosures, AI security institutes (UK AISI, US CAISI and others), evaluators' own publications, and major press. Every item links to the page it was taken from. Before a run is published, a separate checker re-opens its sources and rejects what they do not support.
Records before October 10, 2026 were loaded in one batch from an earlier monitor; daily runs start on October 28, 2026. Not affiliated with any organization listed.