dbcve.org
Secure AccessApplication · Absolute

CVE-2026-33445

MEDIUM · 5.9 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 14.55 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
CVE-2026-33445 is a memory management vulnerability 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a memory management vulnerability in Secure Access servers prior to version 14.55. An attacker with intimate knowledge and total control over the tunnel protocol can exploit improper memory handling to create a persistent denial-of-service condition against the server.

MitigationUpgrade Secure Access servers to version 14.55 or later. Since exploitation requires deep knowledge and control of the tunnel protocol, restrict access to trusted personnel and monitor for anomalous tunnel traffic.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Secure AccessApplication
Affected:< 14.55

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Absolute Secure Access server is present
    Locate the Secure Access server installation in your environment. Check for the Absolute Secure Access server software or any related services running on your systems.
    Affected if The server software is installed and running.
  2. Determine the installed version
    Use the system's standard method for querying software version - typically via the software's built-in version check, About dialog, or command-line version flag. Consult vendor documentation for the specific command or method for your installation.
    Affected if The installed version is any version prior to 14.55.
  3. Verify tunnel protocol configuration
    Examine the server configuration to determine if the tunnel protocol feature is enabled. Check the server settings, profile configurations, or network settings where tunnel-related options are defined.
    Affected if The tunnel protocol is enabled and accessible to an attacker with network access to it.
  4. Assess network exposure
    Review network access controls and firewall rules to determine who can reach the tunnel protocol interface. Identify if untrusted network paths lead to the tunnel endpoint.
    Affected if The tunnel interface is accessible to an attacker with intimate knowledge and control capabilities.

You are affected if you are running any version of Absolute Secure Access server prior to 14.55 with the tunnel protocol enabled and accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 14.55 or later
Fixed in 14.55
Interim mitigation

Upgrade Secure Access servers to version 14.55 or later. Since exploitation requires deep knowledge and control of the tunnel protocol, restrict access to trusted personnel and monitor for anomalous tunnel traffic.

Recommended fix Moderate confidence

Secure Access version 14.55

  1. 1. Back up current Secure Access configuration and data
  2. 2. Review Absolute Secure Access release notes for version 14.55 to understand changes
  3. 3. Download Secure Access version 14.55 from Absolute's official download portal or support site
  4. 4. Follow Absolute's documented upgrade procedure for Secure Access servers
  5. 5. Verify the upgrade was successful by checking the server version
  6. 6. Test that tunnel protocol functionality is restored and stable
  7. 7. Monitor server performance to confirm the DoS vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Secure Access Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33445 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33445 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data