Bug 2558209 - TODAY: Upcoming Critical PHP Security Release
Summary: TODAY: Upcoming Critical PHP Security Release
Keywords:
Status: CLOSED DUPLICATE of bug 2556842
Alias: None
Product: Fedora
Classification: Fedora
Component: php
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Remi Collet
QA Contact: Fedora Extras Quality Assurance
URL: https://www.php.net/archive/2026.php#...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-21 11:16 UTC by customercare
Modified: 2026-10-22 07:06 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-22 07:06:35 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description customercare 2026-10-21 11:16:58 UTC
The PHP security team would like to give advance notice of an upcoming security release.

It is scheduled for Wednesday, 21 October 2026 at 14:00 UTC.

It addresses two critical vulnerabilities, both rated CVSS v4.0 9.2.

All PHP users are encouraged to prepare now so they can upgrade as soon as the release is available.

We reserve the right to release earlier should details of either vulnerability become public, or should evidence of active exploitation appear in the wild.

Full details, affected versions, and the fixed versions will be published with the release.

Thank you for helping us keep PHP secure.
08 Oct 2026

The maintainers published the advisory following the leaking of purported details, which have yet to be confirmed. The report showed a video of an exploit tool dubbed PHP2Shell executing code on webservers running WordPress 7.1.3, MediaWiki 1.46.2, phpBB 3.3.17, Magento 2.4.9, Joomla 6.2.0, Laravel 13.36.0, Laravel 8.83.29, Symphony 8.1.9, Drupal 11.4.10, and WHMCS 9.0.9, all of which use PHP. A video depicting the tool has been reposted here.

Attempts to locate the unconfirmed report were unsuccessful, but security firm watchTowr said it claimed to affect every PHP version from PHP 5, released in 2004, onward. The security firm went on to say it has confirmed that the vulnerabilities, tracked as CVE-2026-109618 and CVE-2026-109619, are real.

Reproducible: Always

Actual Results:
EXPLOIT

Comment 1 Avi Alkalay 2026-10-22 06:38:41 UTC
Are there any instructions to prevent from being exploited by attackers while we wait for an updated package?

Thank you in advance

Comment 2 Avi Alkalay 2026-10-22 07:06:35 UTC

*** This bug has been marked as a duplicate of bug 2556842 ***


Note You need to log in before you can comment on or make changes to this bug.