CVE-2025-26168
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 · uneditedIXON VPN Client before 1.4.4 on Linux and macOS allows Local Privilege Escalation to root because there is code execution from a configuration file that can be controlled by a low-privileged user. There is a race condition in which a temporary configuration file, in a world-writable directory, can be overwritten.
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 · high confidenceThe IXON VPN Client before version 1.4.4 on Linux and macOS contains a local privilege escalation vulnerability. A low-privileged attacker can exploit a race condition by overwriting a temporary configuration file located in a world-writable directory, allowing arbitrary code execution with root privileges.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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 IXON VPN Client is installedOn Linux: check for /opt/ixon-vpn or look for ixon-vpn in /usr/bin, /usr/local/bin. On macOS: check /Applications for IXON VPN.app or run 'which ixon-vpn' in terminalAffected if The IXON VPN Client software is present on the system
-
Determine installed versionRun the client with --version flag or check the installed package version. On Linux: dpkg -l | grep ixon or rpm -qa | grep ixon. On macOS: right-click IXON VPN.app > Get Info or use 'mdls' commandAffected if The installed version is lower than 1.4.4
-
Identify temporary configuration file locationCheck the application's runtime directory for temporary config files. Look in /tmp, /var/tmp, or application-specific temp directories. Use 'find /tmp -user $USER -name "*config*" -o -name "*ixon*"' to locate IXON-related temp filesAffected if A temporary configuration file exists in a world-writable directory (permissions 777)
-
Verify directory permissions on temp locationsRun 'ls -ld /tmp /var/tmp' and check for world-writable sticky bit. Also check any application-specific temp directories found in step 3Affected if The temporary directory lacks proper restrictions (not 1777 with sticky bit, or owned by root)
-
Check for recent file modifications in temp directoriesRun 'ls -lat /tmp | head -20' or use audit logs to review recent file creations/modifications in temp directories related to IXONAffected if Temporary configuration files were recently modified by a non-root user after the application ran
A user is affected if IXON VPN Client version 1.4.4 or earlier is installed on Linux or macOS, and temporary configuration files are stored in world-writable directories without proper permissions.
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 · scopedUpgrade the IXON VPN Client to version 1.4.4 or later. As an interim measure, ensure proper file permissions on directories used by the application and monitor for suspicious file modifications.
IXON VPN Client 1.4.4 (or latest stable release)
- Obtain the latest IXON VPN Client version 1.4.4 or later from the official vendor (https://www.ixon.cloud or https://support.ixon.cloud)
- Uninstall the current IXON VPN Client version from the Linux or macOS system
- Install the updated IXON VPN Client version 1.4.4 or newer
- Verify the installation completed successfully and confirm the version number matches 1.4.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26168 — 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-26168 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