CVE-2026-62232

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

Score 7.4 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-17. A secondary CVSS source baseline 7.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-45120 (ENISA EUVD) · GHSA-4m9m-rmh9-2pgf (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.4Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's CNA (VulnCheck) lists getgrav grav versions before 2.0.4 as affected, and getgrav grav versions 2.0.4 as unaffected. No release containing a fix is confirmed on record.

Grav before 2.0.4 contains a two-factor authentication bypass vulnerability in the login plugin where the regenerate2FASecret task checks only user existence, not authorization, during the pending TOTP challenge window. Attackers who know the victim's password can call this task without a CSRF nonce to overwrite the 2FA secret with an attacker-chosen value, compute a valid TOTP code, and complete authentication while reducing 2FA to password-only protection.

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
49
EG Risk 49/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
28th
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.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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, Track* at medium and Attend at high mission impact.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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (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.

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

July 17, 2026

Last Modified

October 24, 2026

Advisory Details (2)

Auto-updated Jul 17, 2026
No fix on record yet. Sources: github.
Web page

Grav < 2.0.4 2FA Bypass via Secret Regeneration | Advisories | VulnCheck

https://www.vulncheck.com/advisories/grav-2fa-bypass-via-secret-regeneration
GitHub advisoryMentions a patch (unverified)

2FA Bypass via 'login.regenerate2FASecret' - Secret Rotation During Pending Challenge · Advisory · getgrav/grav · GitHub

https://github.com/getgrav/grav/security/advisories/GHSA-7mgc-c7pq-3rr3

Vendor Advisories for CVE-2026-62232(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 10× in last 7d / 49× 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 247 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 147 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-62232?
CVE-2026-62232 is a high-severity vulnerability; its CVE record was published on July 17, 2026. Grav before 2.0.4 contains a two-factor authentication bypass vulnerability in the login plugin where the regenerate2FASecret task checks only user existence, not authorization, during the pending TOTP challenge window. Attackers who know the victim's password can call this task without a CSRF…
When was CVE-2026-62232 made public?
CVE-2026-62232 was made public on June 29, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 17, 2026. EchelonGraph's copy of the record carries a last-modified date of October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-62232 actively exploited?
CVE-2026-62232 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62232?
CVE-2026-62232 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62232?
No fix for CVE-2026-62232 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's CNA (VulnCheck) lists getgrav grav versions before 2.0.4 as affected, and getgrav grav versions 2.0.4 as unaffected. No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-62232 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-62232?

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