{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81820 is a medium-severity cross-site scripting vulnerability in flowintel, published on 27 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-81820 and fix it if it is affected.\n\nWhat it is: CVE-2026-81820 is a medium-severity cross-site scripting vulnerability in flowintel, published on 27 Aug 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-81820 in the wild and no public exploit code.\n\nAffected product: flowintel. 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-81820/ (Markdown: https://insights.sbomify.com/CVE-2026-81820/index.md)","id":"CVE-2026-81820","markdown":"https://insights.sbomify.com/CVE-2026-81820/index.md","name":"CVE-2026-81820","record":{"aliases":["GHSA-cv7j-9q69-fxh4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Flowintel threat intelligence","requires_auth":"low_privilege","summary":"Attackers can inject malicious HTML into MISP case timelines via crafted object attributes, potentially leading to script execution or UI manipulation.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CIRCL","cpe":[],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Affected versions of Flowintel construct timeline HTML using attacker-controllable MISP object fields such as:\n\n  *  \nobject UUID;\n\n  *  \nobject name;\n\n  *  \nattribute value;\n\n  *  \nattribute type;\n\n  *  \ncomment;\n\n  *  \nfirst/last seen values;\n\n  *  \nIDS flag.\n\nThose values were concatenated directly into HTML strings before rendering. The upstream commit explicitly states that DOMPurify removed XSS vectors but still allowed other HTML elements, such as forms, through.\n\nThe fix replaces direct string interpolation with DOM construction via document.createElement() and assigns all attacker-controlled values using textContent. The headline is similarly converted to escaped HTML through a temporary element.\n\nVersion impacted =\u003e3.3.0","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Flowintel HTML Injection in MISP Case History Timeline via Crafted Object Attributes","id":"CVE-2026-81820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"AVEVA Pipeline Integrity Monitor Use of hard-coded cryptographic key","id":"CVE-2026-81821"},"packages":[],"prev":{"headline":"Flowintel Missing Authorization Allows Regular API Users to View Other Users’ Task Assignments","id":"CVE-2026-81819"},"products":["flowintel"],"published":"2026-08-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["flowintel"]},"summary":"Attackers can inject malicious HTML into MISP case timelines via crafted object attributes, potentially leading to script execution or UI manipulation.","url":"https://insights.sbomify.com/CVE-2026-81820/"}