CVEReports
CVEReports

Automated vulnerability intelligence platform. Comprehensive reports for high-severity CVEs generated by AI.

Product

  • Home
  • Sitemap
  • RSS Feed

Company

  • About
  • Contact
  • Privacy Policy
  • Terms of Service

© 2026 CVEReports. All rights reserved.

Made with love by Amit Schendel & Alon Barad



CVE-2026-73974

CVE-2026-73974: Local Path Traversal and Privilege Escalation in Linuxfabrik Monitoring Plugins

Alon Barad
Alon Barad
Software Engineer

Aug 18, 2026·5 min read·19 visits

Executive Summary (TL;DR)

A local path traversal flaw in the testing parameters of Linuxfabrik Monitoring Plugins allows unprivileged users to read sensitive files as root.

CVE-2026-73974 is a local path traversal vulnerability in linuxfabrik-lib and Linuxfabrik Monitoring Plugins. Under standard monitoring configurations running with elevated privileges via sudo, this flaw can be exploited by an unprivileged local user to read arbitrary root-only files, resulting in local privilege escalation.

Vulnerability Overview

CVE-2026-73974 is a directory traversal and improper privilege management vulnerability affecting the Linuxfabrik monitoring ecosystem. This ecosystem includes the Python-based utility library linuxfabrik-lib and its corresponding suite of check plugins. These plugins are commonly integrated into enterprise monitoring frameworks such as Nagios, Icinga, or Sensu.

Under standard monitoring configurations, plugins frequently require elevated privileges to read low-level hardware or system configurations. To facilitate this, administrators regularly configure passwordless sudo access for the dedicated, unprivileged monitoring service accounts, such as nagios or icinga.

An unprivileged local user who has compromised the monitoring service account can leverage a hidden, production-accessible parameter named --test. By supplying a malformed input containing traversal sequences or absolute paths to this parameter, the root-privileged plugin can be forced to disclose the contents of arbitrary restricted files, leading to complete local privilege escalation.

Root Cause Analysis

The root cause of the vulnerability lies in insecure input handling and path resolution within the testing harness library helper lib.lftest.test(). This function was designed to ingest a mock file parameter via the --test command-line flag and simulate output streams during automated testing or validation environments.

When the utility received a file path via --test, it invoked the native Python method os.path.isfile() to confirm the path resolved to a valid file on disk. Upon confirmation, it read the file using the internal disk.read_file() method. This design failed to implement directory containment verification, making it susceptible to path traversal.

In addition to the shared library helper flaw, specific plugins directly interacted with the local file system using the command line arguments without sanitization. The network-bonding plugin directly invoked Python's native open() method on the string provided via --test. Similarly, the openstack-swift-stat plugin leveraged lib.disk.read_file() directly, bypassing the common library testing logic entirely.

A tertiary vulnerability exists within the SQLite database utility helper db_sqlite.py. The get_db_path() function constructed paths using caller-controlled database names. Because it lacked sanity checks to restrict inputs to base file names, path traversal markers like .. could be used to manipulate database files outside of the designated secured directory.

Code and Patch Deep-Dive

The fix for CVE-2026-73974 was implemented by modifying db_sqlite.py and lftest.py in linuxfabrik-lib to enforce strict containment. In db_sqlite.py, the get_db_path() function now explicitly rejects any database filenames that are not plain basenames. This prevents attackers from traversing out of the hardened directories.

The lftest.py library helper was restructured to route all reads through a new private function _read_fixture(). This helper anchors path resolution to the actual location of the running plugin script using sys.argv[0] rather than the current working directory, which is attacker-controlled. The path is then canonicalized using os.path.realpath() and validated to ensure it resides within the safe <plugin_dir>/unit-test/ directory.

The following diagram illustrates the path resolution flow before and after the application of the patch:

Exploitation Methodology

An exploitation scenario requires an attacker to have established local shell access with the privileges of a monitoring service user, such as nagios. The attacker first audits the sudo permissions to identify which Linuxfabrik plugins are whitelisted for passwordless sudo execution.

Upon identifying a whitelisted plugin, such as /usr/lib/nagios/plugins/deb-updates, the attacker invokes the binary under sudo while passing the target file path through the --test parameter. For example, executing sudo deb-updates --test /etc/shadow,1 forces the root-privileged process to read /etc/shadow.

Because the unpatched plugin handles the --test argument as a path to mock standard output or standard error results, the library parses the file and outputs its contents to the console. The attacker can then extract system password hashes, private SSH keys, or administrative configuration files.

Remediation and Detection

Immediate remediation requires updating the linuxfabrik-lib package to version 6.1.0 or 6.0.1. Simultaneously, the Linuxfabrik Monitoring Plugins package must be updated to version 7.0.0 or later. These versions incorporate the strict basename and directory containment checks.

If patching cannot be performed immediately, temporary workarounds must be applied. Administrators should review /etc/sudoers files to ensure that monitoring plugins are not granted wildcards or permissive invocation privileges. Wherever possible, restrict write permissions to the plugin installation directories to prevent low-privileged users from tampering with files.

Intrusion detection can be achieved by monitoring host audits and shell history logs. Security teams should deploy auditd rules or SIEM detection patterns that trigger alerts when system monitoring accounts execute commands containing the --test parameter in conjunction with path traversal characters or sensitive directory paths like /etc/ or /root/.

Official Patches

Linuxfabriklinuxfabrik-lib containment fix
Linuxfabrikmonitoring-plugins integration fix

Fix Analysis (2)

Technical Appendix

CVSS Score
5.5/ 10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected Systems

linuxfabrik-libLinuxfabrik Monitoring Plugins

Affected Versions Detail

Product
Affected Versions
Fixed Version
linuxfabrik-lib
Linuxfabrik
< 6.1.06.1.0
monitoring-plugins
Linuxfabrik
< 7.0.07.0.0
AttributeDetail
CWE IDCWE-22 / CWE-269
Attack VectorLocal
CVSS5.5
EPSSN/A
ImpactLocal Privilege Escalation
Exploit StatusPoC
KEV StatusNot Listed

MITRE ATT&CK Mapping

T1083File and Directory Discovery
Discovery
T1005Data from Local System
Collection
T1068Exploitation for Privilege Escalation
Privilege Escalation
CWE-22
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Vulnerability Timeline

Security patches committed to Linuxfabrik/lib and Linuxfabrik/monitoring-plugins
2026-07-08
Joint security advisory published and CVE-2026-73974 assigned
2026-08-18

References & Sources

  • [1]GHSA-rh9c-rqvg-f7pr Security Advisory
  • [2]linuxfabrik-lib v6.1.0 Release Notes
  • [3]Linuxfabrik Monitoring Plugins v7.0.0 Release Notes

Attack Flow Diagram

Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.

More Reports

•about 5 hours ago•CVE-2026-58254
6.5

CVE-2026-58254: Authorization Bypass in NATS Server Message Tracing for Leaf Node Connections

NATS Server prior to versions 2.12.8 and 2.14.3 contains an incorrect authorization vulnerability (CWE-863) in its message tracing subsystem. When evaluating whether a connection is permitted to publish trace events to a destination subject specified in the Nats-Trace-Dest header, the server only checks standard client permissions and omits permission checks for leaf node connections. This allows a connected leaf node operator with restricted publishing privileges to emit internal trace events to unauthorized subjects and suppress standard message delivery using the Nats-Trace-Only header.

Alon Barad
Alon Barad
4 views•10 min read
•about 6 hours ago•CVE-2026-63341
7.5

CVE-2026-63341: Unauthenticated Denial of Service via Unbounded Topic Depth in Aedes MQTT Broker

CVE-2026-63341 is a high-severity Denial of Service (DoS) vulnerability in the Aedes MQTT broker for Node.js affecting all versions prior to 1.1.1. The flaw stems from missing input validation on the hierarchical depth of incoming MQTT topic strings before they are passed to the underlying topic-matching engine, qlobber. Because qlobber enforces a hardcoded limit of 100 topic levels and throws a synchronous exception when this threshold is exceeded, an attacker can send a single MQTT packet containing 101 or more forward-slash-separated levels to trigger an uncaught exception that immediately terminates the Node.js broker process.

Alon Barad
Alon Barad
5 views•12 min read
•about 7 hours ago•CVE-2026-61725
6.1

CVE-2026-61725: Path Traversal and Arbitrary File Overwrite in sevenz-rust2

CVE-2026-61725 is a path traversal vulnerability (CWE-22) in the sevenz-rust2 Cargo package prior to version 0.21.1. The vulnerability occurs because the decompression utility fails to validate or sanitize archive entry filenames before joining them with the destination directory path via std::path::Path::join. An attacker who supplies a crafted 7z archive containing parent directory traversal sequences or absolute paths can write or overwrite arbitrary files on the host filesystem with the privileges of the extracting process.

Alon Barad
Alon Barad
5 views•12 min read
•about 8 hours ago•CVE-2026-77309
8.8

CVE-2026-77309: Unauthenticated Remote Code Execution in NASA-AMMOS AIT-GUI via Incomplete File Cleanup and Path Traversal

CVE-2026-77309 (GHSA-jrjx-9jjw-747m) is a high-severity unauthenticated remote code execution vulnerability affecting NASA-AMMOS AIT-GUI versions 1.0.0 through 2.5.0. The flaw results from chaining an incomplete file cleanup error in the telemetry query endpoint (/tlm/query) with a directory traversal flaw in the script execution endpoint (/script/run). An attacker on an adjacent network can stage arbitrary Python statements into a static file on disk and execute that file under the privileges of the AIT-GUI web server process.

Amit Schendel
Amit Schendel
4 views•10 min read
•about 9 hours ago•CVE-2026-77332
2.3

CVE-2026-77332: Surfaced-Memory Envelope Injection and Stored Prompt Injection in memtomem-stm

A vulnerability classified under CWE-116 (Improper Encoding or Escaping of Output) exists in memtomem-stm versions 0.1.0 through 0.1.33. The software acts as a Model Context Protocol (MCP) short-term memory proxy gateway for AI agent architectures. When surfacing retrieved memories and scratchpad items into downstream Large Language Model (LLM) context envelopes, the SurfacingFormatter component fails to properly sanitize untrusted memory attributes. An attacker with the ability to plant untrusted content into the agent's long-term or working memory store can inject arbitrary structural delimiters, close the <surfaced-memories> XML boundary prematurely, visually obscure instructions using Unicode bidirectional overrides, and execute stored prompt injection attacks against downstream LLM agents.

Alon Barad
Alon Barad
7 views•10 min read
•about 10 hours ago•CVE-2026-77331
2.0

CVE-2026-77331: Race Condition and Session State Corruption in memtomem-stm

CVE-2026-77331 (GHSA-72jh-722p-rqr3) is a concurrency and session-state synchronization vulnerability in memtomem-stm, a short-term memory proxy gateway for AI agents. In versions 0.1.2 prior to 0.1.34, concurrent Model Context Protocol (MCP) Remote Procedure Call (RPC) failures or mid-flight task cancellations can initiate duplicate reconnect loops and permit dirty or cancelled transport sessions to be reused. This deficiency results in session-state integrity loss and local service degradation.

Amit Schendel
Amit Schendel
5 views•9 min read