<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T20:07:37.545091+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-81820</id>
    <title>CVE-2026-81820 — Flowintel HTML Injection in MISP Case History Timeline via Crafted Object Attributes</title>
    <updated>2026-10-04T20:07:38.721197+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> flowintel</p>
<p>Affected versions of Flowintel construct timeline HTML using attacker-controllable MISP object fields such as:</p>
<p>*  
object UUID;</p>
<p>*  
object name;</p>
<p>*  
attribute value;</p>
<p>*  
attribute type;</p>
<p>*  
comment;</p>
<p>*  
first/last seen values;</p>
<p>*  
IDS flag.</p>
<p>Those 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.</p>
<p>The 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.</p>
<p>Version impacted =&gt;3.3.0</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-81820"/>
  </entry>
</feed>
