<?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-09T18:39:53.087736+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-42052</id>
    <title>CVE-2026-42052 — beets is Vulnerable to XSS</title>
    <updated>2026-10-09T18:39:53.319370+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> beetbox beets</p>
<p>Beets is the media library management system. Prior to version 2.10.0, the bundled web UI uses Underscore template interpolation mode &lt;%= ... %&gt; for untrusted metadata fields. In this runtime, &lt;%= ... %&gt; is raw insertion and HTML escaping is only performed by &lt;%- ... %&gt;. Rendered output is then inserted with .html(...), allowing attacker-controlled markup to become active DOM. This issue has been patched in version 2.10.0.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-42052"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/usn-8747-1</id>
    <title>USN-8747-1 — beets vulnerability</title>
    <updated>2026-10-09T18:39:53.319492+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:16.04:LTS: beets, Ubuntu:Pro:18.04:LTS: beets, Ubuntu:Pro:20.04:LTS: beets, Ubuntu:Pro:22.04:LTS: beets, Ubuntu:Pro:24.04:LTS: beets, Ubuntu:Pro:26.04:LTS: beets</p>
<p>It was discovered that Beets incorrectly escaped untrusted media metadata
in its web interface. An attacker could possibly use this issue to inject
arbitrary HTML or execute arbitrary JavaScript code in a user's browser.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/usn-8747-1"/>
  </entry>
</feed>
