<?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, 20 Oct 2026 09:05:29 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-82416</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-82416</link>
      <description>&lt;p&gt;FrankenPHP is a modern application server for PHP. Prior to 1.12.5, FrankenPHP worker mode can retain PHP session state between requests when the session extension is loaded as a shared module and is unavailable through HAVE_PHP_SESSION at compile time. In this build configuration, frankenphp_reset_session_state() is compiled out, PS(id) can survive a request boundary, and a subsequent session_start() can ignore the new request&amp;#39;s cookie because an identifier is already present. Under concurrent requests, session_id() can therefore return another client&amp;#39;s identifier or a stale identifier from a previous request on the same worker thread, causing cross-user session exposure, possible session hijacking, and intermittent logout behavior. Builds with the session extension statically linked, including the official static binaries and Docker images, are not affected. This issue is fixed in version 1.12.5.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;FrankenPHP is a modern application server for PHP. Prior to 1.12.5, FrankenPHP worker mode can retain PHP session state between requests when the session extension is loaded as a shared module and is unavailable through HAVE_PHP_SESSION at compile time. In this build configuration, frankenphp_reset_session_state() is compiled out, PS(id) can survive a request boundary, and a subsequent session_start() can ignore the new request&amp;#39;s cookie because an identifier is already present. Under concurrent requests, session_id() can therefore return another client&amp;#39;s identifier or a stale identifier from a previous request on the same worker thread, causing cross-user session exposure, possible session hijacking, and intermittent logout behavior. Builds with the session extension statically linked, including the official static binaries and Docker images, are not affected. This issue is fixed in version 1.12.5.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-82416</guid>
    </item>
    <item>
      <title>GHSA-v3ph-cgqh-r8p5 — FrankenPHP: Cross-request PHP session ID leak in worker mode when the session extension is a shared module</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-v3ph-cgqh-r8p5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/dunglas/frankenphp&lt;/p&gt;
&lt;p&gt;## Summary
In worker mode under concurrency, FrankenPHP can hand a PHP session id from one request to another when PHP&amp;#39;s `session` extension is loaded as a shared module instead of being statically linked into the FrankenPHP binary. A request presenting `Cookie: session=A` can have `session_id()` resolve to `B` (a different concurrent client&amp;#39;s id) or to a stale id from a previous request served by the same worker thread.&lt;/p&gt;
&lt;p&gt;## Impact
- **Security:** cross-user session exposure / session hijacking in worker mode. Same impact class as CVE-2026-24894.
- **Functional:** users are intermittently logged out; their cookie&amp;#39;s session is ignored and they receive a foreign or empty session.&lt;/p&gt;
&lt;p&gt;## Affected / not affected
Exposure is determined by how the `session` extension is linked in the PHP build FrankenPHP is compiled against, **not** by the FrankenPHP release:&lt;/p&gt;
&lt;p&gt;- **Affected:** any build where the `session` extension is not visible to FrankenPHP at compile time, i.e. loaded as a shared / out-of-tree module (`extension=session` in an ini). This includes the RPM and Debian packages and other packaged `php-zts` distributions that ship `session` as a shared extension under `conf.d`.
- **Not affected:** builds where `session` is statically compiled into the PHP that FrankenPHP links against, such as the official static binaries and Docker images. There, the reset code below is compiled in and clears the id every request.&lt;/p&gt;
&lt;p&gt;The C session-reset code is unchanged across 1.11.x-1.12.x, so this i…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/dunglas/frankenphp&lt;/p&gt;
&lt;p&gt;## Summary
In worker mode under concurrency, FrankenPHP can hand a PHP session id from one request to another when PHP&amp;#39;s `session` extension is loaded as a shared module instead of being statically linked into the FrankenPHP binary. A request presenting `Cookie: session=A` can have `session_id()` resolve to `B` (a different concurrent client&amp;#39;s id) or to a stale id from a previous request served by the same worker thread.&lt;/p&gt;
&lt;p&gt;## Impact
- **Security:** cross-user session exposure / session hijacking in worker mode. Same impact class as CVE-2026-24894.
- **Functional:** users are intermittently logged out; their cookie&amp;#39;s session is ignored and they receive a foreign or empty session.&lt;/p&gt;
&lt;p&gt;## Affected / not affected
Exposure is determined by how the `session` extension is linked in the PHP build FrankenPHP is compiled against, **not** by the FrankenPHP release:&lt;/p&gt;
&lt;p&gt;- **Affected:** any build where the `session` extension is not visible to FrankenPHP at compile time, i.e. loaded as a shared / out-of-tree module (`extension=session` in an ini). This includes the RPM and Debian packages and other packaged `php-zts` distributions that ship `session` as a shared extension under `conf.d`.
- **Not affected:** builds where `session` is statically compiled into the PHP that FrankenPHP links against, such as the official static binaries and Docker images. There, the reset code below is compiled in and clears the id every request.&lt;/p&gt;
&lt;p&gt;The C session-reset code is unchanged across 1.11.x-1.12.x, so this i…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-v3ph-cgqh-r8p5</guid>
    </item>
  </channel>
</rss>
