php / php/frankenphp

Vulnerable Go dependencies in FrankenPHP v1.12.7 detected by Trivy

Open
#2,643 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
11.3k
Forks
488
Avg merge
4d 10h
Merged PRs (30d)
11

Description

Vulnerable Go dependencies in FrankenPHP v1.12.7 detected by Trivy

Description

We are using the official FrankenPHP image:

FROM dunglas/frankenphp:1.12.7-builder-php8.4.25-alpine

and Trivy reports two critical vulnerabilities embedded in the frankenphp binary:

usr/local/bin/frankenphp (gobinary)

github.com/getkin/kin-openapi v0.140.0
GHSA-r277-6w6q-xmqw
Fixed version: 0.144.0

golang.org/x/crypto v0.54.0
CVE-2026-56854
Fixed version: 0.55.0
Trivy output
Target: usr/local/bin/frankenphp

github.com/getkin/kin-openapi
Installed Version: v0.140.0
Fixed Version: 0.144.0

golang.org/x/crypto
Installed Version: v0.54.0
Fixed Version: 0.55.0
Questions
  • Are these dependencies still present in FrankenPHP v1.12.7?

  • Have they already been updated on the main branch?

  • Is there a planned release containing:

    • github.com/getkin/kin-openapi >= 0.144.0
    • golang.org/x/crypto >= 0.55.0
  • Is there a recommended mitigation until a new release is available?

Thanks for your help.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by checking the FrankenPHP v1.12.7 builder image and the main branch against the reported dependency versions. Confirm whether kin-openapi is at least 0.144.0 and x/crypto at least 0.55.0, then document the affected release, available mitigation, and release path.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, go
Domain
devops, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.