VulnerabilityPublished 12 Jun 2025Updated 17 Jun 2025

CVE-2025-49080: Absolute Security Secure Access · CWE-762

Affects Absolute Security Secure AccessSource CVE Database V5

Not known to be exploited · CVSS 8.7 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

8.7High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Absolute Security Secure Access	Affected =9.0	Fixed in–

AI-suggested

To mitigate this vulnerability effectively, European organizations should: 1) Immediately identify and inventory all Absolute Secure Access servers running affected versions (9.0 to 13.54). 2) Monitor vendor communications closely for official patches or updates and apply them promptly once available. 3) Implement network-level protections such as firewall rules or intrusion prevention systems (IPS) to restrict access to the Secure Access server only to trusted IP addresses and networks, minimizing exposure to untrusted sources. 4) Employ rate limiting and anomaly detection on network traffic directed at the Secure Access server to detect and block suspicious packet sequences that could trigger the vulnerability. 5) Consider deploying redundant or failover Secure Access servers to maintain availability in case of an attack. 6) Conduct regular penetration testing and vulnerability scanning focused on Secure Access infrastructure to detect exploitation attempts. 7) Review and tighten network segmentation to isolate Secure Access servers from general internet-facing segments where possible. These targeted measures go beyond generic advice by focusing on limiting attack surface, early detection, and operational continuity.

Description

There is a memory management vulnerability in Absolute Secure Access server versions 9.0 to 13.54. Attackers with network access to the server can cause a Denial of Service by sending a specially crafted sequence of packets to the server. The attack complexity is low, there are no attack requirements, privileges, or user interaction required. Loss of availability is high; there is no impact on confidentiality or integrity.

Impact

For European organizations, the impact of CVE-2025-49080 could be significant, especially for those relying on Absolute Secure Access for secure remote connectivity and access control. A successful DoS attack could disrupt remote access services, preventing employees and partners from securely connecting to corporate networks. This could halt critical business operations, delay response times, and reduce productivity. Sectors such as finance, healthcare, government, and critical infrastructure that depend on continuous secure access are particularly vulnerable. The lack of confidentiality or integrity impact means data breaches are unlikely, but the availability disruption alone can cause operational and reputational damage. Additionally, organizations with regulatory obligations for service availability and uptime (e.g., under GDPR or NIS Directive) may face compliance risks if the vulnerability is exploited. The low attack complexity and no requirement for authentication increase the risk of opportunistic attacks, especially in environments with exposed or poorly segmented network access to the Secure Access servers.

CWE-762Mismatched Memory Management Routines (opens in a new tab)
Variant weaknessLikelihood of exploit: Low
The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource.
Implementation
Only call matching memory management functions. Do not mix and match routines. For example, when you allocate a buffer with malloc(), dispose of the original pointer with free().
Implementation · Libraries or Frameworks
Choose a language or tool that provides automatic memory management, or makes manual memory management less error-prone.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

absolute.com/platform/security-information/vulnerability-archive/cve-2025-49080 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 12 Jun 2025, 17:38 UTC

WeaknessesCWE-762

Technical details

References

Community reviews

Related threats