CVE-2026-124622: olivier-ls PHP-FTS Storage.php open toctou
A vulnerability was identified in olivier-ls PHP-FTS up to 1.1.3. This impacts the function TrigramIndex::open of the file Storage.php. Such manipulation leads to time-of-check time-of-use. The attack needs to be performed locally. Upgrading to version 1.1.4 will fix this issue. The name of the patch is 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3. Upgrading the affected component is recommended. The project maintainer explains: "[T]he attack requires write access to the index directory by a user other than the one running the application. That is a real shared-hosting scenario and worth defending against, which is why it is fixed but it is a hardening measure rather than a remotely reachable vulnerability, and the "Code Execution" impact additionally assumes the symlink target is a web-served .php file."
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
olivier-ls PHP-FTSto a version that resolves this vulnerability.Fixed in 1.1.4Patch 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3
Event History
Frequently Asked Questions
Who is realistically exposed to this issue?
Deployments are exposed when a user other than the application runtime user can write to the PHP-FTS index directory. The maintainer identifies shared-hosting environments as a realistic scenario.
What access does an attacker need?
The attack must be performed locally and requires write access to the index directory by a different user than the one running the application. It is not described as remotely reachable.
Are code-execution scenarios automatic?
No. The stated code-execution impact additionally depends on the symlink target being a web-served .php file.
What should be done if the affected version is in use?
Upgrade PHP-FTS to version 1.1.4. The fix is identified by patch 0b2fae333d6b022da7ed4c43e2d41aa03f91dff3; until upgrading, restrict index-directory write access so untrusted or separate local users cannot modify it.