Arbitrary file write via symlinked SQLite path
Published Aug 18, 2026 · Updated Aug 18, 2026
Insecure temporary file handling in Linuxfabrik Monitoring Plugins before 4.2.0 allows local users to write root-owned files via symlinked SQLite paths. In db_sqlite.py, connect() resolves database files at predictable names under shared /tmp, and the vulnerable code opens those paths without rejecting attacker-planted symlinks before sqlite3.connect() creates or updates the target. Exploitation requires control of the monitoring account and a sudo-authorized plugin execution path; affected deployments can suffer arbitrary file overwrite, service interrupt, or modification of an existing SQLite database through crafted journal or WAL files.
Summary
What happened
Insecure temporary file handling in Linuxfabrik Monitoring Plugins before 4.2.0 allows local users to write root-owned files via symlinked SQLite paths. In db_sqlite.py, connect() resolves database files at predictable names under shared /tmp, and the vulnerable code opens those paths without rejecting attacker-planted symlinks before sqlite3.connect() creates or updates the target. Exploitation requires control of the monitoring account and a sudo-authorized plugin execution path; affected deployments can suffer arbitrary file overwrite, service interrupt, or modification of an existing SQLite database through crafted journal or WAL files.
The record
- CVE
- CVE-2026-53759
- Published
- Aug 18, 2026
- Updated
- Aug 18, 2026
- Vendor
- Linuxfabrik
- Product
- Linuxfabrik Monitoring Plugins
- Classifications
- CWE-377, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-r35r-fpx2-jgr4 docker-stats symlink PoCproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo