CVE-2025-66374
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCyberArk Endpoint Privilege Manager Agent through 25.10.0 allows a local user to achieve privilege escalation through policy elevation of an Administration task.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceCyberArk Endpoint Privilege Manager Agent through version 25.10.0 contains a local privilege escalation vulnerability where a local user can elevate privileges by manipulating policy elevation of an Administration task. This allows a standard local user to gain higher-level privileges through the EPM agent's policy configuration mechanism.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 25.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify EPM Agent is installedCheck for CyberArk Endpoint Privilege Manager Agent in installed programs (Programs and Features) or check for the EPM service running on the systemAffected if The CyberArk EPM Agent is installed on the endpoint
-
Check installed EPM versionLocate the EPM Agent installation directory and check the version file, or use 'Get-ItemProperty' on the uninstall registry key for CyberArk EPM to retrieve the version numberAffected if The installed version is 25.10.0 or any version lower than 25.10.0 (the agent version is <= 25.10.0)
-
Review EPM policy configurations for Administration tasksAccess the EPM management console or policy configuration files to examine elevation rules for Administration tasks. Look for any policies that grant elevated privileges to standard local usersAffected if There are policies that allow standard/local users to elevate privileges for Administration tasks, especially if these policies were modified without authorization
-
Audit recent EPM policy changesReview EPM policy change logs or audit trails to identify any recent modifications to elevation policies, particularly those affecting Administration task elevationAffected if There are unauthorized or unexpected modifications to policy elevation settings for Administration tasks
The environment is affected if CyberArk Endpoint Privilege Manager Agent version 25.10.0 or lower is installed AND there are EPM policies that allow manipulation of Administration task elevation by local users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply the vendor patch or upgrade to a version newer than 25.10.0 once released. Review and audit existing EPM policies for unauthorized changes and restrict local administrative access to the endpoint.
Upgrade to the fixed release of Endpoint Privilege Manager published by CyberArk (version higher than 25.10.0 - verify exact version in official CyberArk security advisory)
- 1. Identify all systems running CyberArk Endpoint Privilege Manager version 25.10.0 or earlier.
- 2. Contact CyberArk support or check the official CyberArk security advisory at docs.cyberark.com for the specific fixed version and upgrade instructions.
- 3. Plan and schedule an upgrade window following your organization's change management process.
- 4. Backup current Endpoint Privilege Manager configuration and policies.
- 5. Upgrade Endpoint Privilege Manager agent to the fixed version released by CyberArk.
- 6. Verify the upgrade was successful and test that privilege escalation is no longer possible through policy elevation.
- 7. Monitor for any post-upgrade issues and validate that existing policies function correctly.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66374 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-66374 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data