# CVE-2026-128027: FrankenPHP before 1.1.11 Delayed Propagation of Base Image Security Fixes


- **Severity:** Critical 9.3 (`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 in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 17 Nov 2026
- **Also known as:** GHSA-vjcc-8rh5-xp2j

## What is CVE-2026-128027?

CVE-2026-128027 is a critical vulnerability in frankenphp, published on 13 Nov 2026. 

### Official 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.

Weakness: CWE-1395 (Dependency on Vulnerable Third-Party Component)

## Which versions are affected by CVE-2026-128027?


## How do I fix CVE-2026-128027?

No fix has been published for CVE-2026-128027 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-128027 being exploited?

There is no known exploitation of CVE-2026-128027 in the wild and no public exploit code.

Public exploit code:

- GHSA-x9p2-77v6-6vhf PoC: a FrankenPHP image baked on a stale base snapshot ships libcrypto3 3.3.5, exposed to CVE-2025-15467 (pre-auth stack overflow in CMS parsing); the refreshed base ships 3.3.6 and rejects the same crafted CMS blob. ASan differential lab with registry-staleness evidence. (github_poc): https://github.com/googlesky/CVE-2026-128027

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128027 and fix it if it is affected.

What it is: CVE-2026-128027 is a critical vulnerability in frankenphp, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128027 in the wild and no public exploit code.

Affected product: frankenphp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128027/ (Markdown: https://insights.sbomify.com/CVE-2026-128027/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128027
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128027
- OSV: https://osv.dev/vulnerability/CVE-2026-128027

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128027/
Summaries are generated and may contain mistakes; the official description above is the record.
