Skip to main content
VulnerabilityPublished

CVE-2026-49823: Fission · Cross-namespace Package read via unvalidated PackageRef in Function admission webhook

Affects github.com/fission/fissionSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.7 High : upgrade to 1.24.0 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.24.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade github.com/fission/fission to 1.24.0.

Affected software

ProductAffectedFixed in
Gogithub.com/fission/fissionAffected
  • <1.24.0
Fixed in
  • 1.24.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Fission version 1.24.0 or later, where the admission webhook enforces that Function.spec.package.packageref.namespace must match the Function's namespace. Functions that specify a different namespace for PackageRef are rejected at admission, preventing cross-namespace Package reads. Patch status: fixed in v1.24.0.

Description

A vulnerability in Fission prior to version 1.24.0 allows a function author in one namespace to read the deployment archive, including source code and embedded secrets, of any Package in any other namespace. This occurs because the admission webhook did not validate the PackageRef.Namespace field, allowing cross-namespace Package references. The issue is fixed in version 1.24.0 by enforcing namespace validation in the admission webhook.

References

Community reviews

Loading reviews…