# CVE-2025-11862: Verve Asset Manager Access Control Vulnerability

> Unauthorized read-only users can read, update, and delete user accounts via the API in Verve Asset Manager.

- **Severity:** High 8.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:L/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2025
- **Updated:** 12 Nov 2025
- **Also known as:** GHSA-wffg-fw64-5mvq

## What is CVE-2025-11862?

CVE-2025-11862 is a high-severity missing authorization vulnerability in Rockwell Automation Verve Asset Manager, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security issue was discovered within Verve Asset Manager allowing unauthorized read-only users to read, update, and delete users via the API.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2025-11862 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11862 is a high-severity missing authorization vulnerability in Rockwell Automation Verve Asset Manager, published on 11 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11862 in the wild and no public exploit code.

Affected product: Rockwell Automation Verve Asset Manager. 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-11862/ (Markdown: https://insights.sbomify.com/CVE-2025-11862/index.md)
```

## Sources

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

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