# CVE-2025-66374: Privilege escalation in n/a

> A local user can escalate privileges by exploiting policy elevation of an Administration task in the CyberArk Endpoint Privilege Manager Agent.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 28 Feb 2026
- **Also known as:** GHSA-qg48-mr48-98hv

## What is CVE-2025-66374?

CVE-2025-66374 is a high-severity vulnerability in n/a, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

CyberArk Endpoint Privilege Manager Agent through 25.10.0 allows a local user to achieve privilege escalation through policy elevation of an Administration task.

Weakness: CWE-269 (Improper Privilege Management)

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

It affects 1 product.


Products: Cyberark Endpoint Privilege Manager.

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

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

## Is CVE-2025-66374 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-13052](https://insights.sbomify.com/CVE-2018-13052/): Privilege escalation in n/a (critical 9.8)
- [CVE-2026-2914](https://insights.sbomify.com/CVE-2026-2914/): Privilege escalation in Endpoint Privilege Manager Agent (high 8.5)
- [CVE-2021-44049](https://insights.sbomify.com/CVE-2021-44049/): Privilege escalation in n/a (high 7.8)
- [CVE-2018-14894](https://insights.sbomify.com/CVE-2018-14894/): Security feature bypass in n/a (high 7.8)
- [CVE-2019-9627](https://insights.sbomify.com/CVE-2019-9627/): Memory corruption in n/a (high 7.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-66374 is a high-severity vulnerability in n/a, published on 3 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-66374 in the wild and no public exploit code.

Affected product: n/a. 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-66374/ (Markdown: https://insights.sbomify.com/CVE-2025-66374/index.md)
```

## Sources

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

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