CVE-2026-47680

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (39th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-74295 (ENISA EUVD) · GHSA-jjrm-hr5f-673x (GitHub Security Advisories) · GO-2026-5472 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The source-controller is a Kubernetes operator, specialised in artifacts acquisition from external sources such as Git, OCI, Helm repositories and S3-compatible buckets. In versions 0.0.17 through 1.8.4, an actor with the ability to influence the contents of a bucket referenced by a Bucket resource can cause source-controller to write fetched object data to paths outside the per-reconciliation working directory. The corruption surface is bounded by source-controller's own and downstream Flux controllers' digest verification: source-controller verifies stored artifact digests during reconciliation and rebuilds on divergence; consumers (kustomize-controller, helm-controller) verify the digest of fetched artifacts and reject mismatches. These checks prevent a manipulated artifact from reaching the cluster, but an attacker can still write files anywhere the source-controller pod has permission to write. Separately, a user with permission to create or update GitRepository resources can cause source-controller to test for the existence of paths outside the cloned repository. Because the result is exposed via the resource's status, this allows limited enumeration of file paths on the controller pod. This surface exists only on source-controller v1.6.0 and later, where the sparse-checkout feature was introduced. This vulnerability was fixed in source-controller v1.8.5. There is no in-product workaround. Users should upgrade to a patched version. As a defense-in-depth measure for the GitRepository sparse-checkout surface, a ValidatingAdmissionPolicy (or a third-party policy engine such as Kyverno or OPA Gatekeeper) can be deployed to reject GitRepository resources whose .spec.sparseCheckout entries contain .. or absolute path segments.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 5, 2026

Last Modified

September 30, 2026

Advisory Details (3)

Auto-updated Sep 8, 2026
Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit 759bd6c451e7 (fluxcd/source-controller)

Fix landed in fluxcd/source-controller commit 759bd6c451e7 — awaiting tagged release

https://github.com/fluxcd/source-controller/commit/759bd6c451e7cc4327b38f42c8b671980165cb0e
GitHub pull request

Improve path handling in source reconcilers

Fix merged in fluxcd/source-controller PR #2054 on 2026-05-19 — awaiting tagged release

https://github.com/fluxcd/source-controller/pull/2054
GitHub advisoryMentions a patch (unverified)

Improper path handling allows traversal · Advisory · fluxcd/source-controller · GitHub

https://github.com/fluxcd/source-controller/security/advisories/GHSA-jjrm-hr5f-673x

Vendor Advisories for CVE-2026-47680(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/fluxcd/source-controller @ 1.8.5 (fixes >= 0.0.17, <= 1.8.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/fluxcd/source-controller—
  • 0.0.17 up to 1.8.5: fixed in 1.8.5
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-11-01 07:47 UTCEG score recompute
  3. 2026-11-01 07:47 UTCGHSA enrichmentGHSA-jjrm-hr5f-673x · GitHub severity MODERATE
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-30 14:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-25 14:24 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  14. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-22 23:12 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  21. 2026-10-18 03:35 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 42 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-10-12 16:01 UTCEG score recompute
  4. 2026-10-11 19:44 UTCEG score recompute
  5. 2026-10-11 16:59 UTCEG score recompute
  6. 2026-10-11 14:23 UTCEG score recompute
  7. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  9. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  10. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  14. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-09-30 20:04 UTCEG score recompute
  18. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  23. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  24. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  26. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  27. 2026-09-14 05:01 UTCEG score recompute
  28. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  29. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  31. 2026-09-09 13:40 UTCEG score recompute
  32. 2026-09-09 13:05 UTCEG score recompute
  33. 2026-09-08 23:21 UTCEG score recompute
  34. 2026-09-08 23:13 UTCEG score recomputeFirst assessed: 5.3 MEDIUM
  35. 2026-09-08 23:13 UTCMITRE cvelistV5CVSS v3 → 5.3 · CVSS v4 → 5.3
  36. 2026-08-01 11:11 UTCEG score recompute
  37. 2026-07-26 21:53 UTCEG score recompute
  38. 2026-07-23 03:17 UTCEG score recompute
  39. 2026-06-14 23:18 UTCEPSS rescoreEPSS <0.1% · 16th percentile
  40. 2026-06-13 23:00 UTCEPSS rescoreEPSS <0.1% · 16th percentile
  41. 2026-06-12 23:12 UTCEPSS rescoreEPSS <0.1% · 16th percentile
  42. 2026-06-05 16:57 UTCEG score recompute

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/fluxcd/source-controller

Frequently asked(5)

What is CVE-2026-47680?
CVE-2026-47680 is a medium-severity vulnerability; its CVE record was published on June 5, 2026. The source-controller is a Kubernetes operator, specialised in artifacts acquisition from external sources such as Git, OCI, Helm repositories and S3-compatible buckets. In versions 0.0.17 through 1.8.4, an actor with the ability to influence the contents of a bucket referenced by a Bucket resource…
When was the CVE record for CVE-2026-47680 published?
The CVE record for CVE-2026-47680 was published on June 5, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-47680 actively exploited?
CVE-2026-47680 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47680?
CVE-2026-47680 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47680?
A fix for CVE-2026-47680 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-47680 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-47680

Explore →

Is Your Infrastructure Affected by CVE-2026-47680?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs