FrankenPHP Docker Images Security Update Missing Vulnerabilities

Executive Summary

FrankenPHP Docker images before version 1.1.11 did not automatically incorporate security fixes from base images like Alpine, PHP, and Go. This meant existing image tags contained outdated and vulnerable system libraries, such as libcrypto3 with CVE-2025-15467, which remote attackers could exploit to execute arbitrary code.

Useful 0 Not Useful 0

Detection Guidance

Check FrankenPHP Docker image versions in use with 'docker images | grep frankenphp'. Verify if images are older than 1.1.11. Inspect base image layers for outdated libraries like libcrypto3 using 'docker inspect <image> | grep -i libcrypto3'.

Useful 0 Not Useful 0

Impact Analysis

If you used FrankenPHP Docker images before 1.1.11, your system may have been running outdated and vulnerable libraries. Attackers could exploit known flaws like CVE-2025-15467 to execute code remotely, potentially gaining control of your system or accessing sensitive data.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to non-compliance with GDPR or HIPAA if it results in unauthorized access to personal or health data due to exploited vulnerabilities in outdated libraries. Organizations may face penalties for failing to maintain secure systems.

Useful 0 Not Useful 0

Mitigation Strategies

Update all FrankenPHP Docker images to version 1.1.11 or later. Use 'docker pull --pull <image>' to force a fresh download of base layers. Rebuild containers with updated images to ensure patched dependencies.

Useful 0 Not Useful 0