dbcve.org
Secure AccessApplication · Absolute

CVE-2025-49084

CRITICAL · 9.1 CVSS v3.1 Published 2025-07-31
Fix available
A fix is available. Upgrade to 13.56 or later.
See remediation →
97/100
Remediation priority · Urgent
Remotely reachable 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-2025-49084 is a vulnerability in the management console of Absolute Secure Access prior to version 13.56. Attackers with administrative access can overwrite policy rules without the requisite permissions. The attack complexity is low, attack requirements are present, privileges required are high and no user interaction is required. There is no impact to confidentiality, the impact to integrity is low, and there is no impact to availability. The impact to confidentiality and availability of subsequent systems is high and the impact to the integrity of subsequent systems is low.

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

Absolute Secure Access management console prior to version 13.56 contains an authorization bypass vulnerability where attackers with administrative-level access can overwrite policy rules without the requisite permissions, enabling modification of security policies they should not have rights to modify.

MitigationUpgrade Absolute Secure Access client and management console to version 13.56 or later to remediate this authorization bypass 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:< 13.56

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/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 Absolute Secure Access is installed
    Check the installed applications or services on the system for 'Absolute Secure Access' or run 'Get-Process' or list installed software via system inventory tools
    Affected if Absolute Secure Access software is present on the system
  2. Identify installed version
    Use the product's built-in version check mechanism, typically via 'Help > About' in the client UI, or check the executable version property (right-click the application binary > Properties > Details)
    Affected if The installed version number is lower than 13.56 (e.g., 13.55, 13.50, etc.)
  3. Verify management console access
    Check if the Absolute Secure Access management console interface is accessible - this is typically a web-based console accessible via browser or a dedicated client component
    Affected if The management console is reachable and the user has administrative privileges to view or modify policy rules
  4. Review policy rule configurations
    Navigate to the policy rules section within the management console and inspect existing rules for unexpected modifications, duplicates, or rules that override core security controls
    Affected if Policy rules have been altered without proper authorization records or contain configurations that bypass intended security controls

A system is affected if Absolute Secure Access version is below 13.56 AND the management console with administrative access is in use, allowing potential unauthorized policy rule modifications.

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 13.56 or later
Fixed in 13.56
Interim mitigation

Upgrade Absolute Secure Access client and management console to version 13.56 or later to remediate this authorization bypass vulnerability.

Recommended fix High confidence

version 13.56

  1. Back up the current Absolute Secure Access configuration before proceeding with the update
  2. Download the Absolute Secure Access version 13.56 (or later) update package from the official Absolute vendor portal at www.absolute.com
  3. Review the vendor's official upgrade documentation for version 13.56
  4. Apply the update to the management console following the documented upgrade procedure
  5. After upgrade completion, verify that the management console is running version 13.56 or later
  6. Confirm that administrative users can no longer overwrite policy rules without requisite permissions

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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