{"id":"CVE-2022-36049","aliases":["AZL-10900","BIT-flux-2022-36049","BIT-helm-2022-36049","EUVD-2022-6887","GHSA-p2g7-xwvr-rrw3"],"status":"published","title":"Flux2 Helm Controller denial of service","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","severity":{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.01542,"percentile":0.75136,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-400","CWE-770"],"published":"2022-09-07T20:15:13Z","modified":"2026-10-28T02:30:52Z","fixes":[{"ecosystem":"Go","package":"github.com/fluxcd/helm-controller","fixed_in":["0.23.0"],"sources":["ghsa","osv"]},{"ecosystem":"Go","package":"github.com/fluxcd/flux2","fixed_in":["0.32.0"],"sources":["ghsa","osv"]},{"ecosystem":"Azure Linux:2","package":"helm","fixed_in":["3.9.4-2"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"flux","fixed_in":["0.32.0"],"sources":["osv"]},{"ecosystem":"Bitnami","package":"helm","fixed_in":["3.9.4"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"Go","package":"github.com/fluxcd/helm-controller","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.0.4"},{"fixed":"0.23.0"}]}]},{"source":"ghsa","ecosystem":"Go","package":"github.com/fluxcd/flux2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.0.17"},{"fixed":"0.32.0"}]}]},{"source":"osv","ecosystem":"Azure Linux:2","package":"helm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.9.4-2"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"flux","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.17"},{"fixed":"0.32.0"}]}]},{"source":"osv","ecosystem":"Bitnami","package":"helm","ranges":[{"type":"SEMVER","events":[{"introduced":"3.0.0"},{"fixed":"3.9.4"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/fluxcd/helm-controller","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.4"},{"fixed":"0.23.0"}]}]},{"source":"osv","ecosystem":"Go","package":"github.com/fluxcd/flux2","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.17"},{"fixed":"0.32.0"}]}]}],"products":[{"vendor":"fluxcd","product":"flux2"},{"vendor":"fluxcd","product":"helm-controller"},{"vendor":"helm","product":"helm"}],"references":[{"url":"https://github.com/fluxcd/flux2/security/advisories/GHSA-p2g7-xwvr-rrw3","tags":["x_refsource_CONFIRM","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://github.com/helm/helm/security/advisories/GHSA-7hfp-qfw3-5jxh","tags":["x_refsource_MISC","x_transferred","Third Party Advisory","advisory","web"]},{"url":"https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44996","tags":["x_refsource_MISC","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48360","tags":["x_refsource_MISC","x_transferred","Mailing List","Third Party Advisory","advisory","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-36049","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-p2g7-xwvr-rrw3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/36xxx/CVE-2022-36049.json","tags":["advisory"]},{"url":"https://github.com/fluxcd/flux2","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2022-36049","title":"Flux2 Helm Controller denial of service","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2022-09-07T20:15:13Z","modified":"2025-04-23T17:14:00.853Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high","assessor":"cna"}],"cwes":["CWE-400"],"updated_at":"2026-11-02T14:34:35.945659Z"}],"euvd":[{"id":"EUVD-2022-6887","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2022-09-07T20:15:13Z","modified":"2025-04-23T17:14:00Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T20:52:10.906327Z"}],"ghsa":[{"id":"GHSA-p2g7-xwvr-rrw3","title":"Helm Controller denial of service","description":"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.\n\n### Impact\nIn 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.\n\n### Credits\n\nThe initial crash bug was reported by [oss-fuzz](https://github.com/google/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.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in any of the affected repositories.\n- Contact us at the CNCF Flux Channel.\n\n### References\n\n- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48360\n- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44996\n- https://github.com/helm/helm/security/advisories/GHSA-7hfp-qfw3-5jxh\n","status":"published","published":"2022-09-16T18:49:48Z","modified":"2023-01-27T05:03:11Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:36:20.144464Z"}],"nvd":[{"id":"CVE-2022-36049","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2022-09-07T21:15:08.483Z","modified":"2026-06-17T04:52:48.74Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high","assessor":"secondary"},{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T14:07:26.802986Z"}],"osv":[{"id":"AZL-10900","title":"CVE-2022-36049 affecting package helm for versions less than 3.9.4-2","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2022-09-07T21:15:08Z","modified":"2026-04-21T04:21:37.460991Z","cvss":[{"version":"3.1","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:02.044071Z"},{"id":"CVE-2022-36049","title":"Flux2 Helm Controller denial of service","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2022-09-07T20:15:13Z","modified":"2026-10-28T02:30:52.489346603Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400"],"updated_at":"2026-11-02T15:44:26.195407Z"},{"id":"GHSA-p2g7-xwvr-rrw3","title":"Helm Controller denial of service","description":"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.\n\n### Impact\nIn 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.\n\n### Credits\n\nThe initial crash bug was reported by [oss-fuzz](https://github.com/google/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.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n- Open an issue in any of the affected repositories.\n- Contact us at the CNCF Flux Channel.\n\n### References\n\n- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=48360\n- https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=44996\n- https://github.com/helm/helm/security/advisories/GHSA-7hfp-qfw3-5jxh\n","status":"published","published":"2022-09-16T18:49:48Z","modified":"2026-02-04T02:59:17.730653Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-400","CWE-770"],"updated_at":"2026-11-02T15:46:52.534897Z"},{"id":"BIT-flux-2022-36049","title":"Flux2 Helm Controller denial of service","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2025-12-02T17:36:59.799Z","modified":"2026-09-08T08:47:10.360032624Z","updated_at":"2026-11-02T15:28:29.999658Z"},{"id":"BIT-helm-2022-36049","title":"Flux2 Helm Controller denial of service","description":"Flux2 is a tool for keeping Kubernetes clusters in sync with sources of configuration, and Flux's helm-controller is a Kubernetes operator that allows one to declaratively manage Helm chart releases. Helm controller is tightly integrated with the Helm SDK. A vulnerability found in the Helm SDK that affects flux2 v0.0.17 until v0.32.0 and helm-controller v0.0.4 until v0.23.0 allows for specific data inputs to cause high memory consumption. In some platforms, this could cause the controller to panic and stop processing reconciliations. 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. Patches are available in flux2 v0.32.0 and helm-controller v0.23.0.","status":"published","published":"2024-03-06T10:53:31.97Z","modified":"2026-09-08T08:48:23.092246466Z","updated_at":"2026-11-02T15:28:31.02759Z"}]}}