<?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>Sat, 03 Oct 2026 07:45:58 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-233754</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233754</link>
      <description>EUVD-2026-233754</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233754</guid>
    </item>
    <item>
      <title>fkie_cve-2022-36032</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36032</link>
      <description>&lt;p&gt;ReactPHP HTTP is a streaming HTTP client and server implementation for ReactPHP. In ReactPHP&amp;#39;s HTTP server component versions starting with 0.7.0 and prior to 1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. This issue is fixed in ReactPHP HTTP version 1.7.0. As a workaround, Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ReactPHP HTTP is a streaming HTTP client and server implementation for ReactPHP. In ReactPHP&amp;#39;s HTTP server component versions starting with 0.7.0 and prior to 1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. This issue is fixed in ReactPHP HTTP version 1.7.0. As a workaround, Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-36032</guid>
    </item>
    <item>
      <title>GHSA-w3w9-vrf5-8mx8 — ReactPHP's HTTP server parses encoded cookie names so malicious `__Host-` and `__Secure-` cookies can be sent</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w3w9-vrf5-8mx8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: react/http&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In ReactPHP&amp;#39;s HTTP server component versions below v1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. See also CVE-2020-7070 and CVE-2020-8184 for more information.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;* https://github.com/reactphp/http/commit/663c9a3b77b71463fa7fcb76a6676ffd16979dd6 - Fixed in [reactphp/http `v1.7.0`](https://github.com/reactphp/http/releases/tag/v1.7.0)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* CVE-2020-7070, https://bugs.php.net/bug.php?id=79699 and https://github.com/php/php-src/commit/6559fe912661ca5ce5f0eeeb591d928451428ed0
* CVE-2020-8184, https://hackerone.com/reports/895727 and https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c
* Originally introduced via https://github.com/reactphp/http/pull/175&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;* Thanks to Marco Squarcina (TU Wien) for reporting this and working with us to coordinate this security advisory&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* [Join the discussion](https://github.com/orgs/reactphp/discussions/465)
* Email us at support@reactphp.org&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: react/http&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In ReactPHP&amp;#39;s HTTP server component versions below v1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. See also CVE-2020-7070 and CVE-2020-8184 for more information.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;* https://github.com/reactphp/http/commit/663c9a3b77b71463fa7fcb76a6676ffd16979dd6 - Fixed in [reactphp/http `v1.7.0`](https://github.com/reactphp/http/releases/tag/v1.7.0)&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;* CVE-2020-7070, https://bugs.php.net/bug.php?id=79699 and https://github.com/php/php-src/commit/6559fe912661ca5ce5f0eeeb591d928451428ed0
* CVE-2020-8184, https://hackerone.com/reports/895727 and https://github.com/rack/rack/commit/1f5763de6a9fe515ff84992b343d63c88104654c
* Originally introduced via https://github.com/reactphp/http/pull/175&lt;/p&gt;
&lt;p&gt;### Credits&lt;/p&gt;
&lt;p&gt;* Thanks to Marco Squarcina (TU Wien) for reporting this and working with us to coordinate this security advisory&lt;/p&gt;
&lt;p&gt;### For more information&lt;/p&gt;
&lt;p&gt;If you have any questions or comments about this advisory:&lt;/p&gt;
&lt;p&gt;* [Join the discussion](https://github.com/orgs/reactphp/discussions/465)
* Email us at support@reactphp.org&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w3w9-vrf5-8mx8</guid>
    </item>
    <item>
      <title>gsd-2022-36032</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-36032</link>
      <description>gsd-2022-36032</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-36032</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2022-36032</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-36032</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: icinga-php-thirdparty, Ubuntu:22.04:LTS: icingaweb2-module-reactbundle, Ubuntu:24.04:LTS: icinga-php-thirdparty, Ubuntu:24.04:LTS: icingaweb2-module-reactbundle, Ubuntu:25.10: icinga-php-thirdparty, Ubuntu:25.10: icingaweb2-module-reactbundle, Ubuntu:26.04:LTS: icinga-php-thirdparty, Ubuntu:26.04:LTS: icingaweb2-module-reactbundle&lt;/p&gt;
&lt;p&gt;ReactPHP HTTP is a streaming HTTP client and server implementation for ReactPHP. In ReactPHP&amp;#39;s HTTP server component versions starting with 0.7.0 and prior to 1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. This issue is fixed in ReactPHP HTTP version 1.7.0. As a workaround, Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:22.04:LTS: icinga-php-thirdparty, Ubuntu:22.04:LTS: icingaweb2-module-reactbundle, Ubuntu:24.04:LTS: icinga-php-thirdparty, Ubuntu:24.04:LTS: icingaweb2-module-reactbundle, Ubuntu:25.10: icinga-php-thirdparty, Ubuntu:25.10: icingaweb2-module-reactbundle, Ubuntu:26.04:LTS: icinga-php-thirdparty, Ubuntu:26.04:LTS: icingaweb2-module-reactbundle&lt;/p&gt;
&lt;p&gt;ReactPHP HTTP is a streaming HTTP client and server implementation for ReactPHP. In ReactPHP&amp;#39;s HTTP server component versions starting with 0.7.0 and prior to 1.7.0, when ReactPHP is processing incoming HTTP cookie values, the cookie names are url-decoded. This may lead to cookies with prefixes like `__Host-` and `__Secure-` confused with cookies that decode to such prefix, thus leading to an attacker being able to forge cookie which is supposed to be secure. This issue is fixed in ReactPHP HTTP version 1.7.0. As a workaround, Infrastructure or DevOps can place a reverse proxy in front of the ReactPHP HTTP server to filter out any unexpected `Cookie` request headers.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2022-36032</guid>
    </item>
  </channel>
</rss>
