CVE-2026-2660: Use After Free in FascinatedBox lily
A vulnerability was identified in FascinatedBox lily up to 2.3. Affected by this issue is the function shorthash_for_name of the file src/lily_symtab.c. The manipulation leads to use after free. Local access is required to approach this attack. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
AI Analysis
Technical Summary
CVE-2026-2660 is a use-after-free vulnerability discovered in the FascinatedBox lily software, affecting versions 2.0 through 2.3. The flaw resides in the function shorthash_for_name within the source file src/lily_symtab.c. Use-after-free occurs when the program continues to use memory after it has been freed, leading to undefined behavior such as memory corruption, crashes, or potential arbitrary code execution. This vulnerability requires local access with low privileges (PR:L) and does not require user interaction (UI:N), making it exploitable by a local attacker or malicious insider. The CVSS 4.0 vector indicates low attack complexity and no need for authentication beyond local access. Although the CVSS score is medium (4.8), the availability of a public exploit increases the threat level. The vendor has been informed but has not yet issued a patch, leaving systems exposed. The vulnerability could be leveraged to escalate privileges or disrupt application stability, especially in environments where lily is used for development or scripting. The lack of vendor response and patch availability necessitates immediate mitigation steps by users. No known exploits in the wild have been reported yet, but the public exploit presence suggests potential future attacks.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems where FascinatedBox lily is installed and used, especially in development or scripting contexts. The use-after-free flaw can lead to application crashes, denial of service, or potentially arbitrary code execution if exploited successfully. This could compromise confidentiality, integrity, and availability of affected systems. Since exploitation requires local access, the threat is heightened in environments with multiple users or insufficient access controls. Organizations relying on lily for internal tooling or automation may face operational disruptions. The presence of a public exploit increases the likelihood of exploitation attempts, particularly in insider threat scenarios or compromised endpoints. The medium severity rating suggests moderate impact, but the absence of patches and vendor response could prolong exposure. European entities with sensitive or critical infrastructure using this software could see increased risk of targeted attacks or insider misuse.
Mitigation Recommendations
1. Immediately restrict local access to systems running FascinatedBox lily to trusted users only, employing strict access control and monitoring. 2. Implement host-based intrusion detection systems (HIDS) to detect anomalous behavior or exploitation attempts related to memory corruption. 3. Isolate systems running lily in segmented network zones to limit lateral movement in case of compromise. 4. Regularly audit and review user privileges to minimize the number of users with local access. 5. Monitor public sources and vendor communications for patch releases or updates addressing CVE-2026-2660 and apply them promptly. 6. Consider deploying application whitelisting or sandboxing techniques to limit the impact of potential exploitation. 7. Educate internal users about the risks of local exploitation and enforce policies to prevent unauthorized software installation or execution. 8. If feasible, temporarily disable or replace the affected versions of lily with alternative tools until a patch is available.
Affected Countries
Germany, France, United Kingdom, Netherlands, Sweden, Finland
CVE-2026-2660: Use After Free in FascinatedBox lily
Description
A vulnerability was identified in FascinatedBox lily up to 2.3. Affected by this issue is the function shorthash_for_name of the file src/lily_symtab.c. The manipulation leads to use after free. Local access is required to approach this attack. The exploit is publicly available and might be used. The project was informed of the problem early through an issue report but has not responded yet.
AI-Powered Analysis
Technical Analysis
CVE-2026-2660 is a use-after-free vulnerability discovered in the FascinatedBox lily software, affecting versions 2.0 through 2.3. The flaw resides in the function shorthash_for_name within the source file src/lily_symtab.c. Use-after-free occurs when the program continues to use memory after it has been freed, leading to undefined behavior such as memory corruption, crashes, or potential arbitrary code execution. This vulnerability requires local access with low privileges (PR:L) and does not require user interaction (UI:N), making it exploitable by a local attacker or malicious insider. The CVSS 4.0 vector indicates low attack complexity and no need for authentication beyond local access. Although the CVSS score is medium (4.8), the availability of a public exploit increases the threat level. The vendor has been informed but has not yet issued a patch, leaving systems exposed. The vulnerability could be leveraged to escalate privileges or disrupt application stability, especially in environments where lily is used for development or scripting. The lack of vendor response and patch availability necessitates immediate mitigation steps by users. No known exploits in the wild have been reported yet, but the public exploit presence suggests potential future attacks.
Potential Impact
For European organizations, this vulnerability poses a risk primarily to systems where FascinatedBox lily is installed and used, especially in development or scripting contexts. The use-after-free flaw can lead to application crashes, denial of service, or potentially arbitrary code execution if exploited successfully. This could compromise confidentiality, integrity, and availability of affected systems. Since exploitation requires local access, the threat is heightened in environments with multiple users or insufficient access controls. Organizations relying on lily for internal tooling or automation may face operational disruptions. The presence of a public exploit increases the likelihood of exploitation attempts, particularly in insider threat scenarios or compromised endpoints. The medium severity rating suggests moderate impact, but the absence of patches and vendor response could prolong exposure. European entities with sensitive or critical infrastructure using this software could see increased risk of targeted attacks or insider misuse.
Mitigation Recommendations
1. Immediately restrict local access to systems running FascinatedBox lily to trusted users only, employing strict access control and monitoring. 2. Implement host-based intrusion detection systems (HIDS) to detect anomalous behavior or exploitation attempts related to memory corruption. 3. Isolate systems running lily in segmented network zones to limit lateral movement in case of compromise. 4. Regularly audit and review user privileges to minimize the number of users with local access. 5. Monitor public sources and vendor communications for patch releases or updates addressing CVE-2026-2660 and apply them promptly. 6. Consider deploying application whitelisting or sandboxing techniques to limit the impact of potential exploitation. 7. Educate internal users about the risks of local exploitation and enforce policies to prevent unauthorized software installation or execution. 8. If feasible, temporarily disable or replace the affected versions of lily with alternative tools until a patch is available.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulDB
- Date Reserved
- 2026-02-18T07:25:33.125Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6996fb498fb9188dea8c09a0
Added to database: 2/19/2026, 12:00:09 PM
Last enriched: 2/19/2026, 12:05:56 PM
Last updated: 2/21/2026, 12:22:04 AM
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-27203: CWE-15: External Control of System or Configuration Setting in YosefHayim ebay-mcp
HighCVE-2026-27168: CWE-122: Heap-based Buffer Overflow in HappySeaFox sail
HighCVE-2026-27134: CWE-287: Improper Authentication in strimzi strimzi-kafka-operator
HighCVE-2026-27190: CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in denoland deno
HighCVE-2026-27026: CWE-770: Allocation of Resources Without Limits or Throttling in py-pdf pypdf
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.