Official FrankenPHP Docker images before version 1.1.11 could contain outdated, vulnerable system libraries. The flaw is tracked as CVE-2026-128027. It comes from how the images were built. They were rebuilt only when new base image tags were created. Security fixes that Alpine, PHP and Go applied under existing tags therefore never reached the FrankenPHP images.
According to the NVD description, remote attackers could exploit known flaws in these stale libraries to execute code. The description gives CVE-2025-15467 in libcrypto3 as an example. NVD rates the issue 9.8 out of 10 (Critical). As of the record date, it is not listed in CISA’s Known Exploited Vulnerabilities catalog.
What’s affected
The records list the php/frankenphp project as affected in all versions before 1.1.11. Version 1.1.11 is marked unaffected. The problem lies in the Docker images, not in FrankenPHP’s own code. Any container built on an affected FrankenPHP image may carry the outdated libraries. This includes custom images that use FrankenPHP as a base.
The records do not list every library or upstream CVE that may be present in affected images. Which flaws an image actually contains depends on when it was built.
How serious is it
NVD assigns a CVSS 3.1 base score of 9.8 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. In plain terms:
- Network attack vector, low complexity: an attacker can reach the vulnerable component remotely, with no special conditions required.
- No privileges or user interaction: the attacker needs no account, and no user has to take any action.
- High impact on confidentiality, integrity and availability: successful exploitation could lead to data exposure, tampering, or disruption, up to code execution as the description states.
Real-world risk depends on which stale libraries a given image contains and whether those components are reachable by an attacker. NVD lists this record’s status as “Deferred”, and no CWE classification has been assigned.
Is it being exploited?
As of the record date (2026-11-17), CVE-2026-128027 is not in CISA’s Known Exploited Vulnerabilities (KEV) catalog. The supplied records contain no reports of active exploitation.
Some of the underlying library flaws carried in stale images may have their own exploitation history. The records do not address this.
What to do
- Move to FrankenPHP images at version 1.1.11 or later. The records list 1.1.11 as unaffected. Pull fresh images rather than relying on locally cached copies.
- Rebuild derived images. If your application images use a FrankenPHP image as a base, rebuild and redeploy them so they pick up the updated base layers.
- Scan your container images. Run an image vulnerability scanner against running and stored FrankenPHP-based images. Look in particular for outdated Alpine packages such as
libcrypto3. - Re-pull on a schedule. Security fixes can arrive under an existing tag. Periodically pulling and rebuilding, or pinning to image digests that you update deliberately, helps keep containers current.
- Limit exposure. Until images are updated, restrict network access to affected services where possible.
- Check the vendor advisory (linked below) for any further guidance from the FrankenPHP maintainers.

