CVE-2025-22220VulnerabilityPublished 30 Jan 2025Updated 26 Feb 2026

CVE-2025-22220: VMware Aria Operations for Logs · Vulnerability

Affects VMware Aria Operations for LogsSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 9.0.0 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.0.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Jan 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade VMware Aria Operations for Logs to 9.0.0.

Affected software

Product	Affected	Fixed in
VMware VMware Aria Operations for Logs	Affected >=8.0.0 <9.0.0	Fixed in 9.0.0

AI-suggested

1. Restrict network access to the VMware Aria Operations for Logs API to trusted and authenticated users only, using network segmentation and firewall rules. 2. Implement strict access controls and role-based access management to minimize the number of users with non-administrative privileges who can access the API. 3. Monitor API access logs for unusual or unauthorized administrative operations that could indicate exploitation attempts. 4. Once VMware releases an official patch or update addressing CVE-2025-22220, apply it promptly in all affected environments. 5. Employ multi-factor authentication (MFA) for all users accessing the system to reduce the risk of compromised credentials being used to exploit this vulnerability. 6. Conduct regular security audits and penetration testing focused on privilege escalation vectors within the logging and monitoring infrastructure. 7. Consider deploying additional integrity monitoring tools on log data and configurations to detect unauthorized changes early.

Description

VMware Aria Operations for Logs contains a privilege escalation vulnerability. A malicious actor with non-administrative privileges and network access to Aria Operations for Logs API may be able to perform certain operations in the context of an admin user.

Impact

The primary impact of CVE-2025-22220 is on the integrity of VMware Aria Operations for Logs environments. An attacker exploiting this vulnerability can perform unauthorized administrative operations, potentially altering logs, configurations, or operational data. This can undermine trust in the monitoring and logging infrastructure, complicate incident investigations, and potentially hide malicious activities. Since the vulnerability does not affect confidentiality or availability directly, data leakage or service disruption is unlikely. However, the ability to escalate privileges within a critical monitoring tool can facilitate further attacks or persistence within an organization's environment. Organizations relying heavily on VMware Aria Operations for Logs for security monitoring, compliance, and operational awareness are at risk of having their log data manipulated, which could have cascading effects on security posture and operational decision-making.

CWE-269Improper Privilege Management (opens in a new tab)
Class weaknessLikelihood of exploit: MediumOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Separation of Privilege
Follow the principle of least privilege when assigning access rights to entities in a software system.
Architecture and Design · Separation of Privilege
Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Restful Privilege Elevation (opens in a new tab)
Privilege Abuse (opens in a new tab)
Privilege Escalation (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/25329 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 20:32 UTC

WeaknessesCWE-269

Technical details

References

Community reviews

Related threats