CVE-2026-33444 secure access vulnerability
CVE-2026-33444 is a memory management vulnerability in Secure Access servers prior to 14.55. Attackers with intimate knowledge of and total control over the tunnel protocol can create a non-persistent DoS against the server.
Quick answer
absolute secure access should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-33444 affects absolute secure access and is rated medium. CVE-2026-33444 is a memory management vulnerability in Secure Access servers prior to 14.55. Fix this first on internet-facing or admin systems. The practical fix is to upgrade Secure Access to 14.55 or a later vendor-supported release, then verify the system is no longer exposed.
- Inventory every server, container, appliance, cluster, plugin, or device that uses absolute secure access.
- Check the installed version and configuration against CVE-2026-33444 and the linked advisory.
- Apply the vendor fix: upgrade Secure Access to 14.55 or a later vendor-supported release.
- Restrict tunnel access to trusted users and block unknown networks until patched.
- Disable or isolate the affected feature if you cannot update right away.
- Review tunnel, server, and publisher logs for repeated disconnects, crashes, or resource spikes.
- Rotate secrets, rebuild affected systems, or reset sessions if you suspect compromise.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm absolute secure access is running the patched version or the approved mitigation is active.
- Confirm affected public, admin, API, tunnel, or cluster access is limited to trusted users.
- Repeat the risky workflow or a safe test case and confirm the issue no longer appears.
- Review logs again after the fix for crashes, bypass attempts, file access, or suspicious changes.
- Save version, config, log, and scan evidence for your remediation record.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-33444?
absolute secure access should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.