# CVE-2025-14377: Verve Asset Manager – Plaintext Storage Vulnerabilities

> Attackers can read plaintext secrets from legacy Ansible playbooks in Verve Asset Manager if the retired optional component is enabled.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Jan 2026
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-w6pj-gq3f-8h94

## What is CVE-2025-14377?

CVE-2025-14377 is a high-severity vulnerability in Rockwell Automation Verve Asset Manager, published on 20 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security issue was discovered within the legacy Ansible playbook component of Verve Asset Manager, caused by plaintext secrets incorrectly stored when a playbook is running. This component has been retired and has been optional since the 1.36 release in 2024.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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


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

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

## Is CVE-2025-14377 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14377 is a high-severity vulnerability in Rockwell Automation Verve Asset Manager, published on 20 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14377 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-14377/ (Markdown: https://insights.sbomify.com/CVE-2025-14377/index.md)
```

## Sources

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

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