Fluxcd Notification Controller
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in Fluxcd Notification Controller.
By the Year
In 2026 there have been 0 vulnerabilities in Fluxcd Notification Controller. Notification Controller did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 0 | 0.00 |
| 2025 | 0 | 0.00 |
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 1 | 4.30 |
It may take a day or so for new Notification Controller vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Fluxcd Notification Controller Security Vulnerabilities
Flux CD DoS via .spec.interval/.timeout (v<0.35)
CVE-2022-39272
4.3 - Medium
- October 22, 2022
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 version 0.35.0. As a workaround, Admission controllers can be employed to restrict the values that can be used for fields `.spec.interval` and `.spec.timeout`, however upgrading to the latest versions is still the recommended mitigation.
Improper Validation of Specified Quantity in Input
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Fluxcd Notification Controller or by Fluxcd? Click the Watch button to subscribe.
