Helm Controller denial of service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H

EPSS

• CVE-2022-36049: 1.54% estimated exploitation activity in the next 30 days; percentile 74.98 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK allows for specific data inputs to cause high memory consumption, which in some platforms could cause the controller to panic and stop processing reconciliations. Impact In a shared cluster multi-tenancy environment, a tenant could create a HelmRelease that makes the controller panic, denying all other tenants from their Helm releases being reconciled. Credits The initial crash bug was reported by oss-fuzz. The Flux Security team produced the first exploit and worked together with the Helm Security team to ensure that both projects were patched timely. For more information If you have any questions or comments about this advisory: - Open an issue in any of the affected repositories. - Contact us at the CNCF Flux Channel. References - https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48360 - https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44996 -…

Published by the source

16 Sep 2022, 18:49 UTC

Last modified by the source

27 Jan 2023, 05:03 UTC

Source last checked

26 Oct 2026, 14:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-p2g7-xwvr-rrw3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-36049

Advisory: Helm Controller denial of service
IDs: CVE-2022-36049, GHSA-p2g7-xwvr-rrw3
Record: https://patchnext.com/advisories/cve-2022-36049 (revision 1, source checked 26 Oct 2026, 14:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fluxcd/helm-controller 0.23.0; github.com/fluxcd/flux2 0.32.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fluxcd/helm-controller: affected >= 0.0.4, < 0.23.0; fixed in 0.23.0
- Go github.com/fluxcd/flux2: affected >= 0.0.17, < 0.32.0; fixed in 0.32.0

## Suggested inspection (read-only)
- Go github.com/fluxcd/helm-controller: check the installed version with your package manager.
- Go github.com/fluxcd/flux2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fluxcd/helm-controller, github.com/fluxcd/flux2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-p2g7-xwvr-rrw3 (GitHub-reviewed advisory GHSA-p2g7-xwvr-rrw3 lists affected ranges: Go github.com/fluxcd/helm-controller >=0.0.4 =0.0.17 <0.32.0)

Commands are suggestions: review each one before running it.