CVE-2026-62290

HIGHPre-NVD 7.37.3
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (1st 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

Also known asEUVD-2026-45017 (ENISA EUVD) · GHSA-8rvj-mm4h-c258 (GitHub Security Advisories)Source: ENISA EUVD

7.3EG
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.1%CVSS: 7.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates. From 1.18.0 until 1.19.6 and 1.20.3, Challenge resources under acme.cert-manager.io can be created directly by namespace users without admission validation tying the Challenge to an Order, owner reference, or Issuer-selected solver, allowing attacker-controlled Challenge.spec.solver values referencing a ClusterIssuer to bypass DNS01 solver selectors such as dnsZones, dnsNames, and matchLabels and cause cert-manager to use ClusterIssuer DNS credentials for attacker-selected provider settings and DNS names, including disclosure of X-Api-User and X-Api-Key headers for acme-dns. This issue is fixed in versions 1.19.6 and 1.20.3.

CVSS v3
7.3
EG Score
7.3HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity73% × 45%
Impact severity (EG Severity): CVSS 7.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
1st
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 (7.3): severity, escalated by confirmed exploitation. This CVE's 7.3 is its impact severity (EG Severity), not escalated.

EG Severity
7.3 HIGHCVSS-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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). 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

July 16, 2026

Last Modified

July 30, 2026

Advisory Details (7)

Auto-updated Jul 16, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Direct ACME Challenge resources can bypass Issuer DNS01 solver policy and use ClusterIssuer DNS credentials · Advisory · cert-manager/cert-manager · GitHub

https://github.com/cert-manager/cert-manager/security/advisories/GHSA-8rvj-mm4h-c258
GitHub release Patch Available

v1.20.3

Patch available: cert-manager/cert-manager v1.20.3

https://github.com/cert-manager/cert-manager/releases/tag/v1.20.3
GitHub release Patch Available

v1.19.6

Patch available: cert-manager/cert-manager v1.19.6

https://github.com/cert-manager/cert-manager/releases/tag/v1.19.6
GitHub pull request Patch Available

[release-1.19] Restrict Challenge and Order verbs in aggregate edit ClusterRole

Patch available: cert-manager/cert-manager v1.19.6 (PR #8941 merged 2026-06-25)

https://github.com/cert-manager/cert-manager/pull/8941
GitHub pull request Patch Available

[release-1.20] Restrict Challenge and Order verbs in aggregate edit ClusterRole

Patch available: cert-manager/cert-manager v1.20.3 (PR #8940 merged 2026-06-25)

https://github.com/cert-manager/cert-manager/pull/8940
GitHub commit Patch Available

commit b37dbf01ecea (cert-manager/cert-manager)

Patch available: cert-manager/cert-manager v1.19.6 (contains commit b37dbf01ecea)

https://github.com/cert-manager/cert-manager/commit/b37dbf01ecea50a0b3a19df0a7fe4c5ad6803f16
GitHub commit Patch Available

commit 6bda47297c8f (cert-manager/cert-manager)

Patch available: cert-manager/cert-manager v1.20.3 (contains commit 6bda47297c8f)

https://github.com/cert-manager/cert-manager/commit/6bda47297c8fbc6b121b8b76624b668d26f1a155

Vendor Advisories for CVE-2026-62290(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 33× 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.

Showing the most recent 100 of 129 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-27 19:01 UTCEG score recompute
  6. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-25 14:14 UTCEG score recompute
  10. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-20 09:22 UTCEG score recompute
  15. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-10-18 03:24 UTCEG score recompute
  17. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-10-13 12:56 UTCEG score recompute
  21. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-10-12 15:49 UTCEG score recompute
  23. 2026-10-11 19:34 UTCEG score recompute
  24. 2026-10-11 16:49 UTCEG score recompute
  25. 2026-10-11 14:11 UTCEG score recompute
Show 75 more
  1. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  4. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-01 11:22 UTCEG score recompute
  13. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-09-28 08:16 UTCEG score recompute
  15. 2026-09-24 06:58 UTCEG score recompute
  16. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-23 03:01 UTCEG score recompute
  18. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-18 04:38 UTCEG score recompute
  21. 2026-09-17 10:29 UTCEG score recompute
  22. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-13 23:05 UTCEG score recompute
  24. 2026-09-13 07:07 UTCEG score recompute
  25. 2026-09-11 21:39 UTCEG score recompute
  26. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  27. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  28. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-09-08 00:26 UTCEG score recompute
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  31. 2026-09-05 20:33 UTCEG score recompute
  32. 2026-09-04 05:07 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  33. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  35. 2026-08-31 04:29 UTCEG score recompute
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-08-30 03:30 UTCEG score recompute
  38. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  39. 2026-08-28 21:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  40. 2026-08-28 01:49 UTCEG score recompute
  41. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-08-27 00:17 UTCEG score recompute
  43. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-08-25 20:58 UTCEG score recompute
  45. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  46. 2026-08-24 19:18 UTCEG score recompute
  47. 2026-08-22 01:11 UTCEG score recompute
  48. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  49. 2026-08-21 00:34 UTCEG score recompute
  50. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  51. 2026-08-19 23:52 UTCEG score recompute
  52. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  53. 2026-08-17 14:01 UTCEG score recompute
  54. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  55. 2026-08-17 01:43 UTCEG score recompute
  56. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  57. 2026-08-16 13:24 UTCEG score recompute
  58. 2026-08-15 12:47 UTCEG score recompute
  59. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  60. 2026-08-13 23:48 UTCEG score recompute
  61. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-08-12 23:07 UTCEG score recompute
  63. 2026-08-12 13:51 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-08-11 22:30 UTCEG score recompute
  65. 2026-08-11 10:12 UTCEG score recompute
  66. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  67. 2026-08-09 21:17 UTCEG score recompute
  68. 2026-08-09 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-08-08 20:41 UTCEG score recompute
  70. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  71. 2026-08-07 20:04 UTCEG score recompute
  72. 2026-08-06 19:27 UTCEG score recompute
  73. 2026-08-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  74. 2026-08-06 07:08 UTCEG score recompute
  75. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile

Frequently asked(5)

What is CVE-2026-62290?
CVE-2026-62290 is a high-severity vulnerability; its CVE record was published on July 16, 2026. cert-manager adds certificates and certificate issuers as resource types in Kubernetes clusters, and simplifies the process of obtaining, renewing and using those certificates. From 1.18.0 until 1.19.6 and 1.20.3, Challenge resources under acme.cert-manager.io can be created directly by namespace…
When was the CVE record for CVE-2026-62290 published?
The CVE record for CVE-2026-62290 was published on July 16, 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 July 30, 2026; the record at its source may have been updated since.
Is CVE-2026-62290 actively exploited?
CVE-2026-62290 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62290?
CVE-2026-62290 has a CVSS base score of 7.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62290?
A fix for CVE-2026-62290 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62290 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-62290

Explore →

Is Your Infrastructure Affected by CVE-2026-62290?

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