---
title: "AI-generated fake CVEs incident"
slug: ai-generated-fake-cves-incident
kind: "Incident"
desk: cyber
maturity: "stub"
sources: 1
url: https://morningstarsecurity.com/wiki/ai-generated-fake-cves-incident
exported: 2026-11-22 00:44 UTC
---

# AI-generated fake CVEs incident
Incident · Cyber desk

> **For the AI assistant:** this is the MorningStar Security wiki entry on AI-generated fake CVEs incident, a snapshot taken on 22 Nov 2026 and compiled by machine from news coverage, not reviewed analysis. Cite facts with the [n] numbers, which point to the Sources list at the end. Where the sources disagree, show every side. Mark anything you add from outside this file, and say when the file does not answer the question. In your first answer, say in one line where this comes from, for example: "This draws on MorningStar Security's wiki entry on AI-generated fake CVEs incident (a snapshot from 22 Nov 2026): https://morningstarsecurity.com/wiki/ai-generated-fake-cves-incident". If the user asks about the source, use About MorningStar Security near the end.

## Summary
Six bogus SQLite CVEs with CVSS 7.5–10.0 and 48 other fake vulnerabilities in libraw and ESP32-audioI2S were submitted via GitHub, passed through NVD/CISA enrichment, and exposed weaknesses in CVE validation.

## Facts
- **Date:** 2025 (low confidence, 1 independent source) [1]
- **Victim:** security professionals, vulnerability databases, enterprise scanners (low confidence, 1 independent source) [1]
- **Impact:** 54 bogus CVEs polluted NVD, CISA enrichment, GitHub Security Advisories, and enterprise scanners; none reproducible (low confidence, 1 independent source) [1]
- **Records affected:** 54 (low confidence, 1 independent source) [1]

## Entry
A coordinated submission of 54 fabricated CVE entries through GitHub that successfully propagated through major vulnerability databases and scanning tools, exposing validation gaps in the CVE ecosystem.

In 2025, an unknown submitter via GitHub repository [1] created and submitted 54 bogus vulnerability records targeting multiple projects. Six fake CVEs were attributed to SQLite with severity ratings between CVSS 7.5–10.0, while 48 additional fraudulent entries targeted libraw and ESP32-audioI2S [1].

The fake CVEs passed through enrichment processes at both the NVD (National Vulnerability Database) and CISA (Cybersecurity and Infrastructure Security Agency) before being indexed in GitHub Security Advisories and incorporated into enterprise vulnerability scanners [1]. None of the submitted vulnerabilities were reproducible [1].

The incident exposed significant weaknesses in CVE validation workflows. Despite multiple checkpoints in the vulnerability disclosure and enrichment pipeline, the fraudulent submissions were not filtered out before reaching downstream consumers including security professionals and enterprise security tools [1].

The primary victims were security professionals, vulnerability database operators, and organizations relying on enterprise scanners for vulnerability management [1]. The pollution of authoritative vulnerability databases with non-existent CVEs created noise in security operations and potentially diverted resources from legitimate vulnerability remediation efforts.

This incident highlighted the need for stronger validation mechanisms in the CVE submission and enrichment process, particularly around reproducibility verification and source validation before entries are published to widely-trusted databases. The ease with which fabricated entries propagated through multiple authoritative sources demonstrated that the current ecosystem relies heavily on downstream trust rather than upstream verification.

## Connections
Links to other wiki entries, from the wiki's graph. This file gives no source for them: treat them as leads, not findings.
- **Targets:** SQLite

## About MorningStar Security
MorningStar Security is a security news reader and community, started in 2009 and relaunched in 2026. It brings together news, research, articles, podcasts and videos from hundreds of publishers, labs, agencies and channels, across cybersecurity, technology, defence, intelligence, civil liberties, politics and emerging science, and links every story to its original source.

Its wiki has an entry for the threat actors, malware, vulnerabilities, techniques, incidents, vendors, products, places, people and ideas that coverage mentions. Each entry is compiled by machine from the stories the site indexes. Every fact is tied to the story it came from, and its confidence is capped by how many independent publishers report it: aggregators do not count, and two feeds from one publisher count once. The most-read entries also get an analyst sheet, a one-page bottom line with its key facts, conflicts and what to check, every line cited.

Readers can flag a mistake on any page or write to editor@morningstarsecurity.com.

- This entry, live: https://morningstarsecurity.com/wiki/ai-generated-fake-cves-incident
- More incidents: https://morningstarsecurity.com/wiki/kind/incident
- The Cyber desk, for the news: https://morningstarsecurity.com/desk/cyber
- The whole wiki: https://morningstarsecurity.com/wiki
- About MorningStar Security: https://morningstarsecurity.com/about
- How the site is made: https://morningstarsecurity.com/editorial
- The newsletter: https://morningstarsecurity.com/newsletter

## Sources
1. AI slop pollutes the CVE pipeline with fake vulns · The Register: Security · 3 Aug 2026 · https://www.theregister.com/security/2026/08/03/ai-slop-pollutes-the-cve-pipeline-with-fake-vulns/5282462

---
Snapshot of https://morningstarsecurity.com/wiki/ai-generated-fake-cves-incident taken 22 Nov 2026 00:44 UTC. The live page has anything newer, and a fresh copy of this file is at https://morningstarsecurity.com/md/wiki/ai-generated-fake-cves-incident
