dbcve.org
Secure AccessApplication · Absolute

CVE-2026-40957

HIGH · 7.5 CVSS v3.1 Published 2026-07-15
Fix available
A fix is available. Upgrade to 14.55 or later.
See remediation →
84/100
Remediation priority · High
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
o   CVE-2026-40957 is a frameable content vulnerability in the Secure Access server login page prior to 14.55. Attackers with control of a malicious web site could use it to potentially steal credentials from an unwary administrator.

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 frameable content (clickjacking) vulnerability in the Secure Access server login page prior to version 14.55 allows remote attackers to embed the login page within an iframe on a malicious website. Attackers can then overlay invisible or deceptive content to trick administrators into submitting their credentials to the attacker-controlled page.

MitigationUpgrade to Secure Access server version 14.55 or later. Alternatively, implement X-Frame-Options: DENY or SAMEORIGIN HTTP header, and/or Content-Security-Policy with frame-ancestors directive to prevent the login page from being embedded in iframes.

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

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

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 installed Absolute Secure Access version
    Locate the server version through its admin interface, command-line tools, or installed software inventory. Common methods include checking 'About' pages in the admin console, running 'show version' commands, or reviewing installation manifests.
    Affected if Installed version is below 14.55 (e.g., 14.54, 14.50, earlier releases)
  2. Inspect X-Frame-Options HTTP header on login page
    Use browser developer tools (Network tab), curl, or any HTTP client to request the login page URL and examine response headers. Look for 'X-Frame-Options' header.
    Affected if X-Frame-Options header is missing, or present but set to values other than DENY or SAMEORIGIN (e.g., ALLOW-FROM arbitrary-domain)
  3. Inspect Content-Security-Policy header on login page
    Examine the HTTP response headers from the login page for a 'Content-Security-Policy' header. Check if it includes the 'frame-ancestors' directive.
    Affected if Content-Security-Policy header is missing or does not include 'frame-ancestors' directive, or frame-ancestors allows arbitrary sources (e.g., frame-ancestors * or frame-ancestors untrusted-domain)
  4. Verify iframe embedding possibility
    Create a simple HTML page with an iframe src pointing to the Absolute Secure Access login page URL, then load it in a browser or use a headless browser to confirm whether the page renders inside the iframe.
    Affected if The login page successfully renders inside a third-party iframe (no X-Frame-Options DENY/SAMEORIGIN and no restrictive frame-ancestors)

You are affected if the installed Absolute Secure Access version is below 14.55 AND the login page lacks X-Frame-Options: DENY/SAMEORIGIN headers AND lacks Content-Security-Policy with restrictive frame-ancestors, allowing it to be embedded in iframes.

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 to Secure Access server version 14.55 or later. Alternatively, implement X-Frame-Options: DENY or SAMEORIGIN HTTP header, and/or Content-Security-Policy with frame-ancestors directive to prevent the login page from being embedded in iframes.

Recommended fix High confidence

14.55

  1. Upgrade Absolute Secure Access to version 14.55 or later to resolve the frameable content vulnerability

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-40957 — 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-40957 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