Tunnelblick: Incomplete Cleanup
CVE-2025-43711 is a high-severity incomplete cleanup vulnerability in Tunnelblick from Tunnelblick Project, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, without any action from a user. The record lists version 7.0 as the first without the flaw, so updating Tunnelblick to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.18% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Tunnelblick to 7.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Tunnelblick Project | Tunnelblick | 3.5beta06 up to, but not including, 7.0 | 7.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (mitre.org).
Official description
Tunnelblick 3.5beta06 before 7.0, when incompletely uninstalled, allows attackers to execute arbitrary code as root (upon the next boot) by dragging a crafted Tunnelblick.app file into /Applications.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incomplete Cleanup
The product does not properly clean up and remove temporary or supporting resources after they have been used.
How developers prevent this class of flaw
- Temporary files and other supporting resources should be deleted/released immediately after they are no longer needed.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Recent Incomplete Cleanup vulnerabilities
- 7.8 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.