Local root file read via --test path
Published Aug 18, 2026 · Updated Aug 19, 2026
Path traversal in Linuxfabrik linuxfabrik-lib before 6.1.0 allows local users to read root-readable files via --test. In Linuxfabrik Monitoring Plugins before 7.0.0, lib.lftest.test() treats the first or second CSV element of the hidden but live --test argument as a filesystem path and returns that file's contents as simulated stdout or stderr without confining resolution to a plugin fixture directory; network-bonding and openstack-swift-stat originally bypassed the helper with direct reads. Reachability requires control of the nagios or icinga account on systems that allow the affected plugins to run through passwordless sudo, letting deb-updates disclose whole files and other plugins expose filtered content or a root file existence and readability oracle.
Summary
What happened
Path traversal in Linuxfabrik linuxfabrik-lib before 6.1.0 allows local users to read root-readable files via --test. In Linuxfabrik Monitoring Plugins before 7.0.0, lib.lftest.test() treats the first or second CSV element of the hidden but live --test argument as a filesystem path and returns that file's contents as simulated stdout or stderr without confining resolution to a plugin fixture directory; network-bonding and openstack-swift-stat originally bypassed the helper with direct reads. Reachability requires control of the nagios or icinga account on systems that allow the affected plugins to run through passwordless sudo, letting deb-updates disclose whole files and other plugins expose filtered content or a root file existence and readability oracle.
The record
- CVE
- CVE-2026-73974
- Published
- Aug 18, 2026
- Updated
- Aug 19, 2026
- Vendor
- Linuxfabrik
- Product
- Linuxfabrik Monitoring Plugins
- Classifications
- CWE-269, CWE-22, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 18, 2026CVE publishedPublication date reported by the CVE source.
- Aug 19, 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=< 7.0.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
- OSV proof-of-concept commands for GHSA-rh9c-rqvg-f7prproof 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