Skip to content
major vulnerability· requires attention

Affects VMware Aria Operations (enterprise software); unauthenticated RCE could disrupt IT ops across organizations.

Applications

CVE-2026-22719

8.1
High
KEV · Exploited in wildEPSS 17%Patch availableFeb 26, 2026

Unauthenticated command injection leads to RCE in VMware Aria Operations

common questions

Is CVE-2026-22719 being exploited?

Yes. CVE-2026-22719 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-22719?

CVE-2026-22719 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-22719?

Yes. A fix has been recorded for CVE-2026-22719. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-22719 affect?

CVE-2026-22719 affects VMware Aria Operations. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-22719?

Patch per advisory; apply documented workarounds.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
VMware Aria Operations
impact

Unauthenticated RCE via command injection; attacker can run arbitrary commands on the appliance during migrations.

action required

Patch when possible

affected versions
VMware Telco Cloud Infrastructure
  • affected>= 2.0 and < 5.2.3
vendor says fixed in5.2.3
VMware Telco Cloud Platform
  • affected>= 2.0 and < 5.2.3
vendor says fixed in5.2.3
VMware VMware Aria Operations
  • affected>= 8.18.x and < 8.18.6
VMware VMware Cloud Foundation Operations
  • affected>= 9.0 and < 9.0.2
  • affected>= 4.0 and < 5.2.3
vendor says fixed in9.0.2, 5.2.3

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free