# CVE-2026-97714: Denial of service vulnerability in Secure Access

> Attackers can cause persistent denial of service in Secure Access servers by sending malformed authentication responses.

- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-x6hf-62r6-phf3

## What is CVE-2026-97714?

CVE-2026-97714 is a high-severity denial of service vulnerability in Absolute Security Secure Access, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CVE-2026-97714
is a is a vulnerability in the authentication sub-system of Secure Access
servers prior to version 14.60. Attackers can send a malformed response during
authentication and cause a persistent denial of service.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2026-97714?


## How do I fix CVE-2026-97714?

No fix has been published for CVE-2026-97714 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-97714 being exploited?

There is no known exploitation of CVE-2026-97714 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-97714 and fix it if it is affected.

What it is: CVE-2026-97714 is a high-severity denial of service vulnerability in Absolute Security Secure Access, published on 7 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-97714 in the wild and no public exploit code.

Affected product: Absolute Security Secure Access. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-97714/ (Markdown: https://insights.sbomify.com/CVE-2026-97714/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-97714
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-97714
- OSV: https://osv.dev/vulnerability/CVE-2026-97714

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-97714/
Summaries are generated and may contain mistakes; the official description above is the record.