GHSA-X9P2-77V6-6VHF

Delayed propagation of security fixes in upstream base images

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.

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.

Workarounds

You can force a local rebuild of your environment using the --pull flag to ensure you are fetching the latest patched base layers:

docker pull dunglas/frankenphp:latest
# If building your own image based on FrankenPHP
docker build --pull -t my-app .

References

• Alpine Linux Security Advisories
• CVE-2025-15467 (RCE in libcrypto3)

Credits

Thanks to Tim Nelles for reporting and fixing this issue.

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).

GHSA-X9P2-77V6-6VHF has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.11); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is GHSA-X9P2-77V6-6VHF? GHSA-X9P2-77V6-6VHF is a critical-severity security vulnerability in github.com/dunglas/frankenphp (go), affecting versions < 1.1.11. It is fixed in 1.1.11.
2. How severe is GHSA-X9P2-77V6-6VHF? GHSA-X9P2-77V6-6VHF has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/dunglas/frankenphp are affected by GHSA-X9P2-77V6-6VHF? github.com/dunglas/frankenphp (go) versions < 1.1.11 is affected.
4. Is there a fix for GHSA-X9P2-77V6-6VHF? Yes. GHSA-X9P2-77V6-6VHF is fixed in 1.1.11. Upgrade to this version or later.
5. Is GHSA-X9P2-77V6-6VHF exploitable, and should I be worried? Whether GHSA-X9P2-77V6-6VHF is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-X9P2-77V6-6VHF is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-X9P2-77V6-6VHF? Upgrade github.com/dunglas/frankenphp to 1.1.11 or later.

Other vulnerabilities in github.com/dunglas/frankenphp