The vRealize Operations Manager API (8.x prior to 8.5) contains a broken access control vulnerability leading to unauthenticated API access.

published 2021-08-30 5y ago modified 2026-06-17 4mo ago also EUVD-2021-9194

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits: 0; none known

The vRealize Operations Manager API (8.x prior to 8.5) contains a broken access control vulnerability leading to unauthenticated API access. An unauthenticated malicious actor with network access to the vRealize Operations Manager API can add new nodes to existing vROps cluster.

Patch / fix

fixed in 1 links 1

vmware vrealize_operations_manager 8.5.0

vmware.com/security/advisories/VMSA-2021-0018.html advisory

Is CVE-2021-22025 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.81% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

n/a VMware vRealize Operations

Classification

Weakness

CWE-287 Improper Authentication

Technology feeds

VMware rss critical rss

References

vmware.com /security/advisories/VMSA-2021-0018.html
patch, vendor-advisory

Sources

CVE List CVE-2021-22025
NVD CVE-2021-22025

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.