dbcve.org
VulnerabilityAwaiting classification

CVE-2026-55399

MEDIUM · 5.1 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Remotely reachable 6 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-55399 is a resource exhaustion vulnerability in the Secure Access publisher prior to 14.55. Attackers with valid credentials to the Secure Access tunnel can create a non-persistent DoS against the publisher.

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 · high confidence

This is a resource exhaustion vulnerability in Secure Access publisher versions prior to 14.55. Attackers who possess valid credentials to the Secure Access tunnel can exploit improper resource management to cause a non-persistent denial of service against the publisher, likely by exhausting memory, connections, or other finite resources.

MitigationUpgrade Secure Access publisher to version 14.55 or later to obtain the patch for this vulnerability.

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

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
Low
Privileges
Low
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Secure Access publisher installation
    Locate the Secure Access publisher software on the system. Common methods include checking installed programs list, service information, or running 'Get-Service' or 'sc query' commands to find services containing 'Secure Access' or 'publisher' in their name.
    Affected if Secure Access publisher is installed on the system
  2. Determine installed version
    Check the version of the Secure Access publisher installation. This is typically available through the product's UI under 'About' or 'Help', via command line with product-specific flags, or by inspecting registry entries or installation directories if known.
    Affected if The installed version is lower than 14.55 (e.g., 14.54, 14.50, or earlier)
  3. Verify Secure Access tunnel configuration
    Inspect the Secure Access publisher configuration to determine if the tunnel functionality is enabled and accessible. Check for open ports or listening services related to tunnel access, and review configuration files or management console settings for tunnel status.
    Affected if The tunnel feature is enabled and reachable from network locations where attackers could obtain credentials
  4. Monitor for resource exhaustion symptoms
    Observe system resource usage including memory consumption, connection counts, and CPU utilization on the publisher system. Use tools like Task Manager, Resource Monitor, or 'netstat' to check for abnormal connection counts or memory usage patterns.
    Affected if The publisher exhibits unusually high resource consumption that persists or spikes without corresponding legitimate workload

A system is affected if Secure Access publisher version is installed and is lower than 14.55, with the tunnel feature enabled and accessible to attackers who have valid credentials.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Secure Access publisher to version 14.55 or later to obtain the patch for this vulnerability.

Recommended fix Moderate confidence

Secure Access publisher version 14.55

  1. 1. Verify current Secure Access publisher version via admin console or CLI
  2. 2. Schedule a maintenance window for the upgrade process
  3. 3. Obtain the version 14.55 upgrade package from Absolute's official download portal or support
  4. 4. Back up current configuration and verify backup integrity
  5. 5. Apply the upgrade to Secure Access publisher following official installation documentation
  6. 6. Verify the upgrade completed successfully and the version shows 14.55
  7. 7. Test Secure Access tunnel functionality and confirm the resource exhaustion vulnerability is remediated

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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