2026 First quarter vulnerability briefing: Five Perimeter CVEs Enterprises Are Racing To Patch
Five remotely exploitable, pre-authentication vulnerabilities disclosed this quarter now sit in CISA's Known Exploited Vulnerabilities catalog. All five affect perimeter infrastructure - VPN gateways, SD-WAN controllers, application delivery controllers, and endpoint management servers - and none require a credential, a foothold, or user interaction to exploit. This part covers how each one works from an attacker's perspective, what defenders should be hunting for, and why authentication logic - not memory corruption - is the theme connecting all five. Part 2 will cover this quarter's locally exploited CVEs.
Why These Five Are the Priority List
Every CVE below shares the same profile: internet-facing product, zero authentication required, and confirmed exploitation in the wild. That combination is what separates a "patch this quarter" bug from a "patch this week" bug. Threat actors do not wait for research papers on vulnerabilities like these - scanning for exposed, unpatched instances typically begins within days of a public PoC.
| CVE | Product | CVSS | Weakness | CISA KEV |
|---|---|---|---|---|
| CVE-2026-20182 | Cisco Catalyst SD-WAN Manager / Controller | 10.0 | CWE-287 Improper Authentication | Yes |
| CVE-2026-21643 | Fortinet FortiClient EMS 7.4.4 | 9.8 | CWE-89 SQL Injection | Yes |
| CVE-2026-50751 | Check Point Remote Access VPN | 9.3 | CWE-287 Improper Authentication | Yes |
| CVE-2026-3055 | Citrix NetScaler ADC / Gateway | 9.3 | CWE-125 Out-of-Bounds Read | Yes |
| CVE-2026-0257 | Palo Alto PAN-OS GlobalProtect | 9.1 | CWE-565 Reliance on Unvalidated Cookies | Yes |
CVE-2026-20182: Cisco Catalyst SD-WAN Peering Authentication Bypass
This is the single most severe finding in this quarter's remote batch. It affects vdaemon, the service Cisco Catalyst SD-WAN Controllers, Managers, and Validators use to establish authenticated DTLS peering relationships with one another over UDP/12346.
Root Cause
Peering is supposed to be mutually authenticated via certificate exchange. The flaw is in how the server handles a peer that self-identifies as a vHub during the CHALLENGE / CHALLENGE_ACK exchange. Instead of completing certificate validation, the server treats the unverified remote node as authenticated and accepts it as a trusted peer.
Attack Flow
| Step | Action |
|---|---|
| 1 | Attacker connects to the target on UDP/12346 and receives a CHALLENGE (msg_type 8) |
| 2 | Responds with CHALLENGE_ACK (msg_type 9), spoofing device_type = 2 (vHub) |
| 3 | Server replies CHALLENGE_ACK_ACK (msg_type 10) and skips certificate validation |
| 4 | peer->authenticated is now 1 - bypass complete |
| 5 | Attacker sends HELLO (msg_type 5), moving the peering session to UP state |
| 6 | Attacker sends VMANAGE_TO_PEER (msg_type 14) with a 768-byte padded SSH public key |
| 7 | Server writes the key into /home/admin/.ssh/authorized_keys for
vmanage-admin |
| 8 | Persistent SSH and NETCONF (TCP/830) access as a privileged administrative account |
$ python3 cve-2026-20182.py -t 192.168.1.10 --netconf [+] Peering bypass successful - peer->authenticated = 1 [+] SSH public key injected into vmanage-admin authorized_keys [*] Verifying via NETCONF hello exchange on TCP/830... [+] Capabilities received - persistent admin access confirmed
Mitigation
- • Apply Cisco's advisory patch (CSCwr23456) without delay - this is a KEV-listed, maximum-severity flaw.
- • Restrict UDP/12346 to management networks only; it should never be internet-facing.
- • Audit
authorized_keyson all vManage/vSmart/vBond nodes for unauthorized entries. - • Monitor vdaemon peering logs for peers claiming device_type = 2 from unexpected source IPs.
CVE-2026-21643: FortiClient EMS Unauthenticated SQL Injection
FortiClient EMS is the centralized console Fortinet administrators use to manage endpoint agents fleet-wide - which makes it a high-value target. Compromising EMS means compromising visibility and control over every managed endpoint.
Root Cause
The /api/v1/init_consts endpoint accepts a Site HTTP header meant to carry a
tenant identifier. That value is used, unsanitized, to set the PostgreSQL search_path for the
backend query - and the endpoint requires no authentication at all.
GET /api/v1/init_consts HTTP/1.1
Host: target-ems.example.com
Site: tenant1; SELECT version()--
[Response]
....
PostgreSQL error
PostgreSQL 15.3 (Ubuntu 15.3-1.pgdg22.04+1)
The injected statement modifies the PostgreSQL search_path setting before executing an attacker-controlled SQL statement. If successful, the server may return database version information, error messages, or other query results, confirming that the SQL injection point is reachable.
Once validated, an attacker could perform blind SQL injection techniques, introduce execution delays using database timing functions, and enumerate database metadata such as tables and schemas.
Mitigation
- • Upgrade to FortiClient EMS 7.4.5 or later immediately.
- • Restrict management interface exposure - EMS should not be reachable from the public internet.
- • Review PostgreSQL logs for anomalous queries containing
search_pathmanipulation. - • Apply WAF rules to detect SQL metacharacters in the
Siteheader as an interim control.
CVE-2026-50751: Check Point Remote Access VPN IKEv1 Authentication Bypass
A logic flaw in the deprecated IKEv1 key exchange lets an unauthenticated attacker bypass certificate/PSK validation and establish a full remote-access VPN session - landing inside the corporate network without a valid password. This CVE has been directly linked to Qilin ransomware intrusions.
How the Public PoC Probes It
Detection tooling sends a minimal 80-byte IKEv1 Main Mode packet (28-byte ISAKMP header plus a 52-byte SA payload proposing 3DES/SHA1/PSK/DH Group 5) to UDP/500 or UDP/4500 and checks for a valid IKEv1 response. No authentication is attempted by the probe itself - a response simply confirms IKEv1 is enabled and the gateway is potentially exploitable.
$ python3 cve-2026-50751.py -t 1.2.3.4 -p 500 [*] Sending minimal IKEv1 probe to 1.2.3.4:500 ... [-] Received IKEv1 response from 1.2.3.4:500 (68 bytes) [!] IKEv1 IS ENABLED AND RESPONDING -> POTENTIALLY VULNERABLE Recommendation: Disable IKEv1 immediately and apply hotfix (SK185033)
Mitigation
- • Disable IKEv1 on all Remote Access VPN gateways - migrate to IKEv2 where possible.
- • Apply Check Point hotfix per advisory SK185033 immediately.
- • Hunt for VPN sessions established without a corresponding successful authentication event.
- • Enforce MFA as a compensating control, though this does not fully mitigate a pre-auth bypass.
CVE-2026-3055: Citrix NetScaler SAML/WS-Fed Memory Overread
Security teams who lived through CitrixBleed will recognize this shape immediately. NetScaler instances configured as a SAML Identity Provider are affected by an out-of-bounds read that leaks adjacent process memory into an HTTP response cookie.
Attack Flow
| Step | Action |
|---|---|
| 1 | Attacker identifies an internet-facing NetScaler with SAML or WS-Fed endpoints exposed |
| 2 | Sends a malformed SAML assertion, or a WS-Fed request with a valueless wctx
parameter |
| 3 | The vulnerable parser performs an out-of-bounds read of process memory |
| 4 | Leaked memory is returned, base64-encoded, inside Set-Cookie: NSC_TASS=... |
| 5 | Attacker decodes the cookie, extracting session cookies, SAML assertions, or auth tokens |
| 6 | Extracted tokens are replayed to hijack active sessions - no credential ever touched |
GET /wsfed/passive?wa=ctx HTTP/1.1
Host: target-netscaler.example.com
[Response]
Set-Cookie: NSC_TASS=TvQ0AAAAAAEAAA//8AAQuQAAA!AAAAAAAAAAAAA...
Mitigation
- • Upgrade to the patched build (14.1-66.59 or later, per vendor advisory).
- • After patching, terminate all active ICA and PCoIP sessions to invalidate leaked tokens.
- • Review NSC_TASS-related session logs for anomalous concurrent sessions from differing geolocations.
- • Disable SAML/WS-Fed endpoints where not actively in use.
CVE-2026-0257: Palo Alto GlobalProtect Cookie-Based Authentication Bypass
GlobalProtect portals and gateways configured with authentication override cookies are susceptible to unauthorized VPN connections when the override mechanism relies on a cookie value without adequate validation or integrity checking.
Root Cause
The "authentication override" feature lets a returning client skip re-authentication by presenting a previously issued cookie. Under specific configurations, the gateway does not adequately verify that cookie's authenticity before granting a session - allowing an attacker who obtains or forges the value to bypass authentication entirely and establish a VPN tunnel.
Mitigation
- • Apply the PAN-OS update addressing CVE-2026-0257 per Palo Alto's advisory.
- • Review GlobalProtect configuration for authentication override cookie usage; disable if not required.
- • Rotate authentication override cookie secrets/keys after patching.
- • Monitor GlobalProtect logs for VPN sessions established via cookie override from unfamiliar source IPs.
Cross-Vulnerability Analysis
Viewed together, these five CVEs point to a clear shift: authentication and trust-boundary logic is now a bigger target than memory corruption. Four of the five - Cisco, Check Point, Fortinet, and Palo Alto - are pure logic flaws where vulnerable code trusted something it should have verified: a claimed device role, a legacy protocol handshake, a header value, or a cookie. Only the Citrix NetScaler issue is a classic memory-safety bug, and even there the payoff for the attacker is authentication material, not code execution.
For defenders, this shifts priorities. Memory-safety bugs get caught by fuzzing and static analysis over time; trust-boundary logic flaws often surface only when someone specifically tests "what happens if I claim to be X" - exactly what red teams should be probing against edge infrastructure that terminates VPN, SD-WAN, or SAML/SSO trust relationships.
Recommended Immediate Actions
- • Patch by exposure, not CVSS alone. All five are in CISA KEV - treat federal remediation timelines as the floor, not the ceiling.
- • Disable legacy protocol support (IKEv1 on Check Point gateways) where feasible.
- • Invalidate sessions after patching any auth-bypass or memory-disclosure CVE - a patch does not retroactively invalidate already-stolen tokens.
- • Hunt, don't just patch. KEV-listed bugs are, by definition, already being exploited - search retrospectively using the log guidance above.
- • Reduce perimeter exposure of management-plane services that have no legitimate reason to be internet-reachable.
What's Next? Initial access is only the first stage of an attack. In Part 2: Critical Local Exploited CVEs, we examine the privilege escalation vulnerabilities attackers use to gain SYSTEM or root access after compromising a host.
For a deeper analysis of this quarter's most critical vulnerabilities and exploitation trends, watch our Quarterly Vulnerability Update Webinar.
Instantly Fix Risks with Saner Patch Management
Saner patch management is a continuous, automated, and integrated software that instantly fixes risks exploited in the wild. The software supports major operating systems like Windows, Linux, and macOS, as well as 550+ third-party applications.
It also allows you to set up a safe testing area to test patches before deploying them in a primary production environment. Saner patch management additionally supports a patch rollback feature in case of patch failure or a system malfunction.
Experience the fastest and most accurate patching software here.




