<?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-01T17:05:35.397090+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/bdu:2026-09353</id>
    <title>bdu:2026-09353</title>
    <updated>2026-10-01T17:05:35.912364+00:00</updated>
    <content>bdu:2026-09353</content>
    <link href="https://vulnerability.circl.lu/vuln/bdu:2026-09353"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2025-12474</id>
    <title>CVE-2025-12474 — libjxl: Uninitialized memory read in decoder due to incorrect optimization in patch handling</title>
    <updated>2026-10-01T17:05:35.912465+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Google libjxl</p>
<p>A specially-crafted file can cause libjxl's decoder to read pixel data from uninitialized (but allocated) memory.</p>
<p>This can be done by causing the decoder to reference an outside-image-bound area in a subsequent patches. An incorrect optimization causes the decoder to omit populating those areas.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-12474"/>
  </entry>
</feed>
