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 2 min ago.

At a glance

Published CVEs; rejected ones are not counted.

  • 401,273All CVEsplus 19,140 rejected
  • 466Last 24 hours2,759 in the last 7 days
  • 16,923Last 30 days1,555 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
20260114401920
20250010011

Latest CVEs

20 CVEs, newest first

CVEs, newest first
Title
CVE-2026-112908
filelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live holdtox-dev · filelock
Medium5.3
CVE-2026-112938
filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user choosestox-dev · filelock
Medium5.8
CVE-2026-112907
filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale breaktox-dev · filelock
Low2.5
CVE-2026-112913
filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its databasetox-dev · filelock
Low3.3
CVE-2026-112910
filelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACLtox-dev · filelock
Medium5.3
CVE-2026-112941
filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the locktox-dev · filelock
Low3.3
CVE-2026-112940
filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own filestox-dev · filelock
High7.1
CVE-2026-112939
filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable markertox-dev · filelock
Medium4.7
CVE-2026-112937
filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory nametox-dev · filelock
Medium6.1
CVE-2026-112936
filelock: ReadWriteLock follows a symlink at the lock path into SQLitetox-dev · filelock
Medium6.1
CVE-2026-112935
filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holderstox-dev · filelock
Medium4.7
CVE-2026-112934
filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its recordtox-dev · filelock
Medium6.1
CVE-2026-112915
filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeouttox-dev · filelock
Medium5.5
CVE-2026-112914
filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directorytox-dev · filelock
Medium5.3
CVE-2026-112912
filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock takertox-dev · filelock
Low2.5
CVE-2026-112911
filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusiontox-dev · filelock
Medium6.3
CVE-2026-112909
filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock pathtox-dev · filelock
Medium6.1
CVE-2026-112906
filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reusetox-dev · filelock
Medium4.7
CVE-2026-22701
filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLocktox-dev · filelock
Medium5.3
CVE-2025-68146
filelock has TOCTOU race condition that allows symlink attacks during lock file creationtox-dev · filelock
Medium6.3