Menu

Star on GitHub · 3.2k

CVE-2026-55401

CVE-2026-55401 is a null dereference vulnerability on the load-balancing sub-system of Secure Access servers prior to 14.57.

Published Aug 13, 2026CWE-476EPSS 0.40%

Overview

CVE-2026-55401 is a known-severity vulnerability. It was published on August 13, 2026.

Technical description

CVE-2026-55401 is a null dereference vulnerability on the load-balancing

sub-system of Secure Access servers prior to 14.57. Attackers can send

an unauthenticated packet to a Secure Access server with load balancing

enabled, which results in the internal load balancer crashing. After a

successful attack, the Secure Access server is still able to accept

connections and is still able to issue a failover to connected clients. ‍ https://www.first.org/cvss/calculator/4.0#CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:L

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2026-55401?

CVE-2026-55401 is a known-severity vulnerability. It was published on August 13, 2026.

How severe is CVE-2026-55401?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-55401?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-55401?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-55401 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.