dbcve.org
Secure AccessApplication · Absolute

CVE-2026-33443

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-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.

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

A memory management error in Secure Access servers versions prior to 14.55 allows an attacker with intimate knowledge and total control over the tunnel protocol to cause a persistent denial of service against the server.

MitigationUpgrade Secure Access servers to version 14.55 or later to remediate this vulnerability.

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. Determine installed Secure Access version
    Locate and inspect the version information for your Absolute Secure Access installation, typically available via the product's About section, management console, or running 'version' command if available in CLI
    Affected if The installed version is lower than 14.55 (e.g., 14.50, 14.0, etc.)
  2. Confirm tunnel protocol is in use
    Review your Secure Access server configuration to determine if the tunnel protocol feature is enabled and actively used for client connections
    Affected if Tunnel protocol is enabled and clients are connecting via this protocol
  3. Check for service disruption indicators
    Review system logs, event logs, and Secure Access-specific logs for evidence of unexpected server crashes, restarts, or service failures that correlate with tunnel protocol activity
    Affected if Multiple unexplained server crashes or persistent service unavailability is observed
  4. Verify server stability
    Monitor the Secure Access server process for abnormal termination or memory-related errors in system monitoring tools or logs
    Affected if The server process terminates unexpectedly or exhibits memory exhaustion patterns

You are affected if your Absolute Secure Access version is below 14.55 and the tunnel protocol feature is enabled, especially if you observe unexplained server crashes or persistent DoS conditions.

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 to remediate this vulnerability.

Recommended fix Moderate confidence

Secure Access version 14.55

  1. 1. Back up the current Secure Access server configuration and any critical data.
  2. 2. Review the Absolute Secure Access release notes for version 14.55 to understand any specific upgrade requirements.
  3. 3. Download the Secure Access version 14.55 or later from the official Absolute download portal.
  4. 4. Apply the upgrade to the Secure Access server following the standard upgrade procedure documented in the Absolute administrator guide.
  5. 5. After upgrade, verify the server is running version 14.55 or later.
  6. 6. Test that the Secure Access tunnel functionality is working properly.
  7. 7. Monitor the server for any abnormal resource consumption that could indicate the vulnerability is still present.
Caveat No breaking changes mentioned in the provided advisory; however, review release notes for any configuration or compatibility notes

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

Fix this in Secure Access Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33443 — 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-33443 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