<?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://cve.radiocsirt.org</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>Fri, 09 Oct 2026 10:06:37 +0000</lastBuildDate>
    <item>
      <title>certfr-2021-avi-902 — De multiples vulnérabilités ont été découvertes dans Symfony. Elles
permettent à un attaquant de provoquer un contourne…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2021-avi-902</link>
      <description>certfr-2021-avi-902</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2021-avi-902</guid>
    </item>
    <item>
      <title>EUVD-2026-31634</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-31634</link>
      <description>EUVD-2026-31634</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-31634</guid>
    </item>
    <item>
      <title>fkie_cve-2021-41267</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2021-41267</link>
      <description>&lt;p&gt;Symfony/Http-Kernel is the HTTP kernel component for Symfony, a PHP framework for web and console applications and a set of reusable PHP components. Headers that are not part of the &amp;#34;trusted_headers&amp;#34; allowed list are ignored and protect users from &amp;#34;Cache poisoning&amp;#34; attacks. In Symfony 5.2, maintainers added support for the `X-Forwarded-Prefix` headers, but this header was accessible in SubRequest, even if it was not part of the &amp;#34;trusted_headers&amp;#34; allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` header, leading to a web cache poisoning issue. Versions 5.3.12 and later have a patch to ensure that the `X-Forwarded-Prefix` header is not forwarded to subrequests when it is not trusted.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Symfony/Http-Kernel is the HTTP kernel component for Symfony, a PHP framework for web and console applications and a set of reusable PHP components. Headers that are not part of the &amp;#34;trusted_headers&amp;#34; allowed list are ignored and protect users from &amp;#34;Cache poisoning&amp;#34; attacks. In Symfony 5.2, maintainers added support for the `X-Forwarded-Prefix` headers, but this header was accessible in SubRequest, even if it was not part of the &amp;#34;trusted_headers&amp;#34; allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` header, leading to a web cache poisoning issue. Versions 5.3.12 and later have a patch to ensure that the `X-Forwarded-Prefix` header is not forwarded to subrequests when it is not trusted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2021-41267</guid>
    </item>
    <item>
      <title>GHSA-q3j3-w37x-hq2q — Webcache Poisoning in symfony/http-kernel</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q3j3-w37x-hq2q</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: symfony/http-kernel, Packagist: symfony/symfony&lt;/p&gt;
&lt;p&gt;Description
-----------&lt;/p&gt;
&lt;p&gt;When a Symfony application is running behind a proxy or a load-balancer, you can tell Symfony to look for the `X-Forwarded-*` HTTP headers. HTTP headers that are not part of the &amp;#34;trusted_headers&amp;#34; allowed list are ignored and protect you from &amp;#34;Cache poisoning&amp;#34; attacks.&lt;/p&gt;
&lt;p&gt;In Symfony 5.2, we&amp;#39;ve added support for the `X-Forwarded-Prefix` header, but this header was accessible in sub-requests, even if it was not part of the &amp;#34;trusted_headers&amp;#34; allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` HTTP header, leading to a web cache poisoning issue.&lt;/p&gt;
&lt;p&gt;Resolution
----------&lt;/p&gt;
&lt;p&gt;Symfony now ensures that the `X-Forwarded-Prefix` HTTP header is not forwarded to sub-requests when it is not trusted.&lt;/p&gt;
&lt;p&gt;The patch for this issue is available [here](https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487) for branch 5.3.&lt;/p&gt;
&lt;p&gt;Credits
-------&lt;/p&gt;
&lt;p&gt;We would like to thank Soner Sayakci for reporting the issue and Jérémy Derussé for fixing the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: symfony/http-kernel, Packagist: symfony/symfony&lt;/p&gt;
&lt;p&gt;Description
-----------&lt;/p&gt;
&lt;p&gt;When a Symfony application is running behind a proxy or a load-balancer, you can tell Symfony to look for the `X-Forwarded-*` HTTP headers. HTTP headers that are not part of the &amp;#34;trusted_headers&amp;#34; allowed list are ignored and protect you from &amp;#34;Cache poisoning&amp;#34; attacks.&lt;/p&gt;
&lt;p&gt;In Symfony 5.2, we&amp;#39;ve added support for the `X-Forwarded-Prefix` header, but this header was accessible in sub-requests, even if it was not part of the &amp;#34;trusted_headers&amp;#34; allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` HTTP header, leading to a web cache poisoning issue.&lt;/p&gt;
&lt;p&gt;Resolution
----------&lt;/p&gt;
&lt;p&gt;Symfony now ensures that the `X-Forwarded-Prefix` HTTP header is not forwarded to sub-requests when it is not trusted.&lt;/p&gt;
&lt;p&gt;The patch for this issue is available [here](https://github.com/symfony/symfony/commit/95dcf51682029e89450aee86267e3d553aa7c487) for branch 5.3.&lt;/p&gt;
&lt;p&gt;Credits
-------&lt;/p&gt;
&lt;p&gt;We would like to thank Soner Sayakci for reporting the issue and Jérémy Derussé for fixing the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q3j3-w37x-hq2q</guid>
    </item>
    <item>
      <title>gsd-2021-41267</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2021-41267</link>
      <description>gsd-2021-41267</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2021-41267</guid>
    </item>
    <item>
      <title>Withdrawn: UBUNTU-CVE-2021-41267</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-41267</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: symfony, Ubuntu:24.10: symfony, Ubuntu:24.04:LTS: symfony&lt;/p&gt;
&lt;p&gt;Symfony/Http-Kernel is the HTTP kernel component for Symfony, a PHP framework for web and console applications and a set of reusable PHP components. Headers that are not part of the &amp;#34;trusted_headers&amp;#34; allowed list are ignored and protect users from &amp;#34;Cache poisoning&amp;#34; attacks. In Symfony 5.2, maintainers added support for the `X-Forwarded-Prefix` headers, but this header was accessible in SubRequest, even if it was not part of the &amp;#34;trusted_headers&amp;#34; allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` header, leading to a web cache poisoning issue. Versions 5.3.12 and later have a patch to ensure that the `X-Forwarded-Prefix` header is not forwarded to subrequests when it is not trusted.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: symfony, Ubuntu:24.10: symfony, Ubuntu:24.04:LTS: symfony&lt;/p&gt;
&lt;p&gt;Symfony/Http-Kernel is the HTTP kernel component for Symfony, a PHP framework for web and console applications and a set of reusable PHP components. Headers that are not part of the &amp;#34;trusted_headers&amp;#34; allowed list are ignored and protect users from &amp;#34;Cache poisoning&amp;#34; attacks. In Symfony 5.2, maintainers added support for the `X-Forwarded-Prefix` headers, but this header was accessible in SubRequest, even if it was not part of the &amp;#34;trusted_headers&amp;#34; allowed list. An attacker could leverage this opportunity to forge requests containing a `X-Forwarded-Prefix` header, leading to a web cache poisoning issue. Versions 5.3.12 and later have a patch to ensure that the `X-Forwarded-Prefix` header is not forwarded to subrequests when it is not trusted.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2021-41267</guid>
    </item>
  </channel>
</rss>
