dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2025-7012

HIGH · 8.6 CVSS v4.0 Published 2025-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
86/100
Remediation priority · High

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 · unedited
An issue in Cato Networks' CatoClient for Linux, before version 5.5, allows a local attacker to escalate privileges to root by exploiting improper symbolic link handling.

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 confidence

CatoClient for Linux versions prior to 5.5 contains a local privilege escalation vulnerability stemming from improper symbolic link handling. A local attacker can exploit this symlink vulnerability to gain root-level privileges on the affected system.

MitigationUpgrade CatoClient for Linux to version 5.5 or later to remediate this vulnerability.

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
Low
Privileges
Low
Authentication
Y
User interaction
P
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:U/V:X/RE:M/U:Green

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if CatoClient for Linux is installed
    Run 'which catoclient' or look for CatoClient in common installation directories such as /opt/CatoNetworks/, /usr/local/cato/, or search for 'catoclient' using 'find / -name "*catoclient*" 2>/dev/null'
    Affected if CatoClient for Linux is not found on the system, then the system is not affected by this local privilege escalation vulnerability
  2. Determine the installed CatoClient version
    Run 'catoclient --version' or 'catoclient -v' to display the installed version number. If these commands fail, check the installation directory for a version file or examine the catoclient binary with 'catoclient --help'
    Affected if The installed version number is lower than 5.5 (for example, 5.4.x, 5.3.x, or earlier)
  3. Verify the symlink vulnerability exposure
    Since this vulnerability involves improper symbolic link handling, inspect the CatoClient installation directory for world-writable directories or files with permissive permissions that could be manipulated via symlinks. Check for log files, temporary files, or configuration directories that the CatoClient process writes to with elevated privileges
    Affected if The CatoClient installation has files or directories with weak permissions (such as 777) that could be manipulated by a local unprivileged user to create or replace symlinks leading to privileged code execution

A system is affected if CatoClient for Linux is installed with a version lower than 5.5 and has insecure file permissions that allow local symlink manipulation leading to privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade CatoClient for Linux to version 5.5 or later to remediate this vulnerability.

Recommended fix Moderate confidence

CatoClient for Linux version 5.5

  1. Verify current CatoClient for Linux version by running: cat /opt/cato/catoclient/version.txt or dpkg -l | grep cato
  2. Download CatoClient version 5.5 or later from Cato Networks support portal at support.catonetworks.com
  3. Stop the CatoClient service: sudo systemctl stop catoclient or sudo /opt/cato/catoclient/catoclientctl stop
  4. Upgrade the package using your distribution's package manager: sudo dpkg -i catoclient-5.5.deb or sudo rpm -Uvh catoclient-5.5.rpm
  5. Verify the installation: dpkg -l | grep catoclient to confirm version 5.5 is installed
  6. Restart the CatoClient service: sudo systemctl start catoclient or sudo /opt/cato/catoclient/catoclientctl start

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-7012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-7012 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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