Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage

Every public CVE, as it is published

The whole CVE List, enriched with NVD scores, CISA's known exploited catalog and EPSS exploit probabilities. Updated every few minutes; last read 9 min ago.

At a glance

Published CVEs; rejected ones are not counted.

  • 401,234All CVEsplus 19,120 rejected
  • 498Last 24 hours2,795 in the last 7 days
  • 16,901Last 30 days1,543 of them critical
  • 1,768Known exploitedin the CISA KEV catalog

CVEs published per year

All time, by publication date in UTC; follows the filter above.

  • Critical
  • High
  • Medium
  • Low
  • Not scored
The numbers of every bucket are in the table under the chart.
Show the numbers as a table
Matching CVEs per period and severity, newest first
PeriodCriticalHighMediumLowNot scoredTotalCumulative
2026033701313

Latest CVEs

13 CVEs, newest first

CVEs, newest first
Title
CVE-2026-77642
tor before 0.4.9.9 was prone to an out-of-bounds write when parsing a consensus or detached signature with unexpected signature digest type. Impact is minor…torproject · Tor
High7.5
CVE-2026-77641
tor before 0.4.9.9 was prone to a NULL write after free when sending a CONFLUX_SWITCH cell fails. The return value of relay_send_command_from_edge() was…torproject · Tor
Medium6.5
CVE-2026-77640
tor before 0.4.9.9 was prone to an infinite loop when decompressing a truncated zlib/gzip stream with done=1. A truncated stream never reaches Z_STREAM_END,…torproject · Tor
Low3.7
CVE-2026-77639
Tor before 0.4.9.9 was prone to a compression bomb bypass where an attacker could concatenate many gzip or zlib sub-streams, each just under the per-stream…torproject · Tor
Medium5.3
CVE-2026-77638
Tor before 0.4.9.11 is prone to a race condition where in just the right circumstances a rendezvous point could man-in-the-middle (impersonate) the onion…torproject · Tor
High8.9
CVE-2026-77587
Tor before 0.4.9.11 is prone to a use-after-free (and potential double free) of a conflux object when a recovery leg revives a conflux set whose last linked…torproject · Tor
Medium5.9
CVE-2026-77584
Tor before 0.4.9.10 did not reject a CONFLUX_LINK cell that arrives on a circuit which already has attached streams. A malicious client could send a…torproject · Tor
High7.0
CVE-2026-44603
Tor before 0.4.9.7 has an out-of-bounds read by one byte via a malformed BEGIN cell, aka TROVE-2026-007.torproject · Tor
Low3.7
CVE-2026-44602
Tor before 0.4.9.7 has a NULL pointer dereference when a CERT cell is received out of order, aka TROVE-2026-006.torproject · Tor
Low3.7
CVE-2026-44601
Tor before 0.4.9.7, when circuit queue memory pressure exists, can experience a client crash because of a double close of a circuit, aka TROVE-2026-009.torproject · Tor
Low3.7
CVE-2026-44600
Tor before 0.4.9.7 mishandles accounting of the conflux out-of-order queue during the clearing of a queue, aka TROVE-2026-010.torproject · Tor
Low3.7
CVE-2026-44599
Tor before 0.4.9.7 can attempt or accept BEGIN_DIR via conflux legs, aka TROVE-2026-008.torproject · Tor
Low3.7
CVE-2026-44597
Tor before 0.4.9.7 has an out-of-bounds read when an END, a TRUNCATE, or a TRUNCATED cell lacks a reason in its payload, aka TROVE-2026-011.torproject · Tor
Low3.7