CVE-2025-64693VulnerabilityPublished 25 Nov 2025

CVE-2025-64693: Intercom Security Point (Windows) of MaLion · Heap-based buffer overflow

Affects Intercom Security Point (Windows) of MaLionSource CVE Database V5

Not known to be exploited · CVSS 9.8 Critical : upgrade to 7.1.1.9 as a priority.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.0 base score

9.8Critical

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

EPSS: 0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 7.1.1.9

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, 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: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; 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 impacted component (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).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 25 Nov 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 2026-10-26.

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

Upgrade Intercom Security Point (Windows) of MaLion to 7.1.1.9.

Affected software

Product	Affected	Fixed in
Intercom, Inc. Security Point (Windows) of MaLion	Affected <7.1.1.9	Fixed in 7.1.1.9

AI-suggested

1. Immediately upgrade all instances of Security Point (Windows) of MaLion to version 7.1.1.9 or later, where the vulnerability is patched. 2. Implement network-level filtering to restrict access to the Security Point service from untrusted networks, using firewalls or segmentation to limit exposure. 3. Deploy intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics capable of detecting anomalous Content-Length header manipulations. 4. Conduct thorough logging and monitoring of network traffic to identify suspicious requests targeting the Content-Length header. 5. Apply strict input validation and sanitization on all incoming requests where possible, to prevent malformed headers from reaching vulnerable code paths. 6. Perform regular vulnerability scanning and penetration testing focused on this vulnerability to ensure remediation effectiveness. 7. Develop and test incident response plans specifically addressing potential exploitation scenarios involving this vulnerability. 8. Educate IT and security teams about the nature of this vulnerability and the importance of timely patching and monitoring.

Description

Security Point (Windows) of MaLion and MaLionCloud contains a heap-based buffer overflow vulnerability in processing Content-Length. Receiving a specially crafted request from a remote unauthenticated attacker could lead to arbitrary code execution with SYSTEM privilege.

Impact

For European organizations, the impact of CVE-2025-64693 is significant. The ability for an unauthenticated remote attacker to execute arbitrary code with SYSTEM privileges means complete takeover of affected systems is possible. This can lead to data breaches involving sensitive personal and corporate data, disruption of critical services, and potential lateral movement within networks to compromise additional assets. Organizations in sectors such as finance, healthcare, government, and critical infrastructure are particularly at risk due to the high value of their data and services. The vulnerability could also be leveraged to deploy ransomware or other malware, causing operational downtime and financial losses. Given the widespread use of Windows environments and the presence of MaLion Security Point in enterprise security stacks, the scope of affected systems could be broad. The lack of known exploits in the wild currently provides a window for proactive defense, but the critical severity demands urgent attention to prevent future exploitation. Failure to address this vulnerability could result in regulatory penalties under GDPR if personal data is compromised.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 2 Dec 2025, 14:43 UTC

Technical details

References

Community reviews

Related threats