Live CVE & 0day intelligence

Sound the depths of every vulnerability.

Newly released CVEs across every platform — sleek to read, verbose on demand, and served raw as markdown for AI and agent ingestion. Severity reads as depth: the deeper the contact, the graver the threat.

Browse the feed For agents → /llms.txt

Depth = severity + exploitation

HadalCritical and actively exploited (CISA KEV / 0day)
AbyssalCritical with a public exploit or in-the-wild use
MidnightCritical, or high with PoC / in-the-wild
TwilightHigh severity, or a signal on a lesser flaw
SunlitLow / medium · no exploitation signal

70369

Tracked CVEs

6569

Critical

756

Exploited in wild

1072

Last 7 days

Trending now

Bluesky + Hacker News mentions, last 7 days

1CVE-2026-109618Critical· 9.2RCE via OOM corruption4896
2CVE-2026-109619Critical· 9.2RCE via stale global state2196
3CVE-2026-111497Critical· 9.8Brotli: Out-of-bounds write in the Brotli decoder ("Node2Shell") also affects the PyPI Brotli package1895
4CVE-2026-99999Critical· 9.3In the Linux kernel, the following vulnerability has been resolved: ipv4: validate checksum_start before completing checksum If a packet with bad checksum metadata gets into the ipv4 stack, skb_checksum_help can corrupt the network hea…963
5CVE-2026-110264Critical· 10.0Integer Overflow or Wraparound in GitLab367
6CVE-2026-91403Critical· 9.1Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: JSSE)262

This week's digest →All digests

Feed

7 matches

CVE-2025-6208Medium· 5.3

9mo ago

llama-index-core vulnerable to Uncontrolled Resource Consumption

▾ Sunlitllama-index-core · llama-index-coreEPSS 0.42%via OSV

CVE-2025-7647High· 7.3

1y ago

The llama-index-core package, up to version 0.12.44, contains a vulnerability in the `get_cache_dir()` function where a predictable, hardcoded directory path `/tmp/llama_index` is used on Linux systems without proper security controls

The llama-index-core package, up to version 0.12.44, contains a vulnerability in the `get_cache_dir()` function where a predictable, hardcoded directory path `/tmp/llama_index` is used on Linux systems without proper security controls. T…

▾ Twilightllama-index-core · llama-index-coreEPSS 0.15%via NVD

CVE-2025-5302High· 8.6

1y ago

LlamaIndex affected by a Denial of Service (DOS) in JSONReader

▾ Twilightllama-index-core · llama-index-coreEPSS 0.29%via OSV

CVE-2025-3108Medium· 5.0

1y ago

LlamaIndex has Incomplete Documentation of Program Execution related to JsonPickleSerializer component

▾ Sunlitllama-index-core · llama-index-coreEPSS 0.50%via OSV

CVE-2025-5472Medium· 6.5

1y ago

LlamaIndex vulnerable to DoS attack through uncontrolled recursive JSON parsing

▾ Sunlitllama-index-core · llama-index-coreEPSS 0.39%via OSV

CVE-2025-6209High· 7.5

1y ago

LlamaIndex vulnerable to Path Traversal attack through its encode_image function

▾ Twilightllama-index-core · llama-index-coreEPSS 0.62%via OSV

CVE-2024-3098Critical· 9.8

2y ago

llama-index-core Prompt Injection vulnerability leading to Arbitrary Code Execution

▾ Midnightllama-index-core · llama-index-coreEPSS 0.96%via OSV

From the blog

All posts →

Oct 27, 2026

VulnSea has moved to vulnsea.com (and what changed since September)

The beta is over. VulnSea now runs at vulnsea.com, every old beta link redirects to the same page, and your account, API keys and watchlists came with it. Plus a round of hardening, faster pages, and new request limits agents should know about.

Sep 8, 2026

What's new: open corpus, three new MCP tools, vendor advisories, package pages

A summary of everything that shipped over the last two weeks — the whole corpus is open, agents get change feeds, alias resolution and EPSS movers, and the data now includes CVE.org, vendor CSAF, aggregated exploits and per-source scores.

Jul 1, 2026

Wiring VulnSea into an agent: a hands-on tutorial

A step-by-step guide to plugging VulnSea into automated and agentic workflows — poll the delta, triage without burning tokens, match an SBOM, and let an MCP-native model do the reasoning.