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

30474

Tracked CVEs

2988

Critical

380

Exploited in wild

4929

Last 7 days

Trending now

Bluesky + Hacker News mentions, last 7 days

1CVE-2026-85046High· 8.8Type confusion in V8 in Google Chrome prior to 152.0.7977.82 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page874
2CVE-2026-58704High· 8.8In Cellular Modem, there is a possible permission bypass due to a logic error in the code373
3CVE-2026-69836Critical· 10.0Microsoft Entra ID Remote Code Execution Vulnerability267
4CVE-2026-66747Critical· 9.8Zbtlink router firmware ships an embedded remote-control implant, ENDLESSDOORS, present in every published build across the product line266
5CVE-2026-18963Critical· 9.1A flaw was found in the reset-credentials flow of the keycloak-services component, which is the core engine for identity and access management in Red Hat Build of Keycloak263

This week's digest →All digests

Feed

345 matches

CVE-2026-65388High· 7.5

6d ago

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host. This vulnerability is addressed in contai…

Sound the depths of every vulnerability.

Trending now

Feed

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host

A permissions issue was addressed with improved path validation

This issue was addressed with improved checks

The issue was addressed with improved memory handling

A use after free issue was addressed with improved memory management

The issue was addressed with improved memory handling

An authorization issue was addressed with improved state management

An out-of-bounds read was addressed with improved bounds checking

A buffer overflow was addressed with improved bounds checking

An integer overflow was addressed with improved input validation

An authorization issue was addressed with improved state management

A permissions issue was addressed with additional restrictions

An authorization issue was addressed with improved access control

A permissions issue was addressed with additional restrictions

A permissions issue was addressed with additional restrictions

A permissions issue was addressed with improved path validation

An integer overflow was addressed with improved input validation

A permissions issue was addressed with additional restrictions

The issue was addressed with improved checks

A denial-of-service issue was addressed with improved input validation

The issue was addressed with improved checks

A use-after-free issue was addressed with improved memory management

An authorization issue was addressed with improved state management

A logic issue was addressed with improved state management

A privacy issue was addressed by moving sensitive data

From the blog

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

Wiring VulnSea into an agent: a hands-on tutorial

VulnSea is live

Sound the depths of every vulnerability.

Trending now

Feed

A remote attacker who controls a container registry may be able to direct a client's token request to a host of the attacker's choice, and disclose the victim's registry credentials to that host

A permissions issue was addressed with improved path validation

This issue was addressed with improved checks

The issue was addressed with improved memory handling

A use after free issue was addressed with improved memory management

The issue was addressed with improved memory handling

An authorization issue was addressed with improved state management

An out-of-bounds read was addressed with improved bounds checking

A buffer overflow was addressed with improved bounds checking

An integer overflow was addressed with improved input validation

An authorization issue was addressed with improved state management

A permissions issue was addressed with additional restrictions

An authorization issue was addressed with improved access control

A permissions issue was addressed with additional restrictions

A permissions issue was addressed with additional restrictions

A permissions issue was addressed with improved path validation

An integer overflow was addressed with improved input validation

A permissions issue was addressed with additional restrictions

The issue was addressed with improved checks

A denial-of-service issue was addressed with improved input validation

The issue was addressed with improved checks

A use-after-free issue was addressed with improved memory management

An authorization issue was addressed with improved state management

A logic issue was addressed with improved state management

A privacy issue was addressed by moving sensitive data

From the blog

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

Wiring VulnSea into an agent: a hands-on tutorial

VulnSea is live