# CVE-2025-41252: Username enumeration vulnerability

> Unauthenticated attackers can enumerate valid usernames in VMware NSX, facilitating unauthorized access attempts.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-2gr4-4mrg-85rh

## What is CVE-2025-41252?

CVE-2025-41252 is a high-severity vulnerability in VMware NSX, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Description: VMware NSX contains a username enumeration vulnerability. An unauthenticated malicious actor may exploit this to enumerate valid usernames, potentially leading to unauthorized access attempts.

Impact: Username enumeration → facilitates unauthorized access.

Attack Vector: Remote, unauthenticated.

Severity: Important.

CVSSv3: 7.5 (High).

Acknowledgments: Reported by the National Security Agency.

Affected Products:

  *  VMware NSX 9.x.x.x, 4.2.x, 4.1.x, 4.0.x

  *  NSX-T 3.x

  *  VMware Cloud Foundation (with NSX) 5.x, 4.5.x

Fixed Versions: 

  *  NSX 9.0.1.0;  4.2.2.2/4.2.3.1 http://4.2.2.2/4.2.3.1 ; 4.1.2.7; NSX-T 3.2.4.3; CCF async patch (KB88287).

Workarounds: None.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2025-41252?


## How do I fix CVE-2025-41252?

No fix has been published for CVE-2025-41252 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-41252 being exploited?

There is no known exploitation of CVE-2025-41252 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41252 and fix it if it is affected.

What it is: CVE-2025-41252 is a high-severity vulnerability in VMware NSX, published on 29 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41252 in the wild and no public exploit code.

Affected product: VMware NSX. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-41252/ (Markdown: https://insights.sbomify.com/CVE-2025-41252/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-41252
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-41252
- OSV: https://osv.dev/vulnerability/CVE-2025-41252

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-41252/
Summaries are generated and may contain mistakes; the official description above is the record.