<?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-55824</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-55824</link>
      <description>&lt;p&gt;Contao is an Open Source CMS. In versions 4.13.40 through 5.3.46 and 5.7.0-RC1 through 5.7.6, the crawler leaks auth credentials to external hosts. Contao&amp;#39;s crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for root page origins, cleaned options for everything else. The cleaner removes Cookie and Authorization headers, but it removes the non-Symfony option names basic_auth and bearer_auth instead of Symfony HttpClient&amp;#39;s real auth_basic and auth_bearer options. When contao.crawl.default_http_client_options contains Basic or Bearer authentication for a protected staging/production site, those credentials remain in the &amp;#34;clean&amp;#34; client used for external links or configured additional URIs. An attacker who can get an external URL crawled, for example through a link on a crawled page while the broken-link checker is enabled, can receive the crawler credentials. This issue has been fixed in versions 5.3.47 and 5.7.7.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Contao is an Open Source CMS. In versions 4.13.40 through 5.3.46 and 5.7.0-RC1 through 5.7.6, the crawler leaks auth credentials to external hosts. Contao&amp;#39;s crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for root page origins, cleaned options for everything else. The cleaner removes Cookie and Authorization headers, but it removes the non-Symfony option names basic_auth and bearer_auth instead of Symfony HttpClient&amp;#39;s real auth_basic and auth_bearer options. When contao.crawl.default_http_client_options contains Basic or Bearer authentication for a protected staging/production site, those credentials remain in the &amp;#34;clean&amp;#34; client used for external links or configured additional URIs. An attacker who can get an external URL crawled, for example through a link on a crawled page while the broken-link checker is enabled, can receive the crawler credentials. This issue has been fixed in versions 5.3.47 and 5.7.7.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-55824</guid>
    </item>
    <item>
      <title>GHSA-3mr9-p497-58f6 — Contao crawler leaks auth credentials to external hosts</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-3mr9-p497-58f6</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
Contao&amp;#39;s crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for root page origins, cleaned options for everything else. The cleaner removes `Cookie` and `Authorization` headers, but it removes the non-Symfony option names `basic_auth` and `bearer_auth` instead of Symfony HttpClient&amp;#39;s real `auth_basic` and `auth_bearer` options.&lt;/p&gt;
&lt;p&gt;When `contao.crawl.default_http_client_options` contains Basic or Bearer authentication for a protected staging/production site, those credentials remain in the &amp;#34;clean&amp;#34; client used for external links or configured additional URIs. An attacker who can get an external URL crawled, for example through a link on a crawled page while the broken-link checker is enabled, can receive the crawler credentials.&lt;/p&gt;
&lt;p&gt;## Technical Detail&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;```php
// core-bundle/src/Crawl/Escargot/Factory.php:175-209 @ e550b92a01ef625bd546e6c3956dd200af05ebf0
private function createHttpClient(array $options = []): HttpClientInterface
{
    $options = array_merge_recursive(
        [
            &amp;#39;headers&amp;#39; =&amp;gt; [
                &amp;#39;accept&amp;#39; =&amp;gt; &amp;#39;text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8&amp;#39;,
                &amp;#39;user-agent&amp;#39; =&amp;gt; self::USER_AGENT,
            ],
            &amp;#39;max_duration&amp;#39; =&amp;gt; 10,
        ],
        array_merge_recursive($this-&amp;gt;getDefaultHttpClientOptions(), $options),
    );&lt;/p&gt;
&lt;p&gt;$cleanOptions = $this-&amp;gt;cleanOptionsFromConfidentialData($options);&lt;/p&gt;
&lt;p&gt;if (…&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
Contao&amp;#39;s crawler tries to prevent confidential HTTP client options from being sent to external domains by creating a scoped client: full options for root page origins, cleaned options for everything else. The cleaner removes `Cookie` and `Authorization` headers, but it removes the non-Symfony option names `basic_auth` and `bearer_auth` instead of Symfony HttpClient&amp;#39;s real `auth_basic` and `auth_bearer` options.&lt;/p&gt;
&lt;p&gt;When `contao.crawl.default_http_client_options` contains Basic or Bearer authentication for a protected staging/production site, those credentials remain in the &amp;#34;clean&amp;#34; client used for external links or configured additional URIs. An attacker who can get an external URL crawled, for example through a link on a crawled page while the broken-link checker is enabled, can receive the crawler credentials.&lt;/p&gt;
&lt;p&gt;## Technical Detail&lt;/p&gt;
&lt;p&gt;### Root Cause&lt;/p&gt;
&lt;p&gt;```php
// core-bundle/src/Crawl/Escargot/Factory.php:175-209 @ e550b92a01ef625bd546e6c3956dd200af05ebf0
private function createHttpClient(array $options = []): HttpClientInterface
{
    $options = array_merge_recursive(
        [
            &amp;#39;headers&amp;#39; =&amp;gt; [
                &amp;#39;accept&amp;#39; =&amp;gt; &amp;#39;text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8&amp;#39;,
                &amp;#39;user-agent&amp;#39; =&amp;gt; self::USER_AGENT,
            ],
            &amp;#39;max_duration&amp;#39; =&amp;gt; 10,
        ],
        array_merge_recursive($this-&amp;gt;getDefaultHttpClientOptions(), $options),
    );&lt;/p&gt;
&lt;p&gt;$cleanOptions = $this-&amp;gt;cleanOptionsFromConfidentialData($options);&lt;/p&gt;
&lt;p&gt;if (…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-3mr9-p497-58f6</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>
