Sensitive information disclosure via verbose error responses
Published May 13, 2026 · Updated May 13, 2026
Information disclosure in Flight's default error handler before 3.18.1 allows remote attackers to obtain internal details through HTTP 500 responses. Engine::_error() inserts the uncaught exception message, code, and complete stack trace into the response body without a debug-mode gate. Any reachable route that raises an uncaught exception exposes absolute paths and module structure, plus secrets embedded in exception text.
Summary
What happened
Information disclosure in Flight's default error handler before 3.18.1 allows remote attackers to obtain internal details through HTTP 500 responses. Engine::_error() inserts the uncaught exception message, code, and complete stack trace into the response body without a debug-mode gate. Any reachable route that raises an uncaught exception exposes absolute paths and module structure, plus secrets embedded in exception text.
The record
- CVE
- CVE-2026-42552
- Published
- May 13, 2026
- Updated
- May 13, 2026
- Vendor
- FlightPHP
- Product
- Flight
- Classifications
- CWE-209, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 13, 2026CVE publishedPublication date reported by the CVE source.
- May 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.18.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-qrch-52m5-vv85 error-response proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo