Read the docs
TI-2026-66202 Aliases GHSA-x9p2-77v6-6vhf

FrankenPHP has delayed propagation of security fixes in upstream base images

Priority LOW 38CWE-1395Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
Fixed

No CVSS vector from any source. Fix status from GitHub.

Summary

# Delayed propagation of security fixes in upstream base images ## Summary **Vulnerability in base Docker images (PHP, Go, and Alpine) not automatically propagating to FrankenPHP images.** FrankenPHP's container images were previously built only when specific version tags were updated or when manual triggers were initiated. This meant that if an upstream base image (such as Alpine Linux or official PHP/Go images) received a security patch under an existing tag, the FrankenPHP image would remain on the older, vulnerable version of those base layers. ## Impact Users pulling FrankenPHP images may have been running environments with known vulnerabilities in underlying system libraries (e.g., `libcrypto3`) even if they were using the "latest" version of a specific FrankenPHP tag. Specifically, this includes vulnerabilities recently patched in **Alpine 3.20.9, 3.21.6, 3.22.3, and 3.23.3**, such as **CVE-2025-15467** (Remote Code Execution in `libcrypto3`). ## Details The issue was a lack of automated "staleness" detection in the CI/CD pipeline. Unless explicitly told, our build server was building new Docker images only when a new tag for base images was created. However, base images such as Alpine, PHP, and Go usually overwrite existing Docker tags to apply security fixes, which wasn't triggering a new build on our side. ## Patches As of **February 4, 2026**, the CI/CD pipeline has been updated. * **Automated Detection:** A daily check is now performed to compare the digest of local base images against upstream registries. * **Auto-Rebuild:** If a change is detected in base images (even if the tag name remains the same), FrankenPHP images are automatically rebuilt and re-pushed. **Users are advised to pull the latest versions of their specific tags to receive these updates.** ## Workarounds You can force a local rebuild of your environment using the `--pull` flag to ensure you are fetching the latest patched base layers: ```bash docker pull dunglas/frankenphp:latest # If building your own image based on FrankenPHP docker build --pull -t my-app . ``` ## References * [Alpine Linux Security Advisories](https://www.alpinelinux.org/posts/Alpine-3.20.9-3.21.6-3.22.3-3.23.3-released.html) * **CVE-2025-15467** (RCE in libcrypto3) ## Credits Thanks to [Tim Nelles](https://timnelles.de/) for reporting and fixing this issue.

Why it matters now

Fix Fixed github.com/dunglas/frankenphp (Go): 1.1.11

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—github.com/dunglas/frankenphp (Go)before 1.1.111.1.11Patch availableGHSA-x9p2-77v6-6vhf
  • github.com/dunglas/frankenphp (Go) Vendor— Affected before 1.1.11 Fixed in 1.1.11 Patch available GHSA-x9p2-77v6-6vhf

Remediation

  • Fix · GHSA-x9p2-77v6-6vhf github.com/dunglas/frankenphp (Go) Fixed in 1.1.11 Advisory →

Timeline

  1. 2026-10-03 Threatist record created from GHSA-x9p2-77v6-6vhf

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences