highCVE-2026-33443

CVE-2026-33443 in Absolute Secure Access

CVE-2026-33443 is a memory management error in Secure Access servers prior to 14.55. Attackers with an intimate knowledge of and total control over the tunnel protocol can create a persistent DoS against the server.

ProductSecure Access
CVSS7.1
EPSSNot scored yet
UpdatedJuly 16, 2026

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

  • Absolute Secure Access server before 14.55

Fixed versions

  • 14.55

How to fix it

CVE-2026-33443 is a denial of service issue in Secure Access. Update from Absolute Secure Access server before 14.55 to 14.55 or newer. Keep it simple: upgrade first, then test the normal user flow.

  1. Find every place where Secure Access is installed or used.
  2. Upgrade Secure Access to 14.55 or a newer fixed release from the vendor.
  3. If you cannot upgrade right away, limit access to the affected feature until the update is done.
  4. Restart or redeploy the service if the product needs it after the update.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is 14.55 or newer.
  • Run a normal login, admin, and user flow to make sure the site still works.
  • Check logs for new errors after the update.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-33443?

Absolute Secure Access versions listed as affected should be reviewed: Absolute Secure Access server before 14.55.

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.