VulnerabilityPublished 1 Mar 2026Updated 2 Mar 2026

CVE-2026-3391: FascinatedBox lily · Out-of-bounds Read

Affects FascinatedBox lilySource CVE Database V5

Compare

Public exploit available · CVSS 4.8 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

4.8Medium

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

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

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

Base metrics

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

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Local: The vulnerable system 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 through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
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: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
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.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 1 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
FascinatedBoxlily	Affected 2.0 – 2.3 4 affected builds	Fixed in–
GitHubfascinatedbox/lily`pkg:github/fascinatedbox/lily`Other threats	Affected 2.0 – 2.3 4 affected builds	Fixed in–

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

AI-suggested

To mitigate CVE-2026-3391 effectively, organizations should implement strict local access controls to limit who can execute or interact with FascinatedBox lily binaries, especially the vulnerable versions 2.0 to 2.3. Employing mandatory access controls (e.g., SELinux, AppArmor) to restrict the process's memory access and user permissions can reduce exploitation risk. Monitoring and logging local user activity around the lily application can help detect suspicious behavior indicative of exploitation attempts. If possible, isolate systems running FascinatedBox lily to trusted users only and avoid multi-user environments where untrusted users have local access. Until an official patch is released, consider recompiling the software with added bounds checking or applying community-developed patches if available. Regularly check for vendor updates or security advisories. Additionally, conduct memory analysis and audits to detect abnormal memory access patterns. Employ endpoint detection and response (EDR) solutions that can alert on unusual local process behaviors. Finally, educate users about the risks of local exploitation and enforce strong authentication and session management to prevent unauthorized local access.

Description

A security flaw has been discovered in FascinatedBox lily up to 2.3. Impacted is the function clear_storages of the file src/lily_emitter.c. The manipulation results in out-of-bounds read. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The primary impact of CVE-2026-3391 is the potential unauthorized disclosure of sensitive information due to out-of-bounds memory reads. For organizations using FascinatedBox lily, this could lead to leakage of confidential data stored in memory, which might include credentials, cryptographic material, or other sensitive runtime information. Although the attack requires local access with low privileges, in environments where multiple users share systems or where attackers can gain limited local access (e.g., through compromised accounts or insider threats), this vulnerability could be leveraged to escalate information gathering. The lack of vendor response and patch increases the risk exposure. However, since the vulnerability does not allow remote exploitation or privilege escalation, the overall impact is contained but still significant in sensitive or multi-tenant environments. The availability and integrity of the system are not directly affected, but the confidentiality breach could facilitate further attacks or data exfiltration. Organizations with strict data confidentiality requirements or those operating in regulated industries should consider this vulnerability a moderate risk.

Summary

CVE-2026-3391 is a security vulnerability identified in FascinatedBox lily versions 2.0 through 2.3, involving an out-of-bounds read in the clear_storages function located in the source file src/lily_emitter.c. This vulnerability arises when the function improperly handles memory boundaries, allowing an attacker with local access to read data outside the allocated memory buffer. Such out-of-bounds reads can lead to unauthorized disclosure of sensitive information residing in adjacent memory regions, potentially including cryptographic keys, passwords, or other critical data. The attack vector requires the attacker to have local access with low privileges, and no user interaction or elevated privileges are necessary beyond that. The vulnerability does not affect confidentiality, integrity, or availability directly but poses a risk of information leakage. The CVSS v4.0 score of 4.8 reflects a medium severity, considering the limited attack vector (local access) and the absence of privilege escalation or remote exploitation. A public exploit is available, increasing the risk of exploitation by local attackers. No known exploits in the wild have been reported so far. This vulnerability highlights the importance of secure memory handling in software components and the risks posed by local attackers in multi-user environments.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Mar 2026, 01:22 UTC

Technical details

References

Community reviews

Related threats