<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 29 Sep 2026 19:39:07 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-55825</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55825</link>
      <description>&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55825</guid>
    </item>
    <item>
      <title>GHSA-grm4-wm43-9jh5 — Contao: Possible path traversal in job download URIs</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-grm4-wm43-9jh5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: contao/contao, Packagist: contao/core-bundle&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;`JobsController::downloadJobAttachment()` checks access to the route `jobUuid` before loading the attachment:&lt;/p&gt;
&lt;p&gt;```php
$job = $this-&amp;gt;jobs-&amp;gt;getByUuid($jobUuid);&lt;/p&gt;
&lt;p&gt;if (!$job || !$this-&amp;gt;jobs-&amp;gt;hasAccess($job)) {
    throw $this-&amp;gt;createNotFoundException();
}&lt;/p&gt;
&lt;p&gt;$attachment = $this-&amp;gt;jobs-&amp;gt;getAttachment($jobUuid, $identifier);
```&lt;/p&gt;
&lt;p&gt;`Jobs::getAttachment()` then resolves a path built from the authorized job UUID and the attacker-controlled identifier:&lt;/p&gt;
&lt;p&gt;```php
$fileItem = $this-&amp;gt;jobAttachmentsStorage-&amp;gt;get($this-&amp;gt;getAttachmentIdentifier($job, $identifier));
```&lt;/p&gt;
&lt;p&gt;```php
return $job-&amp;gt;getUuid().&amp;#39;/&amp;#39;.$identifier;
```&lt;/p&gt;
&lt;p&gt;`VirtualFilesystem::resolve()` canoni…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: contao/contao, Packagist: contao/core-bundle&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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`.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;## Root Cause&lt;/p&gt;
&lt;p&gt;`JobsController::downloadJobAttachment()` checks access to the route `jobUuid` before loading the attachment:&lt;/p&gt;
&lt;p&gt;```php
$job = $this-&amp;gt;jobs-&amp;gt;getByUuid($jobUuid);&lt;/p&gt;
&lt;p&gt;if (!$job || !$this-&amp;gt;jobs-&amp;gt;hasAccess($job)) {
    throw $this-&amp;gt;createNotFoundException();
}&lt;/p&gt;
&lt;p&gt;$attachment = $this-&amp;gt;jobs-&amp;gt;getAttachment($jobUuid, $identifier);
```&lt;/p&gt;
&lt;p&gt;`Jobs::getAttachment()` then resolves a path built from the authorized job UUID and the attacker-controlled identifier:&lt;/p&gt;
&lt;p&gt;```php
$fileItem = $this-&amp;gt;jobAttachmentsStorage-&amp;gt;get($this-&amp;gt;getAttachmentIdentifier($job, $identifier));
```&lt;/p&gt;
&lt;p&gt;```php
return $job-&amp;gt;getUuid().&amp;#39;/&amp;#39;.$identifier;
```&lt;/p&gt;
&lt;p&gt;`VirtualFilesystem::resolve()` canoni…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-grm4-wm43-9jh5</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1921 — Contao: Mehrere Schwachstellen ermöglichen Offenlegung von Informationen</title>
      <link>https://vulnerability.circl.lu/vuln/wid-sec-w-2026-1921</link>
      <description>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Contao ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Contao ausnutzen, um Informationen offenzulegen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/wid-sec-w-2026-1921</guid>
    </item>
  </channel>
</rss>
