← Back
CVE-2026-42552
high
CVSS 7.5
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.
AI summary snake-internal / snake-material-v2
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.
❓ What is the problem
**A vulnerability** (CWE-209) exists in flightphp/core. Attackers reach the vulnerable code path via ``flight.debug`` without authentication.
📍 Affected scope
flightphp/core — . Attack surface: `flight.debug` / `b8dd23a` / `false`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **3.18.1**.
🛡️ 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 'flightphp/core' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade flightphp/core to 3.18.1ステージング環境で 3.18.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
flightphp/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.18.1"}]}]
Packagist
flightphp/core
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.18.1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-42552
- package https://github.com/flightphp/core
- web 134c704f-9b21-4f2e-91b3-4a467353bcc0
- web https://github.com/flightphp/core/commit/b8dd23aaa828cb289fa3c84e75b2a3717cab50b0
- web https://github.com/flightphp/core/releases/tag/v3.18.1
- web https://github.com/advisories/GHSA-qrch-52m5-vv85