Vulnerabilidades en tox-dev

20 resultados
CVE-2026-112934MEDIUMfilelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its recordEPSS 0.2%CVE-2026-112936MEDIUMfilelock: ReadWriteLock follows a symlink at the lock path into SQLiteEPSS 0.2%CVE-2026-112909MEDIUMfilelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock pathEPSS 0.2%CVE-2026-112915MEDIUMfilelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeoutEPSS 0.2%CVE-2026-112912LOWfilelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock takerEPSS 0.2%CVE-2025-68146MEDIUMfilelock has TOCTOU race condition that allows symlink attacks during lock file creationEPSS 0.2%CVE-2026-112940HIGHfilelock 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 filesEPSS 0.2%CVE-2026-112906MEDIUMfilelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuseEPSS 0.2%CVE-2026-112937MEDIUMfilelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory nameEPSS 0.2%CVE-2026-112910MEDIUMfilelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACLEPSS 0.2%CVE-2026-112914MEDIUMfilelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directoryEPSS 0.2%CVE-2026-112911MEDIUMfilelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusionEPSS 0.1%CVE-2026-112939MEDIUMfilelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable markerEPSS 0.1%CVE-2026-112935MEDIUMfilelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holdersEPSS 0.1%CVE-2026-112941LOWfilelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lockEPSS 0.1%CVE-2026-22701MEDIUMfilelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLockEPSS 0.1%CVE-2026-112908MEDIUMfilelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live holdEPSS 0.1%CVE-2026-112913LOWfilelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its databaseEPSS 0.1%CVE-2026-112938MEDIUMfilelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user choosesEPSS 0.1%CVE-2026-112907LOWfilelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale breakEPSS 0.1%