CWE-488
AllowedExposure of Data Element to Wrong Session
Abstraction: Base · Status: Draft
The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.
109 vulnerabilities reference this CWE, most recent first.
GHSA-P8F6-44XP-3CP8
Vulnerability from github – Published: 2026-09-07 18:31 – Updated: 2026-09-07 18:31In JetBrains YouTrack before 2026.2.18634 a shared token cache allowed cross-tenant theft of GitHub App installation tokens
{
"affected": [],
"aliases": [
"CVE-2026-86492"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-07T17:17:27Z",
"severity": "HIGH"
},
"details": "In JetBrains YouTrack before 2026.2.18634 a shared token cache allowed cross-tenant theft of GitHub App installation tokens",
"id": "GHSA-p8f6-44xp-3cp8",
"modified": "2026-09-07T18:31:32Z",
"published": "2026-09-07T18:31:32Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86492"
},
{
"type": "WEB",
"url": "https://www.jetbrains.com/privacy-security/issues-fixed"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-PHG3-GV66-Q38X
Vulnerability from github – Published: 2025-02-13 15:31 – Updated: 2025-03-03 15:31A flaw was found in Quarkus REST that allows request parameters to leak between concurrent requests if endpoints use field injection without a CDI scope. This vulnerability allows attackers to manipulate request data, impersonate users, or access sensitive information.
{
"affected": [
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-rest"
},
"ranges": [
{
"events": [
{
"introduced": "3.16.0.CR1"
},
{
"fixed": "3.18.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-rest-deployment"
},
"ranges": [
{
"events": [
{
"introduced": "3.16.0.CR1"
},
{
"fixed": "3.18.2"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-rest"
},
"ranges": [
{
"events": [
{
"introduced": "3.9.0.CR1"
},
{
"fixed": "3.15.3.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-rest-deployment"
},
"ranges": [
{
"events": [
{
"introduced": "3.9.0.CR1"
},
{
"fixed": "3.15.3.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-rest"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.8.6.1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "Maven",
"name": "io.quarkus:quarkus-rest-deployment"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.8.6.1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2025-1247"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": true,
"github_reviewed_at": "2025-02-13T17:36:18Z",
"nvd_published_at": "2025-02-13T14:16:18Z",
"severity": "HIGH"
},
"details": "A flaw was found in Quarkus REST that allows request parameters to leak between concurrent requests if endpoints use field injection without a CDI scope. This vulnerability allows attackers to manipulate request data, impersonate users, or access sensitive information.",
"id": "GHSA-phg3-gv66-q38x",
"modified": "2025-03-03T15:31:24Z",
"published": "2025-02-13T15:31:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-1247"
},
{
"type": "WEB",
"url": "https://github.com/quarkusio/quarkus/issues/45789"
},
{
"type": "WEB",
"url": "https://github.com/quarkusio/quarkus/commit/02ff9ed45c3928edf2a0f8b906543606fed7cd53"
},
{
"type": "WEB",
"url": "https://github.com/quarkusio/quarkus/commit/d8df15cec17dc5d085efc372d77cbef1341ae071"
},
{
"type": "WEB",
"url": "https://github.com/quarkusio/quarkus/commit/f42166ee7041ed09b7183d5dbf3ece2439b16676"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:1884"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:1885"
},
{
"type": "WEB",
"url": "https://access.redhat.com/errata/RHSA-2025:2067"
},
{
"type": "WEB",
"url": "https://access.redhat.com/security/cve/CVE-2025-1247"
},
{
"type": "WEB",
"url": "https://bugzilla.redhat.com/show_bug.cgi?id=2345172"
},
{
"type": "PACKAGE",
"url": "https://github.com/quarkusio/quarkus"
},
{
"type": "WEB",
"url": "https://quarkus.io/blog/cve-fixes-feb-2025"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "Quarkus REST Endpoint Request Parameter Leakage Due to Shared Instance"
}
GHSA-PQMH-9H5R-56PF
Vulnerability from github – Published: 2026-07-04 09:31 – Updated: 2026-07-04 09:31A vulnerability has been found in FederatedAI FATE up to 2.2.0. This affects the function QueuePushReqStreamObserver.initEggroll of the file java/osx/osx-broker/src/main/java/org/fedai/osx/broker/grpc/QueuePushReqStreamObserver.java of the component OSX Broker. Such manipulation of the argument rollSiteSessionId/dstRole/dstPartyId leads to exposure of data element to wrong session. The attack can be executed remotely. A high complexity level is associated with this attack. It is indicated that the exploitability is difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
{
"affected": [],
"aliases": [
"CVE-2026-14621"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-07-04T09:16:27Z",
"severity": "LOW"
},
"details": "A vulnerability has been found in FederatedAI FATE up to 2.2.0. This affects the function QueuePushReqStreamObserver.initEggroll of the file java/osx/osx-broker/src/main/java/org/fedai/osx/broker/grpc/QueuePushReqStreamObserver.java of the component OSX Broker. Such manipulation of the argument rollSiteSessionId/dstRole/dstPartyId leads to exposure of data element to wrong session. The attack can be executed remotely. A high complexity level is associated with this attack. It is indicated that the exploitability is difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.",
"id": "GHSA-pqmh-9h5r-56pf",
"modified": "2026-07-04T09:31:45Z",
"published": "2026-07-04T09:31:45Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-14621"
},
{
"type": "WEB",
"url": "https://github.com/FederatedAI/FATE/issues/5791"
},
{
"type": "WEB",
"url": "https://github.com/FederatedAI/FATE/pull/5792"
},
{
"type": "WEB",
"url": "https://github.com/FederatedAI/FATE"
},
{
"type": "WEB",
"url": "https://vuldb.com/cve/CVE-2026-14621"
},
{
"type": "WEB",
"url": "https://vuldb.com/submit/844900"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/376137"
},
{
"type": "WEB",
"url": "https://vuldb.com/vuln/376137/cti"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
GHSA-QMVM-MG94-C39P
Vulnerability from github – Published: 2024-02-26 18:30 – Updated: 2024-08-14 18:32In the Bentley ALIM Web application, certain configuration settings can cause exposure of a user's ALIM session token when the user attempts to download files. This is fixed in Assetwise ALIM Web 23.00.02.03 and Assetwise Information Integrity Server 23.00.04.04.
{
"affected": [],
"aliases": [
"CVE-2024-27455"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2024-02-26T16:28:00Z",
"severity": "CRITICAL"
},
"details": "In the Bentley ALIM Web application, certain configuration settings can cause exposure of a user\u0027s ALIM session token when the user attempts to download files. This is fixed in Assetwise ALIM Web 23.00.02.03 and Assetwise Information Integrity Server 23.00.04.04.",
"id": "GHSA-qmvm-mg94-c39p",
"modified": "2024-08-14T18:32:36Z",
"published": "2024-02-26T18:30:31Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2024-27455"
},
{
"type": "WEB",
"url": "https://www.bentley.com/advisories/be-2024-0001"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-QQQ9-5J87-RW35
Vulnerability from github – Published: 2026-11-04 00:32 – Updated: 2026-11-09 21:31CGI::Carp versions before 5.00 for Perl leak warnings across requests in persistent environments via the warningsToBrowser buffer.
Warnings are held in a package-level buffer until warningsToBrowser writes them into the page as HTML comments, and the buffer is never cleared between requests. Under mod_perl, FastCGI or PSGI, warnings from one request are written into a later one.
Warnings that contain one user's request data can appear in the HTML sent to another user.
{
"affected": [],
"aliases": [
"CVE-2026-120634"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-04T00:17:24Z",
"severity": "MODERATE"
},
"details": "CGI::Carp versions before 5.00 for Perl leak warnings across requests in persistent environments via the warningsToBrowser buffer.\n\nWarnings are held in a package-level buffer until warningsToBrowser writes them into the page as HTML comments, and the buffer is never cleared between requests. Under mod_perl, FastCGI or PSGI, warnings from one request are written into a later one.\n\nWarnings that contain one user\u0027s request data can appear in the HTML sent to another user.",
"id": "GHSA-qqq9-5j87-rw35",
"modified": "2026-11-09T21:31:40Z",
"published": "2026-11-04T00:32:21Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-120634"
},
{
"type": "WEB",
"url": "https://github.com/leejo/CGI.pm/commit/604a83fec105f75fe06f1a75026c4c34fd5a1f61.patch"
},
{
"type": "WEB",
"url": "https://metacpan.org/release/LEEJO/CGI-4.72/source/lib/CGI/Carp.pm"
},
{
"type": "WEB",
"url": "https://metacpan.org/release/LEEJO/CGI-5.00/changes"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-R8J3-CWJ5-4J73
Vulnerability from github – Published: 2026-09-06 18:34 – Updated: 2026-09-08 21:33A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup
for a given hostname even when using a different Native CA Store setting
(CURLSSLOPT_NATIVE_CA) than when the connection was created.
{
"affected": [],
"aliases": [
"CVE-2026-80231"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-06T18:17:22Z",
"severity": "HIGH"
},
"details": "A flaw in libcurl makes it wrongly reuse an existing HTTPS connection setup\nfor a given hostname even when using a different Native CA Store setting\n(`CURLSSLOPT_NATIVE_CA`) than when the connection was created.",
"id": "GHSA-r8j3-cwj5-4j73",
"modified": "2026-09-08T21:33:03Z",
"published": "2026-09-06T18:34:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80231"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3969368"
},
{
"type": "WEB",
"url": "https://curl.se/docs/CVE-2026-80231.html"
},
{
"type": "WEB",
"url": "https://curl.se/docs/CVE-2026-80231.json"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-RH6W-4P8R-7GHM
Vulnerability from github – Published: 2026-11-10 18:31 – Updated: 2026-11-16 15:30When MicroProfile JWT authentication is used for servlets that declare a run-as identity, the security state established for a request is not always cleared from the processing thread when the request does not complete normally. A remote attacker holding a valid token can cause later, unrelated requests served by the same thread to invoke enterprise beans with the elevated run-as identity. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.
{
"affected": [],
"aliases": [
"CVE-2026-111242"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-11-10T16:17:14Z",
"severity": "HIGH"
},
"details": "When MicroProfile JWT authentication is used for servlets that declare a run-as identity, the security state established for a request is not always cleared from the processing thread when the request does not complete normally. A remote attacker holding a valid token can cause later, unrelated requests served by the same thread to invoke enterprise beans with the elevated run-as identity. Users are recommended to upgrade to version 10.3.0 or 11.0.0-M2, which fix the issue.",
"id": "GHSA-rh6w-4p8r-7ghm",
"modified": "2026-11-16T15:30:29Z",
"published": "2026-11-10T18:31:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-111242"
},
{
"type": "WEB",
"url": "https://lists.apache.org/thread/opr1oob7p8xtqwcj1yv2dnsj4zqo9f03"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
]
}
GHSA-RHW6-3RRG-MWJQ
Vulnerability from github – Published: 2026-09-06 18:34 – Updated: 2026-09-08 18:31A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.
{
"affected": [],
"aliases": [
"CVE-2026-19931"
],
"database_specific": {
"cwe_ids": [
"CWE-488"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-06T18:17:20Z",
"severity": "CRITICAL"
},
"details": "A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given\nhostname using Negotiate authentication, when the initial request is done\nusing empty credentials. This can make user B\u0027s request get sent over user A\u0027s\npreviously authenticated connection.",
"id": "GHSA-rhw6-3rrg-mwjq",
"modified": "2026-09-08T18:31:45Z",
"published": "2026-09-06T18:34:39Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-19931"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3923520"
},
{
"type": "WEB",
"url": "https://curl.se/docs/CVE-2026-19931.html"
},
{
"type": "WEB",
"url": "https://curl.se/docs/CVE-2026-19931.json"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
GHSA-RP9Q-8Q5W-CH44
Vulnerability from github – Published: 2026-05-13 18:30 – Updated: 2026-05-13 18:30libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers.
libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.
When reusing a connection a range of criteria must be met. Due to a logical error in the code, a network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different 'share' than the new subsequent transfer should.
This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.
{
"affected": [],
"aliases": [
"CVE-2026-5773"
],
"database_specific": {
"cwe_ids": [
"CWE-488",
"CWE-918"
],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-05-13T13:01:56Z",
"severity": "HIGH"
},
"details": "libcurl might in some circumstances reuse the wrong connection for SMB(S)\ntransfers.\n\nlibcurl features a pool of recent connections so that subsequent requests can\nreuse an existing connection to avoid overhead.\n\nWhen reusing a connection a range of criteria must be met. Due to a logical\nerror in the code, a network transfer operation that was requested by an\napplication could wrongfully reuse an existing SMB connection to the same\nserver that was using a different \u0027share\u0027 than the new subsequent transfer\nshould.\n\nThis could in unlucky situations lead to the download of the wrong file or the\nupload of a file to the wrong place. When this happens, the same credentials\nare used and the server name is the same.",
"id": "GHSA-rp9q-8q5w-ch44",
"modified": "2026-05-13T18:30:52Z",
"published": "2026-05-13T18:30:52Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-5773"
},
{
"type": "WEB",
"url": "https://hackerone.com/reports/3650689"
},
{
"type": "WEB",
"url": "https://curl.se/docs/CVE-2026-5773.html"
},
{
"type": "WEB",
"url": "https://curl.se/docs/CVE-2026-5773.json"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2026/04/29/9"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
"type": "CVSS_V3"
}
]
}
GHSA-V3PH-CGQH-R8P5
Vulnerability from github – Published: 2026-10-15 20:14 – Updated: 2026-10-15 20:14Summary
In worker mode under concurrency, FrankenPHP can hand a PHP session id from one request to another when PHP'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's id) or to a stale id from a previous request served by the same worker thread.
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's session is ignored and they receive a foreign or empty session.
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:
- Affected: any build where the
sessionextension is not visible to FrankenPHP at compile time, i.e. loaded as a shared / out-of-tree module (extension=sessionin an ini). This includes the RPM and Debian packages and other packagedphp-ztsdistributions that shipsessionas a shared extension underconf.d. - Not affected: builds where
sessionis 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.
The C session-reset code is unchanged across 1.11.x-1.12.x, so this is not a code regression between releases. A "1.12.2 works / 1.12.3 leaks" observation on the same host reflects two differently-built packages, not a source change. The persistent-zval helpers (#2366) are compiled only under FRANKENPHP_TEST and are unrelated.
Root cause
FrankenPHP resets per-request session state in frankenphp_reset_session_state(), which releases PS(id) so the next session_start() re-reads the request cookie. That whole function is guarded by #ifdef HAVE_PHP_SESSION, a macro defined only when the session extension headers are present at FrankenPHP compile time (session statically enabled in the PHP build). When session is a shared module, HAVE_PHP_SESSION is undefined, the reset is compiled out, and PS(id) survives the request boundary.
PHP's session_start() reads the request cookie only when PS(id) is NULL (ext/session/session.c, try_find_session_id_in_cookies(): if (!PS(use_cookies) || PS(id)) return;). With a stale PS(id), the cookie is ignored and the worker reuses the previous request's id, exposing it to whichever client is served next.
Reproduction
Minimal worker script (index.php):
<?php
$handler = static function () {
session_start();
$sent = $_COOKIE['session'] ?? '(none)';
$id = session_id();
header('Content-Type: text/plain');
echo ($sent === '(none)' || $sent === $id) ? "OK sent=$sent id=$id\n"
: "LEAK sent=$sent id=$id\n";
session_write_close();
};
while (\frankenphp_handle_request($handler)) {}
Run under worker mode with num 2 (≥2 workers), session.use_strict_mode=1, on a PHP build where session is a shared module. Pre-create two valid sessions A and B, then fire concurrent requests alternating the two cookies:
seq 600 | xargs -P32 -I{} sh -c '
c=$([ $(( {} % 2 )) -eq 0 ] && echo A || echo B);
curl -s -H "Cookie: session=$c" http://127.0.0.1:8080/' | grep -c LEAK
On an affected build a large fraction of responses are LEAK (session_id() differs from the cookie sent, and A and B sometimes resolve to the same id). On a statically-linked build the count is always 0.
Fix
When HAVE_PHP_SESSION is undefined, FrankenPHP now resets the session module through the module registry on every worker request (its RSHUTDOWN releases PS(id), RINIT re-initialises the globals), so the per-request cleanup always runs regardless of how the extension is linked. Statically-linked builds are unchanged and keep using frankenphp_reset_session_state().
Verified on PHP 8.6-dev ZTS, 2 workers, session.use_strict_mode=1, 600 alternating-cookie concurrent requests: before the fix 519/600 leaked; after the fix 0/600. Statically-linked builds stayed at 0/600.
Workarounds
- Use a FrankenPHP build with
sessionstatically compiled (official static binaries or Docker images). - Or, in the worker loop, after
session_write_close()callsession_id('')so the nextsession_start()re-reads the request cookie (withsession.use_strict_mode=1).
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 1.12.4"
},
"package": {
"ecosystem": "Go",
"name": "github.com/dunglas/frankenphp"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.12.5"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-82416"
],
"database_specific": {
"cwe_ids": [
"CWE-362",
"CWE-488"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-15T20:14:29Z",
"nvd_published_at": "2026-10-13T17:17:47Z",
"severity": "HIGH"
},
"details": "## Summary\nIn worker mode under concurrency, FrankenPHP can hand a PHP session id from one request to another when PHP\u0027s `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\u0027s id) or to a stale id from a previous request served by the same worker thread.\n\n## Impact\n- **Security:** cross-user session exposure / session hijacking in worker mode. Same impact class as CVE-2026-24894.\n- **Functional:** users are intermittently logged out; their cookie\u0027s session is ignored and they receive a foreign or empty session.\n\n## Affected / not affected\nExposure is determined by how the `session` extension is linked in the PHP build FrankenPHP is compiled against, **not** by the FrankenPHP release:\n\n- **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`.\n- **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.\n\nThe C session-reset code is unchanged across 1.11.x-1.12.x, so this is not a code regression between releases. A \"1.12.2 works / 1.12.3 leaks\" observation on the same host reflects two differently-built packages, not a source change. The persistent-zval helpers (#2366) are compiled only under `FRANKENPHP_TEST` and are unrelated.\n\n## Root cause\nFrankenPHP resets per-request session state in `frankenphp_reset_session_state()`, which releases `PS(id)` so the next `session_start()` re-reads the request cookie. That whole function is guarded by `#ifdef HAVE_PHP_SESSION`, a macro defined only when the session extension headers are present at FrankenPHP compile time (session statically enabled in the PHP build). When `session` is a shared module, `HAVE_PHP_SESSION` is undefined, the reset is compiled out, and `PS(id)` survives the request boundary.\n\nPHP\u0027s `session_start()` reads the request cookie only when `PS(id)` is `NULL` (`ext/session/session.c`, `try_find_session_id_in_cookies()`: `if (!PS(use_cookies) || PS(id)) return;`). With a stale `PS(id)`, the cookie is ignored and the worker reuses the previous request\u0027s id, exposing it to whichever client is served next.\n\n## Reproduction\nMinimal worker script (`index.php`):\n```php\n\u003c?php\n$handler = static function () {\n session_start();\n $sent = $_COOKIE[\u0027session\u0027] ?? \u0027(none)\u0027;\n $id = session_id();\n header(\u0027Content-Type: text/plain\u0027);\n echo ($sent === \u0027(none)\u0027 || $sent === $id) ? \"OK sent=$sent id=$id\\n\"\n : \"LEAK sent=$sent id=$id\\n\";\n session_write_close();\n};\nwhile (\\frankenphp_handle_request($handler)) {}\n```\nRun under worker mode with `num 2` (\u22652 workers), `session.use_strict_mode=1`, on a PHP build where `session` is a shared module. Pre-create two valid sessions `A` and `B`, then fire concurrent requests alternating the two cookies:\n```sh\nseq 600 | xargs -P32 -I{} sh -c \u0027\n c=$([ $(( {} % 2 )) -eq 0 ] \u0026\u0026 echo A || echo B);\n curl -s -H \"Cookie: session=$c\" http://127.0.0.1:8080/\u0027 | grep -c LEAK\n```\nOn an affected build a large fraction of responses are `LEAK` (`session_id()` differs from the cookie sent, and `A` and `B` sometimes resolve to the same id). On a statically-linked build the count is always `0`.\n\n## Fix\nWhen `HAVE_PHP_SESSION` is undefined, FrankenPHP now resets the `session` module through the module registry on every worker request (its `RSHUTDOWN` releases `PS(id)`, `RINIT` re-initialises the globals), so the per-request cleanup always runs regardless of how the extension is linked. Statically-linked builds are unchanged and keep using `frankenphp_reset_session_state()`.\n\nVerified on PHP 8.6-dev ZTS, 2 workers, `session.use_strict_mode=1`, 600 alternating-cookie concurrent requests: before the fix 519/600 leaked; after the fix 0/600. Statically-linked builds stayed at 0/600.\n\n## Workarounds\n- Use a FrankenPHP build with `session` statically compiled (official static binaries or Docker images).\n- Or, in the worker loop, after `session_write_close()` call `session_id(\u0027\u0027)` so the next `session_start()` re-reads the request cookie (with `session.use_strict_mode=1`).",
"id": "GHSA-v3ph-cgqh-r8p5",
"modified": "2026-10-15T20:14:29Z",
"published": "2026-10-15T20:14:29Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/security/advisories/GHSA-v3ph-cgqh-r8p5"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-82416"
},
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/pull/2523"
},
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/commit/be24d82531675f90862b8cde1e9fc7e9ee855aa5"
},
{
"type": "PACKAGE",
"url": "https://github.com/php/frankenphp"
},
{
"type": "WEB",
"url": "https://github.com/php/frankenphp/releases/tag/caddy/v1.12.5"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L",
"type": "CVSS_V3"
}
],
"summary": "FrankenPHP: Cross-request PHP session ID leak in worker mode when the session extension is a shared module"
}
Mitigation
Protect the application's sessions from information leakage. Make sure that a session's data is not used or visible by other sessions.
Mitigation
Use a static analysis tool to scan the code for information leakage vulnerabilities (e.g. Singleton Member Field).
Mitigation
In a multithreading environment, storing user data in Servlet member fields introduces a data access race condition. Do not use member fields to store information in the Servlet.
CAPEC-59: Session Credential Falsification through Prediction
This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
CAPEC-60: Reusing Session IDs (aka Session Replay)
This attack targets the reuse of valid session ID to spoof the target system in order to gain privileges. The attacker tries to reuse a stolen session ID used previously during a transaction to perform spoofing and session hijacking. Another name for this type of attack is Session Replay.