{"answers":{"affected":"1 open source package ship an affected version, including lollms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1116 exists.","fix":"Upgrade lollms to 2.1.1 or later.","what":"CVE-2026-1116 is a high-severity cross-site scripting vulnerability in parisneo/lollms, published on 12 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-1116 and fix it if it is affected.\n\nWhat it is: CVE-2026-1116 is a high-severity cross-site scripting vulnerability in parisneo/lollms, published on 12 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-1116 exists.\n\nAffected packages and fixed versions:\n- lollms (PyPI): affected all versions; fixed in 2.1.1\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-1116/ (Markdown: https://insights.sbomify.com/CVE-2026-1116/index.md)","id":"CVE-2026-1116","markdown":"https://insights.sbomify.com/CVE-2026-1116/index.md","name":"CVE-2026-1116","record":{"aliases":["GHSA-w676-j9x4-3hq2","PYSEC-2026-2200"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python LLM library","requires_auth":"none","summary":"Attackers can inject malicious scripts via unsanitized content fields, leading to account takeover or session hijacking in lollms applications.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"@huntr_ai","cpe":[{"product":"lollms","vendor":"lollms"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A Cross-site Scripting (XSS) vulnerability was identified in the `from_dict` method of the `AppLollmsMessage` class in parisneo/lollms prior to version 2.2.0. The vulnerability arises from the lack of sanitization or HTML encoding of the `content` field when deserializing user-provided data. This allows an attacker to inject malicious HTML or JavaScript payloads, which can be executed in the context of another user's browser. Exploitation of this vulnerability can lead to account takeover, session hijacking, or wormable attacks.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Cross-site Scripting (XSS) in parisneo/lollms","id":"CVE-2026-1116","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":1,"n_references":2,"next":{"headline":"Improper Access Control in parisneo/lollms","id":"CVE-2026-1117"},"packages":[{"ecosystem":"PyPI","fixed":["2.1.1"],"introduced":["0"],"last_affected":[],"package":"lollms","purl":"pkg:pypi/lollms","source":"PYSEC-2026-2200"}],"prev":{"headline":"Stored XSS in parisneo/lollms","id":"CVE-2026-1115"},"products":["parisneo/lollms"],"published":"2026-04-12","related":[{"cvss_score":9.8,"headline":"Improper Access Control via Weak JWT Token in parisneo/lollms","id":"CVE-2026-1114","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":9.8,"headline":"Path Traversal in parisneo/lollms","id":"CVE-2024-3429","kev_date_added":null,"published":"2024-06-06"},{"cvss_score":9.6,"headline":"Stored XSS in parisneo/lollms","id":"CVE-2026-1115","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":8.7,"headline":"Stored XSS in Direct Messages via Prompt Sharing in parisneo/lollms","id":"CVE-2026-12228","kev_date_added":null,"published":"2026-07-18"},{"cvss_score":8.3,"headline":"Insecure Direct Object Reference (IDOR) in parisneo/lollms","id":"CVE-2026-0562","kev_date_added":null,"published":"2026-03-29"},{"cvss_score":7.6,"headline":"CSRF Vulnerability in parisneo/lollms XTTS Server","id":"CVE-2024-4499","kev_date_added":null,"published":"2024-06-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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-04-13","vendors":["parisneo"]},"summary":"Attackers can inject malicious scripts via unsanitized content fields, leading to account takeover or session hijacking in lollms applications.","url":"https://insights.sbomify.com/CVE-2026-1116/"}