VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/fluxcd/source-controller: vulnerability history, versions and safety

github.com/fluxcd/source-controller is a package in the Go ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from May 2024 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded M2 U2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 25 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/fluxcd/source-controller vulnerabilities

Vulert verdict on github.com/fluxcd/source-controller v1.9.6 i

Updated on 23 Oct 2026

Action needed: v1.9.6 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 78/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Moderate

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v1.9.6 — affected i
  • Vulnerabilities on record 4 over 2 years · 2 in the last year i
  • Latest disclosure 25 Jun 2026 i
  • Highest CVSS 5.3 i
  • With no published fix 0 i
  • Stars 286 i
  • OpenSSF scorecard 7/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for github.com/fluxcd/source-controller, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v1.9.1-0.20261022230756-81a72da7e775 22 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261022203101-3b734b6d4f2f 22 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261022164716-e3b7a6c04ac5 22 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261014195956-effd29b2da5b 14 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261014180806-b72ddd7e450c 14 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261012075658-d2a2b4cba663 12 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261010092927-7fd769bd2831 10 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261010030351-d96ad2ca812f 10 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261006101754-f78f4ff9981a 06 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261005153630-4e143357cb73 05 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261005091731-e47a59ad5d01 05 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261003215104-45cec61d284e 03 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261003214030-0032aca0151d 03 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261003210107-911e967c08f4 03 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261003205450-1f6721e337e6 03 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20261002203014-edccd85e3ca3 02 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.6 01 Oct 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260930151543-3b1dc95ff746 30 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260918114034-143c11a58d22 18 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260916143017-4a0e192ac5b2 16 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260901134828-3d828e0b9c87 01 Sep 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260831152233-259057b82c89 31 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.5 31 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260826144206-208961aa7bf3 26 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260807131522-99d894dd82c0 07 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.4 07 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260805104219-fee0a769af59 05 Aug 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260728080107-065d6efd74c2 28 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260713103915-e182c4759866 13 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.3 13 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260712124514-aadd5ebe424a 12 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.2 07 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260702185148-39b711b111fa 02 Jul 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1 30 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260629145849-938d388a812f 29 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.1-0.20260623200430-8721122d3d11 23 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.9.0 17 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260613102545-16e724e06907 13 Jun 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260520095106-524cf240a5dd 20 May 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.5 20 May 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260519114703-759bd6c451e7 19 May 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.4 12 May 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260425132011-73644f6b45cc 25 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.3 21 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260421084830-85d00c6e073b 21 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.2 07 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260401074728-7a113ec18f98 01 Apr 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260312125833-5376a7ead3e6 12 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1 12 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.1-0.20260312104057-870931f86237 12 Mar 2026 M1 U1 Apache-2.0 Yes Details →
v1.8.0 17 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20260216132756-a73fcfca0bc4 16 Feb 2026 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20260112144436-008e0db0f015 12 Jan 2026 M1 U1 Apache-2.0 Yes Details →
v0.0.0-20251206145824-eae8f25c2b44 06 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251206145824-eae8f25c2b44 06 Dec 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.4 19 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251118143826-4ca98f7263f5 18 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251112080632-05b26e8ddb27 12 Nov 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251028131852-974f3338c11d 28 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.3 28 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251009105120-3f9dc6324732 09 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251008141109-f2b25c6f513b 08 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.2 08 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251006084328-8ea0f36810ed 06 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1 06 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20251003090336-cbee72b3a788 03 Oct 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20250924164715-326a22a343f0 24 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.1-0.20250915155014-efb4d219a262 15 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0 15 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0-rc.3.0.20250912133252-eae8d198febe 12 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0-rc.2.0.20250905202013-eb1ff724ea17 05 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0-rc.3 05 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0-rc.2 04 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0-rc.1.0.20250904190504-48806528b77f 04 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250904164318-cf7222108cd0 04 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.7.0-rc.1 04 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250904111316-c8358d063c2c 04 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250903122502-46516fd54fa5 03 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250902170752-04ab27b42a4a 02 Sep 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250831120239-4702fe6c411b 31 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250822092814-12b5f6f0c5f2 22 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250817164920-e5189f67918e 17 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250815173332-24412ed278c8 15 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250815171000-4fe3434ee8c3 15 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250814175035-5f9702bb0126 14 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250814142135-48da00dba23e 14 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250814072223-cd5eebfb3230 14 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250812135301-bd6d090ef02c 12 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250812123130-a84403c95b7c 12 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250812073742-d69d743e75f0 12 Aug 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250731155856-c2b572bae03a 31 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250730033755-93b904870660 30 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250729134106-c43a3393a03a 29 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250721175814-a0b4969dc942 21 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250718124013-173a1cccc5cd 18 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250714221139-114a7024903f 14 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250701133426-8f77ed498100 01 Jul 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250627102154-32967c32c367 27 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.2 27 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250627084419-4dec4c28c0cb 27 Jun 2025 M1 U1 Apache-2.0 Yes Details →
v1.6.1-0.20250613162104-97c995b8c8e3 13 Jun 2025 M1 U1 — Yes Details →
v1.6.1 13 Jun 2025 M1 U1 — Yes Details →
v1.6.1-0.20250612175435-a5e476fce323 12 Jun 2025 M1 U1 — Yes Details →
v1.6.1-0.20250527140810-f2eaf74120a4 27 May 2025 M1 U1 — Yes Details →
v1.6.0 27 May 2025 M1 U1 — Yes Details →
v1.5.1-0.20250527084626-359d50d77e61 27 May 2025 M1 U1 — Yes Details →
v1.5.1-0.20250228192909-ba6d000437b3 28 Feb 2025 M1 U1 — Yes Details →
v1.5.1-0.20250213160748-6952276d79e0 13 Feb 2025 M1 U1 — Yes Details →
v1.5.0 13 Feb 2025 M1 U1 — Yes Details →
v1.3.1-0.20250211120600-c5046b839f93 11 Feb 2025 M1 U1 — Yes Details →
v1.3.1-0.20241212160442-fe7b1fecbab1 12 Dec 2024 M1 U1 — Yes Details →
v1.3.1-0.20241206150636-4d34b3f84362 06 Dec 2024 M1 U1 — Yes Details →
v1.3.1-0.20241205121758-af88ec2ba639 05 Dec 2024 M1 U1 — Yes Details →
v1.3.1-0.20241127181000-3b6896fec114 27 Nov 2024 M1 U1 — Yes Details →
v1.3.1-0.20240926165216-53868f7985fd 26 Sep 2024 M1 U1 — Yes Details →
v1.4.1 26 Sep 2024 M1 U1 — Yes Details →
v1.3.1-0.20240926154212-8baf4513f759 26 Sep 2024 M1 U1 — Yes Details →
v1.4.0 25 Sep 2024 M1 U1 — Yes Details →
v1.3.1-0.20240925064311-03889fecb1a2 25 Sep 2024 M1 U1 — Yes Details →
v1.3.1-0.20240916104646-ccdd523e06d1 16 Sep 2024 M1 U1 — Yes Details →

The newest 120 of 504 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for github.com/fluxcd/source-controller

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-47680: Source Controller Path Traversal Vulnerability in GitHub.com/fluxcd/source-controller 5.3 medium 1.8.5 05 Jun 2026
Open Source Vulnerability in source-controller 5.1 medium 1.2.5 15 May 2024
CVE-2024-31216: Azure Storage SAS Token Leak in github.com/fluxcd/source-controller N/A unrated 1.2.5 04 Jun 2024
CVE-2026-47680: Vulnerability in github.com/fluxcd/source-controller Allows Path Traversal N/A unrated 1.8.5 25 Jun 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About github.com/fluxcd/source-controller

Is github.com/fluxcd/source-controller safe to use?

Vulert records 4 vulnerabilities for github.com/fluxcd/source-controller in Go: 0 critical, 0 high, 2 medium and 0 low, plus 2 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/fluxcd/source-controller's Vulert package health score?

Vulert scores github.com/fluxcd/source-controller 78/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/fluxcd/source-controller affected?

Yes. v1.9.6, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/fluxcd/source-controller should I use?

v1.9.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/fluxcd/source-controller have?

4 vulnerabilities are recorded for github.com/fluxcd/source-controller in the Go ecosystem: 0 critical, 0 high, 2 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new github.com/fluxcd/source-controller vulnerabilities disclosed?

2 vulnerabilities were recorded for github.com/fluxcd/source-controller in the last 12 months, and the oldest entry in this database dates to 15 May 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of github.com/fluxcd/source-controller are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor github.com/fluxcd/source-controller for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/fluxcd/source-controller version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.