RHSA-2026:57600HighCVSS 7.1

Red Hat Security Advisory: mrtg security update

Published
August 20, 2026
Last Modified
September 9, 2026

🔗 CVE IDs covered (1)

CVE-2026-72694 →

📋 Description

CVE-2026-72694 — mrtg: MRTG daemon symlink-following chown allows local privilege escalation via PID file path manipulation

🎯 Affected products14

  • Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-0:2.17.7-12.el9_8.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-0:2.17.7-12.el9_8.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-0:2.17.7-12.el9_8.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-0:2.17.7-12.el9_8.1.src as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-0:2.17.7-12.el9_8.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debuginfo-0:2.17.7-12.el9_8.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debuginfo-0:2.17.7-12.el9_8.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debuginfo-0:2.17.7-12.el9_8.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debuginfo-0:2.17.7-12.el9_8.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debugsource-0:2.17.7-12.el9_8.1.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debugsource-0:2.17.7-12.el9_8.1.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debugsource-0:2.17.7-12.el9_8.1.s390x as a component of Red Hat Enterprise Linux AppStream (v. 9)
  • mrtg-debugsource-0:2.17.7-12.el9_8.1.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 9)

✅ Remediation

For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 Workaround: To mitigate this issue, avoid starting the MRTG daemon as root with the `--daemon` option. Instead, configure MRTG to run directly as an unprivileged user. If root startup is strictly necessary, ensure that the PID file and its directory are owned by root and are not writable by unprivileged users, and prevent untrusted users from influencing the `--pid-file` path. Changes to service configuration may require a service restart to take effect.

🔗 References (4)