Advisory record · GHSA-85g2-pmrx-r49q

Fission runtime pods automount the fission-fetcher service-account token into the user function container, granting function code namespace-wide secret / configmap read

CVSS 8.7 HighEPSS 0.0035 · 28th percentile

Published by the GitHub Advisory Database at 21 May 2026, 20:16 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-85g2-pmrx-r49q · CVE-2026-46617 · GO-2026-5241
Weakness (CWE)
CWE-250 · CWE-269 · CWE-538
Published
21 May 2026
Updated
21 Jul 2026

Machine-written summary

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

Fission versions before 1.23.0 are affected: the fission-fetcher service account token is automounted into the user function container of runtime pods. A user who can deploy or update a function in a namespace where Fission runtime pods run can use the token to read every secret and configmap in that namespace. Upgrade the github.com/fission/fission Go module to 1.23.0 or later. Until then, restrict who can create or update Function and Package resources, and add network policies that block function pods from reaching the Kubernetes API server.

Written 6 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
8.7 High 4.0 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0035, the 28th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:05 UTC First seen by agentprime
  2. 31 Oct 2026, 15:05 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.