VulnerabilityPublished 12 Dec 2025

CVE-2023-29144: Malwarebytes · CVE-2023-29144 is a low-severity

Source CVE Database V5

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

3.3Low

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
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: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 12 Dec 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

AI-suggested

Monitor Malwarebytes official channels for any forthcoming patches or updates addressing CVE-2023-29144 and apply them promptly once available.
Restrict local access to Linux systems running Malwarebytes to trusted users only, minimizing the risk of low-privilege attackers exploiting this vulnerability.
Employ additional endpoint detection and response (EDR) tools alongside Malwarebytes to provide layered malware detection capabilities.
Implement strict application whitelisting and behavior monitoring to detect anomalous activities that might bypass signature-based detection.
Regularly audit and harden Linux systems to reduce the attack surface and prevent unauthorized local access.
Conduct periodic security awareness training emphasizing the importance of maintaining endpoint security hygiene and recognizing suspicious activities.
Use network segmentation to limit potential lateral movement if malware evades detection on one system.

Description

CVE-2023-29144 is a low-severity vulnerability in Malwarebytes 1.0.14 for Linux where improper signature computation allows malware detection bypass. The flaw does not impact confidentiality or availability but can reduce the integrity of the malware detection process. Exploitation requires local access with low privileges and no user interaction is needed. There are no known exploits in the wild, and no patches have been released yet. European organizations using this specific Malwarebytes Linux version could face increased risk of undetected malware infections. Mitigation involves monitoring for updates from Malwarebytes and employing complementary security controls. Countries with higher Linux server usage and Malwarebytes deployment are more likely to be affected. Overall, the threat is limited in scope and impact but should be addressed to maintain endpoint security effectiveness.

Impact

For European organizations, the primary impact of CVE-2023-29144 is the potential reduction in the effectiveness of Malwarebytes 1.0.14 for Linux in detecting malware threats. This could lead to undetected malware infections, increasing the risk of persistent threats and lateral movement within networks. While the vulnerability does not compromise confidentiality or availability directly, the integrity of malware detection is weakened, which may delay incident detection and response. Organizations relying heavily on Malwarebytes for Linux endpoints, particularly in server environments or critical infrastructure, may face increased exposure to stealthy malware. However, since exploitation requires local access with low privileges and no known exploits exist, the immediate risk is limited. The lack of a patch also means organizations must rely on compensating controls until an update is available.

Summary

CVE-2023-29144 identifies a vulnerability in Malwarebytes version 1.0.14 for Linux, where the software fails to properly compute malware signatures under certain conditions. This flaw allows attackers to bypass detection mechanisms, effectively evading the antivirus protection provided by Malwarebytes. The vulnerability is categorized under CWE-190, which relates to integer overflow or wraparound issues that can lead to incorrect calculations or logic errors. The CVSS v3.1 base score is 3.3, indicating a low severity level. The attack vector is local (AV:L), requiring the attacker to have local access with low privileges (PR:L), and no user interaction (UI:N) is necessary. The scope is unchanged (S:U), and the impact affects integrity only (I:L), with no impact on confidentiality (C:N) or availability (A:N). No patches or fixes have been published at the time of this report, and no known exploits are currently active in the wild. The vulnerability could allow malware to remain undetected on Linux systems running this specific Malwarebytes version, potentially undermining endpoint security and incident response efforts.

CWE-190Integer Overflow or Wraparound (opens in a new tab)
Base weaknessLikelihood of exploit: Medium
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Requirements
Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
Requirements · Language Selection
Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
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.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V5.4.3 (opens in a new tab)
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 19 Dec 2025, 17:46 UTC

WeaknessesCWE-190

Technical details

References

Community reviews

Related threats