CVE-2025-12694
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 · uneditedA local privilege escalation vulnerability exists in Forcepoint VPN Client that allows a local non-administrative user to escalate privileges to SYSTEM. This issue affects VPN Client for Windows: versions 6.11.3 and prior.
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 confidenceA local privilege escalation vulnerability in Forcepoint VPN Client for Windows versions 6.11.3 and prior allows an unprivileged local user to gain SYSTEM-level privileges. The specific attack vector is not detailed, but the vulnerability enables complete local privilege escalation on affected Windows systems.
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< 6.11.3CVSS 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.
-
Check if Forcepoint VPN Client is installedOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check for the presence of C:\Program Files\Forcepoint\VPN Client\ folderAffected if The software is not present on the system, so the vulnerability does not apply
-
Retrieve the installed version numberCheck the Version value in the registry key for Forcepoint VPN Client, or right-click on vpngui.exe in the installation folder and view Properties > DetailsAffected if Unable to determine the version - manual inspection required
-
Compare against vulnerable version rangeCompare the installed version to 6.11.3 - any version less than 6.11.3 is affectedAffected if Installed version is 6.11.3 or lower (e.g., 6.11.2, 6.11.1, 6.10.x, etc.)
-
Verify the VPN Client service is presentOpen Services console (services.msc) and look for 'Forcepoint VPN Client' service, or run 'sc query' commandAffected if Service exists and is running - the vulnerability requires the client to be installed and operational
The system is affected if Forcepoint VPN Client for Windows is installed with a version lower than 6.11.3 and the client service is present on the system.
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 · scoped6.11.3
Upgrade Forcepoint VPN Client to a version newer than 6.11.3. Until patched, limit local access to untrusted users and monitor for suspicious processes.
6.11.3 or later
- 1. Backup current VPN Client configuration if needed
- 2. Download Forcepoint VPN Client version 6.11.3 or later from support.forcepoint.com
- 3. Uninstall the current VPN Client version
- 4. Install the new version 6.11.3 or later
- 5. Reconfigure VPN settings as needed
- 6. Verify the installation and test VPN connectivity
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12694 — 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-12694 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