CVE-2026-73973
MEDIUMDescription
Linuxfabrik Monitoring Plugins provides monitoring plugins for Icinga, Nagios, and related systems. Prior to version 7.0.0, check-plugins/logfile/logfile accepted a free-form --filename path and opened it as root when invoked through the shipped nagios or icinga sudoers allowlist, without confining the resolved path to /var/log. An attacker who controls the monitoring account can select a root-readable file such as /etc/shadow and use --warning-regex . while leaving SUPPRESS_OUTPUT false, causing each nonempty line to be collected in warn_matches and returned through lib.base.oao(). The vulnerable flow passes the expanded scan_path directly to open(), and neither real-path containment nor an allowlist protects the sink. The same fix also confines mysql-logfile and openvpn-client-list paths, allows only documented log roots, and resolves symlinks and parent-directory traversal before checking containment. This issue is fixed in version 7.0.0.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 12% of all known CVEs.
References
Related Vulnerabilities
Other CWE-22 (Path Traversal) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-23897 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2023-32315 | High | 8.6 | 100% | KEV | Fix |
| CVE-2022-29464 | Critical | 9.8 | 100% | KEV + Ransom | - |
| CVE-2021-26086 | Medium | 5.3 | 100% | KEV | Fix |
| CVE-2021-22005 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
| CVE-2020-5902 | Critical | 9.8 | 100% | KEV + Ransom | Fix |
Common questions
How do I fix CVE-2026-73973?
No published fix for CVE-2026-73973 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2026-73973 being actively exploited?
Not that we know of. CVE-2026-73973 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.21% is the estimated probability that it will be exploited in the next 30 days. That is higher than 12% of all scored CVEs.
How severe is CVE-2026-73973?
CVE-2026-73973 has a CVSS v3 base score of 5.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2026-73973
Markdown
[](https://tridentstack.com/cve/CVE-2026-73973)HTML
<a href="https://tridentstack.com/cve/CVE-2026-73973"><img src="https://tridentstack.com/cve/badge/CVE-2026-73973.svg" alt="CVE-2026-73973"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-08-19.