<?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://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T04:13:10.642506+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" 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://cve.radiocsirt.org/vuln/cve-2026-45711</id>
    <title>CVE-2026-45711 — Mailpit: Path traversal &amp; arbitrary file write in mailpit dump --http via attacker-controlled message IDs</title>
    <updated>2026-10-07T04:13:10.666498+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> axllent mailpit</p>
<p>Mailpit is an email testing tool and API for developers. Prior to version 1.30.0, the mailpit dump --http &lt;base-url&gt; &lt;out-dir&gt; sub-command downloads every message from a remote Mailpit instance and writes each one as &lt;id&gt;.eml inside the user-supplied output directory. The message ID field is taken verbatim from the JSON response of the remote server and concatenated into the output path with path.Join, which silently normalizes `..` segments. A malicious HTTP server impersonating Mailpit can therefore make mailpit dump write attacker-controlled bytes to any path the running user can write, fully outside the intended output directory. Version 1.30.0 contains a patch.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-45711"/>
  </entry>
</feed>
