CVE
FrankenPHP remote code execution via stale libraries in base image
Affects FrankenPHP Docker images before 1.1.11, which kept outdated Alpine, PHP and Go base layers when upstream fixes landed under existing tags. Fixed in 1.1.11.
Written by anthropic/claude-sonnet-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- Public exploit code, no confirmed attacks
- Fix
- Fixed in 1.1.11
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.1.11.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- First public exploit on GitHub Nov 14
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.78% · 56th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 65/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
Older FrankenPHP Docker images were not rebuilt when Alpine, PHP, and Go fixed security flaws under existing tags, so they still carry known bugs in outdated system libraries such as libcrypto3. A remote attacker can exploit these flaws over the network, without logging in, to run code on the affected system.
Original description
FrankenPHP Docker images before 1.1.11 were rebuilt only when new base image tags were created, so security fixes that Alpine, PHP, and Go applied under existing tags were not propagated. Remote attackers could exploit known flaws in the stale system libraries, such as CVE-2025-15467 in libcrypto3, to execute code.
Who should check
Teams running FrankenPHP Docker images before 1.1.11, or building their own images on top of FrankenPHP, whose Alpine, PHP or Go base layers may be stale.
“FrankenPHP Docker images before 1.1.11 were rebuilt only when new base image tags were created”
cve.now Index
- Exploitation22/40Public exploit on Exploit-DB or GitHub · Unknown: No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity9.3/10CVSS 9.3
- No patch0/5No signal
What would change the score
- Would score about 88 if added to CISA KEV
- Would score about 83 if CISA's SSVC rates exploitation active
- Would score about 70 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.1.11.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-128027 (FrankenPHP before 1.1.11 Delayed Propagation of Base Image Security Fixes), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-128027 (entry last updated 2026-11-13):
Affected:
- php frankenphp: fixed in 1.1.11
Fixed versions: 1.1.11.
Conditions (all must be true for the bug to be hit):
- Running FrankenPHP Docker images older than 1.1.11, built on Alpine, PHP and Go base images (source: https://www.vulncheck.com/advisories/frankenphp-before-1.1.11-delayed-propagation-of-base-image-security-fixes)
- Image keeps stale base layers because upstream fixes applied under existing tags were not rebuilt in (source: https://github.com/php/frankenphp/security/advisories/GHSA-x9p2-77v6-6vhf)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128027 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128027 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/frankenphp/security/advisories/GHSA-x9p2-77v6-6vhf
- https://www.vulncheck.com/advisories/frankenphp-before-1.1.11-delayed-propagation-of-base-image-security-fixes
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-128027
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128027"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now1 day
- Exploit code on GitHub
googlesky/CVE-2026-128027
Affected versions
- php frankenphp
fixed in 1.1.11
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Public exploit code · 1
Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
- Exploit
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128027
Is CVE-2026-128027 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).Source: cve.now feed data
What does this mean?
Before 1.1.11, FrankenPHP Docker images were rebuilt only when new base image tags appeared. If Alpine, PHP or Go images got a security patch under an existing tag, the FrankenPHP image stayed on the older, vulnerable layers, and known flaws in libraries such as libcrypto3 could remain in it.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-128027?
frankenphp: before 1.1.11.Source: cve.now feed data
Am I affected, and how do I check?
FrankenPHP Docker images older than 1.1.11, built on Alpine, PHP and Go base images, are in the affected range. To check, look at the FrankenPHP image tag or version in use and compare it with 1.1.11.Source: vulncheck.com, github.com
How do I fix CVE-2026-128027?
Upgrade to FrankenPHP 1.1.11 or later. The facts list no workaround.Source: vulncheck.com, github.com