Advisory record · GHSA-7pjr-qpvh-m339

Fission builder accepts arbitrary buildcmd strings from Environment.spec.builder.command, allowing the builder pod to invoke arbitrary executables

CVSS 6.9 MediumEPSS 0.0036 · 30th percentile

Published by the GitHub Advisory Database at 21 May 2026, 20:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/fission/fissionGo<1.23.01.23.0
Identifiers
GHSA-7pjr-qpvh-m339 · CVE-2026-46618 · GO-2026-5230
Weakness (CWE)
CWE-78 · CWE-250 · CWE-269
Published
21 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Fission versions before 1.23.0 pass the Environment builder command straight to exec without validating the executable, so a user who can create or update Environment objects in a namespace watched by buildermgr can run arbitrary executables inside the builder pod. That pod can read and write the shared package volume, which bounds the impact to that namespace's package contents. Upgrade to 1.23.0, which validates the build command path. Until then, restrict who can create or modify Environment objects and audit existing builder command values for anything other than /build.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.9 Medium 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0036, the 30th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.