Absolute Secure Access EUVD-2026-44801

Exploitation requires the attacker to have, per the vendor description, 'intimate knowledge of and total control over the tunnel protocol' - meaning the ability to craft and drive arbitrary Secure Access tunnel-protocol exchanges, not merely send generic network traffic. The target must be a Secure Access server running a version earlier than 14.55 and reachable on its tunnel service. The published CVSS states PR:N (no authentication) and AV:N (network), so it is nominally remote and unauthenticated; however, the demanded protocol mastery and 'total control over the tunnel' is the real limiting factor and points toward either an established/authenticated tunnel session or a privileged network position, which narrows the pool of capable attackers well below what AC:L/AT:N implies.

The supplied CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H) rates this network-reachable, unauthenticated, and low-complexity, yielding 8.7 (High) with pure availability impact. That raw scoring conflicts with the description, which states the attacker needs 'intimate knowledge of and total control over the tunnel protocol' - a meaningful skill/positioning prerequisite that argues for higher attack complexity or an explicit attack requirement rather than the AC:L/AT:N in the published vector; this should be verified with the vendor. There is no EPSS score, no SSVC decision data, no POC, and no CISA KEV listing in the provided intelligence, so there is no evidence of automatable or active exploitation. Net assessment: a genuine but bounded risk - the worst case is loss of remote-access availability (which can be business-critical for a VPN gateway), not data theft or code execution - so it should be prioritized as an availability/uptime concern for internet-exposed Secure Access servers rather than treated as a wormable critical.

An attacker who understands the Absolute Secure Access tunnel protocol at a low level connects to an internet-facing server and drives the tunnel into a crafted state that trips the memory-management fault, leaving the server hung or crashed and unable to serve legitimate remote users until manual intervention. Because the failure is persistent rather than transient, a single successful attempt can cause a sustained outage. No public exploit code is known, and the required protocol expertise raises the practical bar despite the network-reachable vector.