tox-dev vulnerabilities

CVEs per yearBy the year they were published

1. 20251
2. 202614

Newest CVEs

• 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 lock

  tox-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 files

  tox-dev · filelock

  High7.1
• CVE-2026-112939

  filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker

  tox-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 name

  tox-dev · filelock

  Medium6.1
• CVE-2026-112936

  filelock: ReadWriteLock follows a symlink at the lock path into SQLite

  tox-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 holders

  tox-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 record

  tox-dev · filelock

  Medium6.1
• CVE-2026-112915

  filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout

  tox-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 directory

  tox-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 taker

  tox-dev · filelock

  Low2.5