Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2022-39272: Flux is an open and extensible continuous delivery solution for Kubernetes

36
Routine
MEDIUM 5.0WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2022-39272 is a medium-severity flaw (CVSS 5.0) affecting flux2, helm-controller, image-automation-controller. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Flux is an open and extensible continuous delivery solution for Kubernetes. Versions prior to 0.35.0 are subject to a Denial of Service. Users that have permissions to change Flux’s objects, either through a Flux source or directly within a cluster, can provide invalid data to fields `.spec.interval` or `.spec.timeout` (and structured variations of these fields), causing the entire object type to stop being processed. This issue is patched in ver

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score5.0 (Medium)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededLow
User interactionNone
EPSS exploit chance0.8% (top 44%)
CISA exploited listNo
WeaknessCWE-1284
Published2022-10-22
Last modified2026-06-17
Publisher (CNA): GitHub, Inc. · Vendor: fluxcd

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

fluxcd flux2 UPGRADE
Affected: >= 0.1.0 and < 0.35.0
Fixed in: 0.35.0
Safe to downgrade to: a release before 0.1.0
1. Check installed version
apt-cache policy flux2 || rpm -q flux2 || flux2 --version
2. UPGRADE to 0.35.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade flux2
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade flux2
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.1.0 (Debian / Ubuntu)
apt-cache madison flux2 sudo apt install flux2=<VERSION_BEFORE_0.1.0> sudo apt-mark hold flux2
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list flux2 sudo dnf downgrade flux2-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add flux2
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fluxcd helm-controller UPGRADE
Affected: >= 0.0.2 and < 0.24.0 · 0.0.1 alpha1 · 0.0.1 alpha2 · 0.0.1 beta1 · 0.0.1 beta2 · 0.0.1 beta3 · 0.0.1 beta4
Fixed in: 0.24.0
Safe to downgrade to: a release before 0.0.1
1. Check installed version
apt-cache policy helm-controller || rpm -q helm-controller || helm-controller --version
2. UPGRADE to 0.24.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade helm-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade helm-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.0.1 (Debian / Ubuntu)
apt-cache madison helm-controller sudo apt install helm-controller=<VERSION_BEFORE_0.0.1> sudo apt-mark hold helm-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list helm-controller sudo dnf downgrade helm-controller-<VERSION_BEFORE_0.0.1> sudo dnf versionlock add helm-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fluxcd image-automation-controller UPGRADE
Affected: >= 0.1.0 and < 0.26.0
Fixed in: 0.26.0
Safe to downgrade to: a release before 0.1.0
1. Check installed version
apt-cache policy image-automation-controller || rpm -q image-automation-controller || image-automation-controller --version
2. UPGRADE to 0.26.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade image-automation-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade image-automation-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.1.0 (Debian / Ubuntu)
apt-cache madison image-automation-controller sudo apt install image-automation-controller=<VERSION_BEFORE_0.1.0> sudo apt-mark hold image-automation-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list image-automation-controller sudo dnf downgrade image-automation-controller-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add image-automation-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fluxcd image-reflector-controller UPGRADE
Affected: >= 0.1.0 and < 0.22.0
Fixed in: 0.22.0
Safe to downgrade to: a release before 0.1.0
1. Check installed version
apt-cache policy image-reflector-controller || rpm -q image-reflector-controller || image-reflector-controller --version
2. UPGRADE to 0.22.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade image-reflector-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade image-reflector-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.1.0 (Debian / Ubuntu)
apt-cache madison image-reflector-controller sudo apt install image-reflector-controller=<VERSION_BEFORE_0.1.0> sudo apt-mark hold image-reflector-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list image-reflector-controller sudo dnf downgrade image-reflector-controller-<VERSION_BEFORE_0.1.0> sudo dnf versionlock add image-reflector-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fluxcd kustomize-controller UPGRADE
Affected: >= 0.0.2 and < 0.29.0 · 0.0.1 alpha1 · 0.0.1 alpha2 · 0.0.1 alpha3 · 0.0.1 alpha4 · 0.0.1 alpha5 · 0.0.1 alpha6 · 0.0.1 alpha7
Fixed in: 0.29.0
Safe to downgrade to: a release before 0.0.1
1. Check installed version
apt-cache policy kustomize-controller || rpm -q kustomize-controller || kustomize-controller --version
2. UPGRADE to 0.29.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade kustomize-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade kustomize-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.0.1 (Debian / Ubuntu)
apt-cache madison kustomize-controller sudo apt install kustomize-controller=<VERSION_BEFORE_0.0.1> sudo apt-mark hold kustomize-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list kustomize-controller sudo dnf downgrade kustomize-controller-<VERSION_BEFORE_0.0.1> sudo dnf versionlock add kustomize-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
fluxcd notification-controller UPGRADE
Affected: >= 0.0.2 and < 0.27.0 · 0.0.1 alpha1 · 0.0.1 alpha2 · 0.0.1 beta1
Fixed in: 0.27.0
Safe to downgrade to: a release before 0.0.1
1. Check installed version
apt-cache policy notification-controller || rpm -q notification-controller || notification-controller --version
2. UPGRADE to 0.27.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade notification-controller
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade notification-controller
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 0.0.1 (Debian / Ubuntu)
apt-cache madison notification-controller sudo apt install notification-controller=<VERSION_BEFORE_0.0.1> sudo apt-mark hold notification-controller
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list notification-controller sudo dnf downgrade notification-controller-<VERSION_BEFORE_0.0.1> sudo dnf versionlock add notification-controller
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-39272?

flux2: upgrade to 0.35.0; helm-controller: upgrade to 0.24.0; image-automation-controller: upgrade to 0.26.0. Exact commands for each OS are on this page.

Is CVE-2022-39272 being exploited?

CVE-2022-39272 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-39272 affect?

CVE-2022-39272 affects flux2, helm-controller, image-automation-controller. Severity is medium (CVSS 5.0). Flux is an open and extensible continuous delivery solution for Kubernetes. Versions prior to 0.35.0 are subject to a Denial of Service. Users that have permissions to change Flux’s objects, either through a Flux source or directly within a

How urgent is CVE-2022-39272?

Priority 36/100. On your watchlist

Software pages

Kubernetes vulnerabilities · Helm vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.