NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2022-36049 — helm-controller

HIGH

CVE-2022-36049 is a high-severity (CVSS 7.7) Uncontrolled Resource Consumption vulnerability in github.com/fluxcd/helm-controller. A fix is available for github.com/fluxcd/helm-controller — see the affected versions and patch details below.

Flux2 Helm Controller denial of service

Also known asBIT-flux-2022-36049BIT-helm-2022-36049GHSA-p2g7-xwvr-rrw3
Published
Updated
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36049.

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.07%0.73%1.38%2.04%0.6%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected
🐹github.com/fluxcd/helm-controller🐹github.com/fluxcd/flux2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/fluxcd/helm-controller≥ 0.0.4&&< 0.23.00.23.0go get github.com/fluxcd/helm-controller@v0.23.0
🐹Gogithub.com/fluxcd/flux2≥ 0.0.17&&< 0.32.00.32.0go get github.com/fluxcd/flux2@v0.32.0

Affected Products

3 products · 3 configurations
Application
flux2fluxcd
≥ 0.0.17 && < 0.32.0
range
Application
helm-controllerfluxcd
≥ 0.0.4 && < 0.23.0
range
Application
helmhelm
≥ 3.0.0 && < 3.9.4
range

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/fluxcd/helm-controller, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/fluxcd/helm-controller to 0.23.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36049 is resolved across your whole dependency graph.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

Helm controller is tightly integrated with the Helm SDK. [A vulnerability](https://github.com/helm/helm/security/advisories/GHSA-7hfp-qfw3-5jxh) 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](https://gi
O3 Security · Impact-Aware SCA

Is CVE-2022-36049 in your dependencies?

Find it across Go, including transitive dependencies.

CVE-2022-36049: helm-controller — Fixed in 0.23.0