{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3391 exists.","fix":"No fix has been published for CVE-2026-3391 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-3391 is a medium-severity memory corruption vulnerability in FascinatedBox lily, published on 1 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-3391 and fix it if it is affected.\n\nWhat it is: CVE-2026-3391 is a medium-severity memory corruption vulnerability in FascinatedBox lily, published on 1 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3391 exists.\n\nAffected product: FascinatedBox lily. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-3391/ (Markdown: https://insights.sbomify.com/CVE-2026-3391/index.md)","id":"CVE-2026-3391","markdown":"https://insights.sbomify.com/CVE-2026-3391/index.md","name":"CVE-2026-3391","record":{"aliases":["GHSA-3f6v-9prc-8grw"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Lily programming language","requires_auth":"low_privilege","summary":"A local attacker can trigger an out-of-bounds read in the Lily library's clear_storages function, potentially causing crashes or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"lily","vendor":"lily-lang"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"},{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"FascinatedBox lily lily_emitter.c clear_storages out-of-bounds","id":"CVE-2026-3391","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"FascinatedBox lily lily_emitter.c eval_tree null pointer dereference","id":"CVE-2026-3392"},"packages":[],"prev":{"headline":"FascinatedBox lily Error Reporting lily_build_error.c patch_line_end out-of-bounds","id":"CVE-2026-3390"},"products":["lily"],"published":"2026-03-01","related":[{"cvss_score":4.8,"headline":"FascinatedBox lily Error Reporting lily_build_error.c patch_line_end out-of-bounds","id":"CVE-2026-3390","kev_date_added":null,"published":"2026-03-01"},{"cvss_score":4.8,"headline":"FascinatedBox lily lily_emitter.c eval_tree null pointer dereference","id":"CVE-2026-3392","kev_date_added":null,"published":"2026-03-01"},{"cvss_score":4.8,"headline":"FascinatedBox lily lily_symtab.c shorthash_for_name use after free","id":"CVE-2026-2660","kev_date_added":null,"published":"2026-02-18"},{"cvss_score":4.8,"headline":"FascinatedBox lily lily_emitter.c count_transforms out-of-bounds","id":"CVE-2026-2662","kev_date_added":null,"published":"2026-02-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["FascinatedBox"]},"summary":"A local attacker can trigger an out-of-bounds read in the Lily library's clear_storages function, potentially causing crashes or information disclosure.","url":"https://insights.sbomify.com/CVE-2026-3391/"}