CVE-2025-47283

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2025-05-19. NVD baseline CVSS 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3

Also known asEUVD-2025-15799 (ENISA EUVD) · GHSA-3hw7-qj9h-r835 (GitHub Security Advisories) · GO-2025-3696 (OSV.dev)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 9.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Gardener implements the automated management and operation of Kubernetes clusters as a service. A security vulnerability was discovered in Gardener prior to versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 that could allow a user with administrative privileges for a Gardener project to obtain control over the seed cluster(s) where their shoot clusters are managed. This CVE affects all Gardener installations no matter of the public cloud provider(s) used for the seed clusters/shoot clusters. gardener/gardener (gardenlet) is the affected component. Versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 fix the issue.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
45
EG Risk 45/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.7% × 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 low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.7%
EPSS %ILE
52nd
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 (9.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

EG Severity
9.9 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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 low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 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 low or medium mission impact; Track* at high (mission-essential systems).

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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)14 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 total (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

May 19, 2025

Last Modified

February 6, 2026

Advisory Details (5)

Auto-updated Nov 6, 2026
Patch available. Sources: github, github_commit.
GitHub advisoryMentions a patch (unverified)

Bypassing project secret validation can lead to privilege escalation · Advisory · gardener/gardener · GitHub

https://github.com/gardener/gardener/security/advisories/GHSA-3hw7-qj9h-r835
GitHub commit

commit cf4e9887d839 (gardener/gardener)

Fix landed in gardener/gardener commit cf4e9887d839 — awaiting tagged release

https://github.com/gardener/gardener/commit/cf4e9887d83902216b85609caf563f7a9dd2de00
GitHub commit

commit bbd19b1dd3a3 (gardener/gardener)

Fix landed in gardener/gardener commit bbd19b1dd3a3 — awaiting tagged release

https://github.com/gardener/gardener/commit/bbd19b1dd3a31843d7b820172d37f75298dfaf8b
GitHub commit

commit b89cf2cd5067 (gardener/gardener)

Fix landed in gardener/gardener commit b89cf2cd5067 — awaiting tagged release

https://github.com/gardener/gardener/commit/b89cf2cd5067e82f364063d5241af73650a6e11d
GitHub commit

commit 924b1575aae0 (gardener/gardener)

Fix landed in gardener/gardener commit 924b1575aae0 — awaiting tagged release

https://github.com/gardener/gardener/commit/924b1575aae052bcda5a51fac8594d38fa3c41b0

Vendor Advisories for CVE-2025-47283(1)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/gardener/gardener @ 1.116.4 (fixes < 1.116.4)—ghsa
gogithub.com/gardener/gardener @ 1.117.5 (fixes >= 1.117.0, < 1.117.5)—ghsa
gogithub.com/gardener/gardener @ 1.118.2 (fixes >= 1.118.0, < 1.118.2)—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/gardener/gardener—
  • every version up to 1.116.4: fixed in 1.116.4
  • 1.117.0 up to 1.117.5: fixed in 1.117.5
  • 1.118.0 up to 1.118.2: fixed in 1.118.2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 43× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 259 rows on record for this CVE, as 98 entries (2 repeats merged).

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 159 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-11-12 07:27 UTCEchelonGraph re-scored
  3. 2026-11-12 07:27 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-11 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-11-11 06:10 UTCEchelonGraph re-scored
  6. 2026-11-11 06:10 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-10 16:40 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-11-10 04:51 UTCEchelonGraph re-scored
  9. 2026-11-10 04:51 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-09 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-11-09 03:34 UTCEchelonGraph re-scored
  12. 2026-11-09 03:34 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  13. 2026-11-08 16:37 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-11-08 02:18 UTCEchelonGraph re-scored
  15. 2026-11-08 02:18 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  16. 2026-11-07 16:36 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-11-07 00:59 UTCEchelonGraph re-scored
  18. 2026-11-07 00:59 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  19. 2026-11-06 16:34 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-11-05 23:41 UTCEchelonGraph re-scored
  21. 2026-11-05 23:41 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  22. 2026-11-05 16:35 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-11-05 13:55 UTCOSV refresh
  24. 2026-11-04 22:24 UTCEchelonGraph re-scored
  25. 2026-11-04 22:24 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
Show 73 more
  1. 2026-11-04 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  2. 2026-11-03 20:59 UTCEchelonGraph re-scored
  3. 2026-11-03 20:59 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  4. 2026-11-03 16:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-11-02 19:43 UTCEchelonGraph re-scored
  6. 2026-11-02 19:43 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  7. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  8. 2026-11-01 18:26 UTCEchelonGraph re-scored
  9. 2026-11-01 18:26 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  10. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  11. 2026-11-01 08:05 UTCGHSA enrichmentGHSA-3hw7-qj9h-r835 · GitHub severity CRITICAL · GitHub CVSS 9.9
  12. 2026-11-01 08:05 UTCEchelonGraph re-scored
  13. 2026-10-31 17:09 UTCEchelonGraph re-scored
  14. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-10-30 16:32 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-10-30 15:50 UTCEchelonGraph re-scored
  17. 2026-10-29 16:31 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-10-29 14:34 UTCEchelonGraph re-scored
  19. 2026-10-28 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-10-28 13:17 UTCEchelonGraph re-scored
  21. 2026-10-27 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  22. 2026-10-27 11:55 UTCEchelonGraph re-scored
  23. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  24. 2026-10-26 10:38 UTCEchelonGraph re-scored
  25. 2026-10-25 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  26. 2026-10-25 16:23 UTCEchelonGraph re-scored
  27. 2026-10-25 09:22 UTCEchelonGraph re-scored
  28. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  29. 2026-10-24 08:05 UTCEchelonGraph re-scored
  30. 2026-10-23 16:30 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  31. 2026-10-23 06:47 UTCEchelonGraph re-scored
  32. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  33. 2026-10-22 05:30 UTCEchelonGraph re-scored
  34. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  35. 2026-10-21 04:12 UTCEchelonGraph re-scored
  36. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  37. 2026-10-20 02:52 UTCEchelonGraph re-scored
  38. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  39. 2026-10-19 01:35 UTCEchelonGraph re-scored
  40. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  41. 2026-10-18 05:31 UTCEchelonGraph re-scored
  42. 2026-10-18 00:17 UTCEchelonGraph re-scored
  43. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  44. 2026-10-16 22:56 UTCEchelonGraph re-scored
  45. 2026-10-16 16:38 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  46. 2026-10-15 19:58 UTCEchelonGraph re-scored
  47. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  48. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  49. 2026-10-14 13:54 UTCEchelonGraph re-scored
  50. 2026-10-13 16:32 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  51. 2026-10-12 17:02 UTCEchelonGraph re-scored
  52. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  53. 2026-10-11 20:35 UTCEchelonGraph re-scored
  54. 2026-10-11 18:47 UTCEchelonGraph re-scored
  55. 2026-10-11 15:23 UTCEchelonGraph re-scored
  56. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  57. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  58. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  59. 2026-10-08 17:10 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  60. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  61. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  62. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  63. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  64. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  65. 2026-10-02 13:10 UTCOSV refresh
  66. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  67. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  68. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  69. 2026-09-27 13:45 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  70. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.6% · 49th percentile
  71. 2026-09-26 00:25 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  72. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  73. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.6% · 49th percentile

Related CVEs(same product + same CWE)

Same product

2 shown

Go:github.com/gardener/gardener

Frequently asked(5)

What is CVE-2025-47283?
CVE-2025-47283 is a critical-severity vulnerability; its CVE record was published on May 19, 2025. Gardener implements the automated management and operation of Kubernetes clusters as a service. A security vulnerability was discovered in Gardener prior to versions 1.116.4, 1.117.5, 1.118.2, and 1.119.0 that could allow a user with administrative privileges for a Gardener project to obtain…
When was the CVE record for CVE-2025-47283 published?
The CVE record for CVE-2025-47283 was published on May 19, 2025. 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 February 6, 2026; the record at its source may have been updated since.
Is CVE-2025-47283 actively exploited?
CVE-2025-47283 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (52nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-47283?
CVE-2025-47283 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-47283?
A fix for CVE-2025-47283 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2025-47283 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-2025-47283

Explore →

Is Your Infrastructure Affected by CVE-2025-47283?

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

Book a Demo →Browse All CVEs