Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-82416 high CVSS 7.7

Vulnerability in github.com/dunglas/frankenphp (CVE-2026-82416)

Summary

Vulnerability in github.com/dunglas/frankenphp (CVE-2026-82416). Confidential information can be exposed externally. Exploitable via session. Mitigation: upgrade to 1.12.5 or later.

Original description

The description as published by the source.

Summary

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 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.

The C session-reset code is unchanged across 1.11.x-1.12.x, so this is…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-82416 has been found in github.com/dunglas/frankenphp.
Attackers can target a specific entry point like session over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade github.com/dunglas/frankenphp to 1.12.5 or later.
If unsure, ask your IT team or search "github.com/dunglas/frankenphp CVE-2026-82416" on the vendor's site.

CVE-2026-82416 (github.com/dunglas/frankenphp) — CWE-362 / CVSS v3 7.7
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: session / conf.d / FRANKENPHP_TEST / HAVE_PHP_SESSION
Patched: 1.12.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-362) exists in github.com/dunglas/frankenphp. Attackers reach the vulnerable code path via session without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/dunglas/frankenphp. Attack surface: session / conf.d / FRANKENPHP_TEST / HAVE_PHP_SESSION.

🔥 Severity

Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.12.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/dunglas/frankenphp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/dunglas/frankenphp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/dunglas/frankenphp を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/dunglas/frankenphp to 1.12.5

    ステージング環境で 1.12.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/dunglas/frankenphp
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.12.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details