flightphp/core
Affected
- introduced
0, fixed3.18.1(ecosystem)
Fixed versions
3.18.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-42552
Flight vulnerable to sensitive information disclosure via default error handler
Summary
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).
Affected codeflight/Engine.php (≈ lines 678-704):
public function _error(Throwable $e): void
{
...
$msg = sprintf(<<<'HTML'
<h1>500 Internal Server Error</h1>
<h3>%s (%s)</h3>
<pre>%s</pre>
HTML,
$e->getMessage(),
$e->getCode(),
$e->getTraceAsString()
);
$this->response()->cache(0)->clearBody()->status(500)->write($msg)->send();
}
No flight.debug check, no environment gating.
Proof of concept
Any uncaught exception — including those auto-raised from handleError() — returns:
HTTP/1.1 500 Internal Server Error
<h1>500 Internal Server Error</h1>
<h3>secret path /var/www/config/db.yml; token=LEAKED123 (0)</h3>
<pre>#0 [internal function]: {closure}()
#1 /home/user/app/vendor/flightphp/core/flight/core/Dispatcher.php(361)...
#2 /home/user/app/vendor/flightphp/core/flight/Engine.php(...)
...
</pre>
Reproduced against the live PoC app at /poc5/error.
Impact
Patch (fixed in 3.18.1, commit b8dd23a)
A new flight.debug setting (default false) gates the verbose output. In production the handler now emits only <h1>500 Internal Server Error</h1>. Developers can set flight.debug = true in local environments to restore the full trace output.
Credit
Discovered by @Rootingg.
High Basis: The source's own band: HIGH
0, fixed 3.18.1 (ecosystem)3.18.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0