# CVE-2025-41245: Information disclosure in VMware Aria Operations

> A malicious actor with non-administrative privileges can disclose credentials of other users in VMware Aria Operations.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-8rq8-hfwr-4p7v

## What is CVE-2025-41245?

CVE-2025-41245 is a medium-severity vulnerability in VMware Aria Operations, published on 29 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

VMware Aria Operations contains an information disclosure vulnerability. A malicious actor with non-administrative privileges in Aria Operations may exploit this vulnerability to disclose credentials of other users of Aria Operations.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2025-41245 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41245 is a medium-severity vulnerability in VMware Aria Operations, published on 29 Sep 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-41245 in the wild and no public exploit code.

Affected product: VMware Aria Operations. 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-41245/ (Markdown: https://insights.sbomify.com/CVE-2025-41245/index.md)
```

## Sources

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

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