Skip to content

PHP2Shell fix out? #139

Open
Open

Description

@dpacmittal

I'm wondering if PHP2Shell vuln is fixed in fpm images

Activity

  1. fquffio commented on Oct 21, 2026

    @fquffio
    Collaborator

    Hi, we're trying to rebuild but PECL returns 500 intermittently. Hopefully we can publish fixed images soon. This will only apply to 8.2 and above, however...

  2. dpacmittal commented on Oct 21, 2026

    @dpacmittal
    Author

    Thank you for the update. I'm aware that it only applies to 8.2+.

  3. fquffio commented on Oct 22, 2026

    @fquffio
    Collaborator

    Images tagged 8.2-8.5 are up to date with the latest official patches.
    Build for :latest and :alpine have failed — I relaunched them, but it will take another while before they're ready. Apologize for the delays… 😞

  4. frankstrater commented on Oct 22, 2026

    @frankstrater

    Any chance the php7.4-apache image will be rebuild? Would be very gratefull on behalf of muziekweb.nl (currently offline), the Dutch public music library...

    Edit: I see it's just been published. Thank you.

  5. fquffio commented on Oct 22, 2026

    @fquffio
    Collaborator

    @frankstrater Careful! The 7.4 rebuilt image does not include the security patch! It was not released on the base image we build upon. @le0m is still working to bring the patched version on images ≤ 8.2

  6. frankstrater commented on Oct 22, 2026

    @frankstrater

    Ah ok, thanks for the heads up. I'll patiently wait, but will test this specifc version anyway.

  7. frankstrater commented on Oct 22, 2026

    @frankstrater

    @le0m Is there any way to speed up this work at Chialab? Does Chialab accept monetary donations from other European cultural institutes? Or personal donations?

  8. fquffio commented on Oct 22, 2026

    @fquffio
    Collaborator

    @frankstrater Thank you, but it's not needed… unless "personal donations" include weekends in the Netherlands with a free guided tour of the Dutch public music library. 😂

    We're working on this as a priority anyway.

    Just to keep you posted: we have investigated what options we have right now for PHP versions that are EoL.

    We could use a newer Debian base image and install PHP from ondrej repositories, but that could cause issues with unexpected OS updates that might break things in more or less subtle ways, and paths where PHP config files should be placed would change. We could work around this with a bunch of symlinks… but it feels an unstable solution to us, and end users might see their build start failing, or worse.

    We have thus decided to build from source using the same base image, and apply backported patches from the Debian backports: https://salsa.debian.org/php-team/php
    This allows us to keep the same base Debian image, which should cause less issues with backward compatibility, and hopefully this will be less painful for those who build upon these images — ourselves in primis.
    This might take a bit longer, but should be a more stable solution.

    @le0m is working on this in #140

  9. frankstrater commented on Oct 23, 2026

    @frankstrater

    @fquffio @le0m Grazie mille!

    I'll stay in touch through email @chialab and see what we can do to express our gratitude at the Netherlands Institute for Sound and Vision (NISV) / Muziekweb.nl / Fonos. (the new location is under construction, see: https://www.beeldengeluid.nl/fonos )

  10. le0m commented on Oct 23, 2026

    @le0m
    Member

    @frankstrater Sorry for the long delay 🙏🏼

    As fquffio explained, we decided to start building EOL PHP versions from source, so that we could apply the Debian backported patches. We tested the new images and didn't find any regressions, but please run your own tests before deploying in production 😉

    We decided to initially apply only the patches specific for CVE-2026-109618 and CVE-2026-109619 to speed up the release, but we'll now start adding the other security patches as well.

  11. adlanarifzr commented on Oct 23, 2026

    @adlanarifzr

    @le0m Thanks for the updates! Is that meant we can pull latest image now and it already patches the CVE-2026-109618 and CVE-2026-109619 ?

  12. fquffio commented on Oct 23, 2026

    @fquffio
    Collaborator

    @adlanarifzr The :latest, :alpine, and the 8.2-8.5 versions were already patched as of Thursday in the early morning (UTC).

    For the 5.6-8.1 images to be patched, we had to rebuild PHP from source using the Debian patches backports, and those have been published a few minutes ago, after #140 got merged!

    The -compat flavor is still being built, so that's the only variant that is still unsafe.

  13. le0m commented on Oct 23, 2026

    @le0m
    Member

    Beware that most vulnerability scanners rely on the reported PHP version (php -v) to detect if they are vulnerable or not. Our images do not change this, so they appear as still vulnerable. We specifically added a PHP_PATCHES env variable and a it.chialab.php.patches docker label to differentiate patched images from unpatched ones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions