<?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-09-29T19:39:07.659116+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/fkie_cve-2026-55825</id>
    <title>fkie_cve-2026-55825</title>
    <updated>2026-09-29T19:39:07.702336+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Contao is an Open Source CMS. In versions 5.7.0 through 5.7.6, an authenticated backend user who can access one job can request an attachment identifier containing ../ segments and make the job attachment download endpoint read a file from another job directory inside var/job-attachments. The controller authorizes only the jobUuid route parameter. The later attachment lookup joins that authorized job UUID with the attacker-controlled identifier, then passes the combined path to the virtual filesystem. VirtualFilesystem::resolve() canonicalizes the whole path and only rejects paths that escape the filesystem mount, so authorized-job/../victim-job/debug_log.csv becomes victim-job/debug_log.csv. This is a cross-job authorization bypass for known job attachment paths. It is not a practical brute-force against unknown jobs because job directories are UUID v4 values.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-55825"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-grm4-wm43-9jh5</id>
    <title>GHSA-grm4-wm43-9jh5 — Contao: Possible path traversal in job download URIs</title>
    <updated>2026-09-29T19:39:07.702421+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: contao/contao, Packagist: contao/core-bundle</p>
<p>## Summary</p>
<p>An authenticated backend user who can access one job can request an attachment identifier containing `../` segments and make the job attachment download endpoint read a file from another job directory inside `var/job-attachments`.</p>
<p>The controller authorizes only the `jobUuid` route parameter. The later attachment lookup joins that authorized job UUID with the attacker-controlled `identifier`, then passes the combined path to the virtual filesystem. `VirtualFilesystem::resolve()` canonicalizes the whole path and only rejects paths that escape the filesystem mount, so `authorized-job/../victim-job/debug_log.csv` becomes `victim-job/debug_log.csv`.</p>
<p>This is a cross-job authorization bypass for known job attachment paths. It is not a practical brute-force against unknown jobs because job directories are UUID v4 values.</p>
<p>## Root Cause</p>
<p>`JobsController::downloadJobAttachment()` checks access to the route `jobUuid` before loading the attachment:</p>
<p>```php
$job = $this-&gt;jobs-&gt;getByUuid($jobUuid);</p>
<p>if (!$job || !$this-&gt;jobs-&gt;hasAccess($job)) {
    throw $this-&gt;createNotFoundException();
}</p>
<p>$attachment = $this-&gt;jobs-&gt;getAttachment($jobUuid, $identifier);
```</p>
<p>`Jobs::getAttachment()` then resolves a path built from the authorized job UUID and the attacker-controlled identifier:</p>
<p>```php
$fileItem = $this-&gt;jobAttachmentsStorage-&gt;get($this-&gt;getAttachmentIdentifier($job, $identifier));
```</p>
<p>```php
return $job-&gt;getUuid().'/'.$identifier;
```</p>
<p>`VirtualFilesystem::resolve()` canoni…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-grm4-wm43-9jh5"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-1921</id>
    <title>WID-SEC-W-2026-1921 — Contao: Mehrere Schwachstellen ermöglichen Offenlegung von Informationen</title>
    <updated>2026-09-29T19:39:07.702503+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Contao ausnutzen, um Informationen offenzulegen.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/wid-sec-w-2026-1921"/>
  </entry>
</feed>
