dbcve.org
Secure AccessApplication · Absolute

CVE-2026-0517

HIGH · 7.5 CVSS v3.1 Published 2026-01-17
Fix available
A fix is available. Upgrade to 14.20 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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-0517 is a denial-of-service vulnerability in versions of Secure Access Server prior to 14.20. An attacker can send a specially crafted packet to a server and cause the server to crash

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 denial-of-service vulnerability exists in Secure Access Server versions prior to 14.20. An unauthenticated remote attacker can send a specially crafted packet to the server, causing it to crash.

MitigationUpgrade Secure Access Server to version 14.20 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.20

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/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. Confirm Secure Access Server is installed
    Check system inventory, installed software list, or running processes for 'Secure Access Server' or related service names
    Affected if Secure Access Server software is present on the system
  2. Identify the installed version
    Use system-specific commands or consult software inventory to retrieve the Absolute Secure Access version number
    Affected if The version retrieved is less than 14.20
  3. Verify version against affected range
    Compare your installed version to the affected range: versions prior to 14.20 are vulnerable
    Affected if Installed version is 14.19.x or lower, or any version below 14.20

If Secure Access Server is installed and the version is below 14.20, the environment is affected by this denial-of-service vulnerability.

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.20 or later
Fixed in 14.20
Interim mitigation

Upgrade Secure Access Server to version 14.20 or later to remediate this vulnerability.

Recommended fix Moderate confidence

Secure Access Server 14.20

  1. 1. Backup current Secure Access Server configuration and data
  2. 2. Download Secure Access Server version 14.20 from Absolute's official download portal
  3. 3. Follow Absolute's standard upgrade procedure for Secure Access Server
  4. 4. Verify the upgrade completed successfully by checking the server version
  5. 5. Test that the server is responsive and functioning normally
  6. 6. Monitor server logs to confirm no crash events occur
Caveat No specific breaking changes mentioned in the available description; standard upgrade precautions apply

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

Fix this in Secure Access Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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