CVE-2026-24828VulnerabilityPublished 27 Jan 2026

CVE-2026-24828: Is-Daouda is-Engine · Memory Leak

Affects Is-Daouda is-EngineSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 3.3.4 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
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: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within 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 27 Jan 2026
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-25.

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 is-Engine and is-daouda/is-Engine to 3.3.4.

Affected software

Product	Affected	Fixed in
Is-Daoudais-Engine	Affected <3.3.4	Fixed in 3.3.4
GitHubis-daouda/is-Engine`pkg:github/is-daouda/is-Engine`Other threats	Affected <3.3.4	Fixed in 3.3.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately inventory their deployments of is-Engine to identify affected versions prior to 3.3.4. If you cannot patch yet, implement resource monitoring to detect abnormal memory usage patterns indicative of exploitation attempts. Employ automated alerts for memory consumption thresholds to enable rapid response. Consider deploying application-level or network-level rate limiting to reduce the risk of sustained exploitation. Where feasible, isolate is-Engine instances in containerized or virtualized environments to limit the blast radius of potential crashes. Engage with the vendor or community for early patch releases or workarounds. Regularly update system and application logs to capture memory-related errors for forensic analysis. Plan for scheduled restarts of affected services as a temporary mitigation to reclaim leaked memory. Finally, incorporate this vulnerability into incident response and business continuity plans to minimize downtime impact.

Description

Missing Release of Memory after Effective Lifetime vulnerability in Is-Daouda is-Engine.This issue affects is-Engine: before 3.3.4.

Impact

For European organizations, this vulnerability poses a significant risk to service availability, especially for those relying on is-Engine in production environments. Memory exhaustion can lead to application crashes or system instability, resulting in downtime and potential disruption of business-critical services. Sectors such as finance, telecommunications, and government agencies that depend on continuous availability could face operational interruptions. Additionally, denial of service conditions might be exploited as part of broader attack campaigns, amplifying the impact. The absence of confidentiality or integrity impact reduces the risk of data breaches but does not diminish the operational threat. Organizations with limited capacity for rapid incident response or those running legacy versions of is-Engine are particularly vulnerable. The vulnerability could also increase operational costs due to the need for emergency remediation or system restarts.

CWE-401Missing Release of Memory after Effective Lifetime (opens in a new tab)
Variant weaknessLikelihood of exploit: Medium
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
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
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Architecture and Design · Build and Compilation
Consider using the Boehm-Demers-Weiser garbage collector (bdwgc), which can help avoid leaks.
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/Is-Daouda/is-Engine/pull/6 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Jan 2026, 17:20 UTC

WeaknessesCWE-401

Technical details

References

Community reviews

Related threats