Local forwarding-control bypass via unreleased health-check port
Published Nov 12, 2025 · Updated Nov 12, 2025
Resource-release failure in Zscaler Client Connector 4.6 before 4.6.0.216 and 4.7 before 4.7.0.47 allows local users to bypass forwarding controls. Under specific circumstances, the client fails to clear a cached health-check source port after use, allowing new traffic to inherit its bypass treatment. Low-privileged local access is required; successful use routes affected traffic around forwarding controls without interrupting service.
Summary
What happened
Resource-release failure in Zscaler Client Connector 4.6 before 4.6.0.216 and 4.7 before 4.7.0.47 allows local users to bypass forwarding controls. Under specific circumstances, the client fails to clear a cached health-check source port after use, allowing new traffic to inherit its bypass treatment. Low-privileged local access is required; successful use routes affected traffic around forwarding controls without interrupting service.
The record
- CVE
- CVE-2025-54983
- Published
- Nov 12, 2025
- Updated
- Nov 12, 2025
- Vendor
- Zscaler
- Product
- Zscaler Client Connector
- Classifications
- CWE-772, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 12, 2025CVE publishedPublication date reported by the CVE source.
- Nov 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=4.6 <4.6.0.216
- Affected versionversion=4.7 <4.7.0.47
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo