CVE-2026-72694

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-11. a secondary CVSS source baseline 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

A fix is available — apply it.

A flaw was found in MRTG. When the MRTG daemon is started as a root user and subsequently drops privileges, a local, low-privileged attacker can exploit a symbolic link (symlink) following vulnerability. By influencing or pre-placing a symlink in the process ID (PID) file path, the attacker can trick the root process into changing the ownership of an arbitrary existing file to the daemon user. This can lead to local privilege escalation, allowing unauthorized access to or modification of sensitive files.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

August 11, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 11, 2026
Patch available. Sources: redhat.
redhat

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

https://bugzilla.redhat.com/show_bug.cgi?id=2460973
redhat Patch Available

CVE-2026-72694 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-72694

Vendor Advisories for CVE-2026-72694(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmrtg-0:2.17.7-1.el8_10.12026-09-09redhat
redhatmrtg-0:2.17.10-12.el10_2.12026-08-20redhat
redhatmrtg-0:2.17.7-12.el9_8.12026-08-20redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mrtg2.17.10-10 ... 2.17.10-9 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mrtg2.17.10-13, 2.17.10-13+deb13u1, 2.17.10-14, 2.17.10-15, 2.17.10-16——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mrtg2.17.10-13, 2.17.10-142.17.10-15—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 36× in last 7d / 159× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 216 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 19:43 UTCVendor advisory
  3. 2026-09-20 19:43 UTCGHSA enrichment
  4. 2026-09-20 02:58 UTCEG score recompute
  5. 2026-09-20 02:58 UTCVendor advisory
  6. 2026-09-20 02:58 UTCGHSA enrichment
  7. 2026-09-19 14:45 UTCVendor advisory
  8. 2026-09-19 14:45 UTCGHSA enrichment
  9. 2026-09-19 02:03 UTCEG score recompute
  10. 2026-09-19 02:03 UTCVendor advisory
  11. 2026-09-19 02:03 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-18 13:59 UTCVendor advisory
  14. 2026-09-18 13:59 UTCGHSA enrichment
  15. 2026-09-18 01:57 UTCVendor advisory
  16. 2026-09-18 01:57 UTCGHSA enrichment
  17. 2026-09-17 14:04 UTCVendor advisory
  18. 2026-09-17 14:04 UTCGHSA enrichment
  19. 2026-09-17 00:39 UTCEG score recompute
  20. 2026-09-17 00:39 UTCVendor advisory
  21. 2026-09-17 00:39 UTCGHSA enrichment
  22. 2026-09-16 14:08 UTCEPSS rescore
  23. 2026-09-16 05:15 UTCEPSS rescore
  24. 2026-09-16 02:20 UTCVendor advisory
  25. 2026-09-16 02:20 UTCGHSA enrichment
Show 75 more
  1. 2026-09-15 13:30 UTCEG score recompute
  2. 2026-09-15 13:30 UTCVendor advisory
  3. 2026-09-15 13:30 UTCGHSA enrichment
  4. 2026-09-15 03:12 UTCEPSS rescore
  5. 2026-09-15 01:19 UTCVendor advisory
  6. 2026-09-15 01:19 UTCGHSA enrichment
  7. 2026-09-14 13:26 UTCVendor advisory
  8. 2026-09-14 13:26 UTCGHSA enrichment
  9. 2026-09-14 01:33 UTCEG score recompute
  10. 2026-09-14 01:33 UTCVendor advisory
  11. 2026-09-14 01:33 UTCGHSA enrichment
  12. 2026-09-13 13:40 UTCVendor advisory
  13. 2026-09-13 13:40 UTCGHSA enrichment
  14. 2026-09-13 01:47 UTCEG score recompute
  15. 2026-09-13 01:47 UTCVendor advisory
  16. 2026-09-13 01:47 UTCGHSA enrichment
  17. 2026-09-12 15:02 UTCEPSS rescore
  18. 2026-09-12 13:53 UTCVendor advisory
  19. 2026-09-12 13:53 UTCGHSA enrichment
  20. 2026-09-12 02:00 UTCEG score recompute
  21. 2026-09-12 02:00 UTCVendor advisory
  22. 2026-09-12 02:00 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:06 UTCEG score recompute
  25. 2026-09-11 14:06 UTCVendor advisory
  26. 2026-09-11 14:06 UTCGHSA enrichment
  27. 2026-09-11 01:43 UTCVendor advisory
  28. 2026-09-11 01:43 UTCGHSA enrichment
  29. 2026-09-10 13:50 UTCEG score recompute
  30. 2026-09-10 13:50 UTCVendor advisory
  31. 2026-09-10 13:50 UTCGHSA enrichment
  32. 2026-09-10 09:35 UTCEPSS rescore
  33. 2026-09-10 01:57 UTCVendor advisory
  34. 2026-09-10 01:57 UTCGHSA enrichment
  35. 2026-09-09 10:30 UTCEG score recompute
  36. 2026-09-09 10:30 UTCVendor advisory
  37. 2026-09-09 10:30 UTCGHSA enrichment
  38. 2026-09-09 09:30 UTCEG score recompute
  39. 2026-09-09 09:30 UTCVendor advisory
  40. 2026-09-09 09:30 UTCGHSA enrichment
  41. 2026-09-09 05:47 UTCEG score recompute
  42. 2026-09-09 05:47 UTCVendor advisory
  43. 2026-09-09 05:47 UTCGHSA enrichment
  44. 2026-09-08 22:01 UTCEPSS rescore
  45. 2026-09-08 05:03 UTCVendor advisory
  46. 2026-09-08 05:03 UTCGHSA enrichment
  47. 2026-09-07 17:07 UTCEG score recompute
  48. 2026-09-07 17:07 UTCVendor advisory
  49. 2026-09-07 17:07 UTCGHSA enrichment
  50. 2026-09-06 15:30 UTCEG score recompute
  51. 2026-09-06 15:30 UTCVendor advisory
  52. 2026-09-06 15:30 UTCGHSA enrichment
  53. 2026-09-06 13:48 UTCEPSS rescore
  54. 2026-09-06 03:19 UTCEG score recompute
  55. 2026-09-06 03:19 UTCVendor advisory
  56. 2026-09-06 03:18 UTCGHSA enrichment
  57. 2026-09-05 15:24 UTCVendor advisory
  58. 2026-09-05 15:23 UTCGHSA enrichment
  59. 2026-09-05 01:47 UTCEG score recompute
  60. 2026-09-05 01:47 UTCVendor advisory
  61. 2026-09-05 01:47 UTCGHSA enrichment
  62. 2026-09-04 08:19 UTCEG score recompute
  63. 2026-09-04 08:19 UTCVendor advisory
  64. 2026-09-04 08:19 UTCGHSA enrichment
  65. 2026-09-04 05:07 UTCEPSS rescore
  66. 2026-09-03 16:36 UTCVendor advisory
  67. 2026-09-03 16:36 UTCGHSA enrichment
  68. 2026-09-03 01:57 UTCEG score recompute
  69. 2026-09-03 01:57 UTCVendor advisory
  70. 2026-09-03 01:57 UTCGHSA enrichment
  71. 2026-09-02 14:12 UTCEPSS rescore
  72. 2026-09-02 02:00 UTCEG score recompute
  73. 2026-09-02 02:00 UTCVendor advisory
  74. 2026-09-02 02:00 UTCGHSA enrichment
  75. 2026-09-01 13:54 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-72694?
CVE-2026-72694 is a high vulnerability published on August 11, 2026. A flaw was found in MRTG. When the MRTG daemon is started as a root user and subsequently drops privileges, a local, low-privileged attacker can exploit a symbolic link (symlink) following vulnerability. By influencing or pre-placing a symlink in the process ID (PID) file path, the attacker can…
When was CVE-2026-72694 disclosed?
CVE-2026-72694 was first published in the National Vulnerability Database on August 11, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-72694 actively exploited?
CVE-2026-72694 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 97.0% of all scored CVEs.
What is the CVSS score of CVE-2026-72694?
CVE-2026-72694 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-72694?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-72694, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-72694

Explore →

Is Your Infrastructure Affected by CVE-2026-72694?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs