Vulnerability in flightphp/core (CVE-2026-42552)
Summary
Vulnerability in flightphp/core (CVE-2026-42552). Confidential information can be exposed externally. Exploitable via flight.debug. Mitigation: upgrade to 3.18.1 or later.
Original description
The description as published by the source.
Flight is an extensible micro-framework for PHP. Prior to 3.18.1, the default error handler Engine::_error() writes the full exception message, exception code, and stack trace (including absolute filesystem paths) directly into the HTTP 500 response, with no debug gating. Production deployments leak internal paths, any secret interpolated into an exception message, and full module structure — giving attackers primitives for chaining other weaknesses (LFI, path traversal). This vulnerability is fixed in 3.18.1.
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-42552 has been found in flightphp/core.
Attackers can target a specific entry point like flight.debug over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade flightphp/core to 3.18.1 or later.
If unsure, ask your IT team or search "flightphp/core CVE-2026-42552" on the vendor's site.
CVE-2026-42552 (flightphp/core) — CWE-209 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: flight.debug / b8dd23a / false
Patched: 3.18.1 — 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.
A vulnerability (CWE-209) exists in flightphp/core. Attackers reach the vulnerable code path via flight.debug without authentication.
Check the vendor advisory for the affected versions of flightphp/core. Attack surface: flight.debug / b8dd23a / false.
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally.
Update to 3.18.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flightphp/core' . 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
-
1Identify exposure identify
grep -r 'flightphp/core' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flightphp/coreを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flightphp/core to 3.18.1ステージング環境で 3.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com