AI Incident Tracker

Artificial intelligence systems are rapidly becoming integral to our world, but with increased reliance comes heightened risk. This tracker compiles incidents of AI-related breaches, leaks, and vulnerabilities to raise awareness and encourage proactive security measures. From model exploits to data leaks involving AI systems, stay informed about the latest risks and lessons learned in this evolving landscape.

This tracker is maintained as a resource for researchers, developers, and organizations to understand the security challenges associated with AI. Each entry includes details about the incident, its impact, and key takeaways. The information is sourced from verified reports and will be updated regularly.

Report an AI Incident

If you want to add a known AI breach, leak or vulnerability to our tracker, you can send us the information via our 'AI Breach Tracker Submission Form'. We'll validate and confirm the event before adding to the database.

Submit a Breach

Secure the AI Behind the Headlines

Most of these incidents trace back to AI that nobody was watching. FireTail gives you visibility and control over every AI tool, model and agent across your organization, so you can adopt AI without becoming the next entry.

Schedule a Demo

//// QUICK FACTS

The AI Incident Tracker.

Updated regularly to reflect emerging AI threats.

  • Tracks real-world AI security incidents, breaches and vulnerabilities
  • Covers model exploits, data leakage, prompt abuse and insecure integrations
  • Sources incidents from verified public disclosures and security research
  • Designed for security teams, developers and risk leaders

AI Incident Examples

A selection of notable AI security incidents from the tracker: what happened, how it was exploited, and why it matters.

Chef's Kiss - AI Companion Site Breach
A platform offering AI-generated "girlfriends" suffered a significant data breach, exposing private user data, including personal conversations and fantasies. The attackers exploited a weak authentication mechanism, allowing them to access and exfiltrate sensitive data stored in the system. The breach raises concerns about the privacy implications of AI systems designed for intimate interactions and underscores the need for stricter safeguards in handling user-generated content.

Mudler Time - AI Vulnerability
‍
A timing attack vulnerability was discovered in Mudler’s LocalAI version 2.17.1. This exploit allows attackers to deduce sensitive information, such as valid API keys or passwords, by analyzing the response times of the server during authentication attempts. The flaw stems from discrepancies in the time taken to validate incorrect versus correct credentials, enabling attackers to iteratively guess the correct inputs. If exploited, it could lead to unauthorized access to systems relying on this AI tool for authentication.

IDOR in Lunary - AI Vulnerability
‍
In version 1.3.2 of Lunary AI, an Insecure Direct Object Reference (IDOR) vulnerability (CVE-2024-7474) was identified, allowing unauthorized access to sensitive user data. By manipulating the id parameter in the request URL, attackers could view or delete external user accounts without authorization. This flaw resulted from inadequate validation of the id parameter, leaving external user information exposed. The issue has been categorized as critical, with a CVSS score of 9.1, underlining the potential for severe impact if exploited.

Ollama Drama - Multiple AI Vulnerabilities
A vulnerability in Ollama, detailed in Oligo Security's blog, highlighted the risks of exposing AI model prompts and context data during multi-model integrations. This issue arises when poorly configured models inadvertently leak sensitive user data through unencrypted channels or logging mechanisms. Specifically, in Ollama's case, data from prompt engineering experiments was accessible without adequate restrictions, enabling unauthorized users to extract sensitive information or manipulate outcomes. This incident underscores the need for robust access controls and encryption when deploying interconnected AI models

Syntax Error - AI Crypto Breach
‍
A vulnerability in the Syntax smart contract platform, identified by Spectral Labs, allowed attackers to exploit logic errors in the code, enabling unauthorized transactions. In response, the platform was forced to pause its operations, temporarily freezing users' assets. The vulnerability allowed hackers to make off with $200K in crypto transactions. This incident highlights the critical importance of AI security audits in AI-driven blockchain platforms to prevent catastrophic misuse.

You Only Load Once - AI Supply Chain Attack
‍
Hackers hijacked an Ultralytics AI model by injecting malicious payloads during a public model-sharing session. The compromised model was downloaded by unsuspecting developers, infecting thousands of systems with cryptomining malware. This breach underscores the danger of downloading unverified machine learning models and highlights the need for secure distribution channels in the AI ecosystem.

Disclaimer: This document includes links to multiple third-party publications and websites. FireTail is not responsible for any external content. Additionally, analysis of the data breaches contained here is based on best effort understanding of the information made available. Disclosures often do not include all the relevant information or details. Information provided is for educational / illustrative purposes only.

Why AI Security Matters

AI systems introduce new security risks that traditional controls were never designed to handle. Vulnerabilities can emerge from model behavior, training data exposure, prompt manipulation, insecure integrations and poor access controls.

As organizations rely more heavily on AI for decision-making and automation, security gaps can lead to data leaks, system misuse, regulatory exposure, and loss of trust. Proactive AI security helps teams identify risks early, respond to incidents faster, and deploy AI responsibly at scale.

Frequently asked questions.

Answers to common questions about AI security incidents and the FireTail AI Incident Tracker.

What is an AI security incident?+

An AI security incident occurs when an AI system is compromised or misused, for example through sensitive data exposure, prompt abuse, model misbehavior or an insecure integration. The tracker records these incidents so organizations can see which AI risks are happening in the real world.

How are AI breaches different from traditional security breaches?+

AI breaches often involve indirect risks, such as prompt injection, model behavior flaws or data exposed through a model's outputs. Traditional security tools weren't built to see these AI-specific threats, so they often go unnoticed.

Who should monitor AI security incidents?+

Security teams, risk and governance leaders, and anyone deploying AI in production. Real incidents show which risks are actually materializing, which helps teams prioritize controls and make the case for them.

How is the tracker maintained?+

We add incidents from verified public disclosures and security research, and update the tracker regularly as new incidents emerge. If you know of an incident we've missed, you can submit it for review using the form on this page.

How does FireTail help prevent incidents like these?+

FireTail discovers the AI in use across your organization, enforces policy at the point of use, and monitors AI activity for threats such as prompt injection and sensitive data exposure, so issues are caught before they become incidents.