THREAT OPS › Threat News › [GHSA] GHSA-v4x8-3wr5-3wq8 (high) — 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
[GHSA] GHSA-v4x8-3wr5-3wq8 (high) — 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
GHSA-v4x8-3wr5-3wq8 Severity: high CVE: 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
`ReadWriteLock` and `AsyncReadWriteLock` (the SQLite-backed reader/writer lock) hand SQLite a name they do not control. On Linux the lock validates its database through a desc
MITRE ATT&CK techniques
Indicators of compromise
- b831496b0273ecd11bf02b8d080ca8b673a538c1sha1
- CVE-2026-112940cve
- https://www.sqlite.org/fileformat2.html#the_rollback_journalurl
Original source: https://github.com/advisories/GHSA-v4x8-3wr5-3wq8