Is CVE-2026-49823 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-49823 being exploited in the wild.

How severe is CVE-2026-49823?

High severity, with a CVSS score of 7.7, published 10 June 2026.

Which products and versions are affected?

Fission <= 1.23.0; github.com/fission/fission (Go) <= 1.23.0, SEMVER:introduced=0,fixed=1.24.0.

Is there a fix for CVE-2026-49823?

Yes. github.com/fission/fission (Go): upgrade to 1.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-49823 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-49823?

Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49823: Fission improper authorization in Function PackageRef namespace validation

Q: Which products and versions are affected?

Fission <= 1.23.0; github.com/fission/fission (Go) <= 1.23.0, SEMVER:introduced=0,fixed=1.24.0.

Q: Is there a fix for CVE-2026-49823?

Yes. github.com/fission/fission (Go): upgrade to 1.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-49823 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-49823?

Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-49823 · Severity: high · CVSS 7.7 · Published 2026-06-10

Fission is a framework for running serverless functions on Kubernetes. A security flaw allowed a user in one project area (namespace) to access the source code and sensitive credentials of functions belonging to other projects. This could lead to the theft of intellectual property or the exposure of passwords and API keys used by other teams within the same cluster.

Technologies: Fission, github.com/fission/fission (Go). Vendors: Fission, Go.

Quick answers

Is CVE-2026-49823 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-49823 being exploited in the wild.
How severe is CVE-2026-49823?: High severity, with a CVSS score of 7.7, published 10 June 2026.
Which products and versions are affected?: Fission <= 1.23.0; github.com/fission/fission (Go) <= 1.23.0, SEMVER:introduced=0,fixed=1.24.0.
Is there a fix for CVE-2026-49823?: Yes. github.com/fission/fission (Go): upgrade to 1.24.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-49823 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-49823?: Check whether you run Fission or github.com/fission/fission (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/fission/fission (Go): upgrade to 1.24.0 or later
```
go get github.com/fission/fission@v1.24.0
```

Technical details

A vulnerability in the Fission Function admission webhook exists due to missing namespace validation for 'PackageRef.Namespace'. An attacker with permissions to create functions in their own namespace can specify a 'PackageRef' pointing to a different namespace. When the function is invoked, the 'fission-fetcher' service account—which possesses cluster-wide 'get packages' permissions—retrieves the target package and writes its contents to the attacker's pod. This allows for the extraction of deployment archives, source code, and embedded secrets from any package in the cluster. The issue is fixed in version 1.24.0 by enforcing that the package namespace matches the function's metadata namespace.

Affected products

fission fission <= 1.23.0

Identifiers

CVE-2026-49823
GHSA-3r8v-2xmj-5c39
GO-2026-5846

Timeline

2026-05-26: disclosed
2026-06-10: kev added: NVD Published Date
2026-06-30: advisory: GitHub Advisory published/reviewed
1.24.0: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.