Virtual Traffic Manager
Auto-added after CISA flagged Virtual Traffic Manager as actively exploited (KEV catalog). Version and lifecycle mapping is pending review, so this is assessed at the product level and is never reported as a confident "healthy".
Summary iPlain-English security verdict for Virtual Traffic Manager, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
Virtual Traffic Manager currently scores 92/100 — healthy. No tracked vulnerabilities are currently known to be exploited in the wild. It's on the latest patch with no significant known issues — keep it current.
The known vulnerabilities
IsItPatched tracks 1 known vulnerability in Ivanti Virtual Traffic Manager disclosed in 2026. CVE-2026-8051 is a high-severity os command injection vulnerability (CVSS 7.2). Apply Ivanti's latest security update for Virtual Traffic Manager to stay protected.
Disclosure trend iNew CVEs published for Virtual Traffic Manager each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
No urgent unpatched issues identified. ✓
Get alerted about Virtual Traffic Manager
Be emailed the moment Virtual Traffic Manager gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for Virtual Traffic Manager — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is Virtual Traffic Manager safe and patched?
Virtual Traffic Manager currently scores 92/100 — healthy. No tracked vulnerabilities are currently known to be exploited in the wild. It's on the latest patch with no significant known issues — keep it current.
What should I do about Virtual Traffic Manager now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against Ivanti's official advisory.
Why is Virtual Traffic Manager listed on IsItPatched?
Virtual Traffic Manager was added automatically because CISA's Known Exploited Vulnerabilities (KEV) catalog flagged it as actively exploited in the wild. IsItPatched tracks its known CVEs, severity (CVSS), exploitation probability (EPSS) and KEV status from public data; its version and lifecycle mapping is verified over time.
Has Virtual Traffic Manager been actively exploited?
Yes. CISA added Virtual Traffic Manager to its Known Exploited Vulnerabilities (KEV) catalog after confirming exploitation in the wild — the triggering vulnerability is CVE-2024-7593. Make sure you are running a patched, supported version of Virtual Traffic Manager and confirm it against Ivanti's security advisory.
Similar software we track
More from Ivanti tracked on IsItPatched.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Ivanti's official advisory before you patch or upgrade.