<?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>Wed, 07 Oct 2026 16:29:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-42665</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-42665</link>
      <description>EUVD-2026-42665</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-42665</guid>
    </item>
    <item>
      <title>fkie_cve-2020-15094</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2020-15094</link>
      <description>&lt;p&gt;In Symfony before versions 4.4.13 and 5.1.5, the CachingHttpClient class from the HttpClient Symfony component relies on the HttpCache class to handle requests. HttpCache uses internal headers like X-Body-Eval and X-Body-File to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient and if an attacker can control the response for a request being made by the CachingHttpClient, remote code execution is possible. This has been fixed in versions 4.4.13 and 5.1.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In Symfony before versions 4.4.13 and 5.1.5, the CachingHttpClient class from the HttpClient Symfony component relies on the HttpCache class to handle requests. HttpCache uses internal headers like X-Body-Eval and X-Body-File to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by CachingHttpClient and if an attacker can control the response for a request being made by the CachingHttpClient, remote code execution is possible. This has been fixed in versions 4.4.13 and 5.1.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2020-15094</guid>
    </item>
    <item>
      <title>GHSA-754h-5r27-7x3r — RCE in Symfony</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-754h-5r27-7x3r</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;The `CachingHttpClient` class from the HttpClient Symfony component relies on the `HttpCache` class to handle requests. `HttpCache` uses internal headers like `X-Body-Eval` and `X-Body-File` to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by `CachingHttpClient` and if an attacker can control the response for a request being made by the `CachingHttpClient`, remote code execution is possible.&lt;/p&gt;
&lt;p&gt;Resolution
----------&lt;/p&gt;
&lt;p&gt;HTTP headers designed for internal use in `HttpCache` are now stripped from remote responses before being passed to `HttpCache`.&lt;/p&gt;
&lt;p&gt;The patch for this issue is available [here](https://github.com/symfony/symfony/commit/d9910e0b33a2e0f993abff41c6fbc86951b66d78) for the 4.4 branch.&lt;/p&gt;
&lt;p&gt;Credits
-------&lt;/p&gt;
&lt;p&gt;I would like to thank Matthias Pigulla (webfactory GmbH) for reporting and 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;The `CachingHttpClient` class from the HttpClient Symfony component relies on the `HttpCache` class to handle requests. `HttpCache` uses internal headers like `X-Body-Eval` and `X-Body-File` to control the restoration of cached responses. The class was initially written with surrogate caching and ESI support in mind (all HTTP calls come from a trusted backend in that scenario). But when used by `CachingHttpClient` and if an attacker can control the response for a request being made by the `CachingHttpClient`, remote code execution is possible.&lt;/p&gt;
&lt;p&gt;Resolution
----------&lt;/p&gt;
&lt;p&gt;HTTP headers designed for internal use in `HttpCache` are now stripped from remote responses before being passed to `HttpCache`.&lt;/p&gt;
&lt;p&gt;The patch for this issue is available [here](https://github.com/symfony/symfony/commit/d9910e0b33a2e0f993abff41c6fbc86951b66d78) for the 4.4 branch.&lt;/p&gt;
&lt;p&gt;Credits
-------&lt;/p&gt;
&lt;p&gt;I would like to thank Matthias Pigulla (webfactory GmbH) for reporting and fixing the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-754h-5r27-7x3r</guid>
    </item>
    <item>
      <title>gsd-2020-15094</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2020-15094</link>
      <description>gsd-2020-15094</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2020-15094</guid>
    </item>
  </channel>
</rss>
