CVE-2026-82470

MEDIUMPre-NVD 5.45.4
EchelonGraph scoreMEDIUM confidence

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

Score 5.4 from GitHub Security Advisory published 2026-08-29. A secondary CVSS source baseline 5.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 week
5.4EG
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.4%CVSS: 5.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Rodauth before 2.47.0 contains a time-based one-time password reuse vulnerability in the otp feature that fails to track the last accepted code timestamp. Attackers who observe a valid TOTP code can replay it during the drift window to bypass the second authentication factor.

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

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity54% × 45%
The EG Score, 5.4 of 10.
Exploitation0.4% × 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.4%
EPSS %ILE
33rd
KEV
Not listed

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.

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

August 29, 2026

Last Modified

September 11, 2026

Advisory Details (4)

Auto-updated Aug 29, 2026
Patch available. Sources: github, github_commit.
Web page

Rodauth before 2.47.0 TOTP Code Reuse via Drift Window | Advisories | VulnCheck

https://www.vulncheck.com/advisories/rodauth-before-2.47.0-totp-code-reuse-via-drift-window
Web page

GitHub - jeremyevans/rodauth: Ruby's Most Advanced Authentication Framework · GitHub

https://github.com/jeremyevans/rodauth
GitHub advisoryMentions a patch (unverified)

otp feature allows replay of otp code during drift window · Advisory · jeremyevans/rodauth · GitHub

https://github.com/jeremyevans/rodauth/security/advisories/GHSA-hhvg-6qmv-58vc
GitHub commit

commit 3bfd0a11bae7 (jeremyevans/rodauth)

Fix landed in jeremyevans/rodauth commit 3bfd0a11bae7 — awaiting tagged release

https://github.com/jeremyevans/rodauth/commit/3bfd0a11bae70935b1944e71dbe787dd0c3a62ad

Vendor Advisories for CVE-2026-82470(1)

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

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
ruby-rodauth2.42.0-1 ... 2.46.0-1 (6 versions)
  • every version up to 2.47.0-1: fixed in 2.47.0-1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 83× 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 98 of 128 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. 2 repeat rows among the latest 100 are merged into the row they repeat. The 30 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-82470?
CVE-2026-82470 is a medium-severity vulnerability; its CVE record was published on August 29, 2026. Rodauth before 2.47.0 contains a time-based one-time password reuse vulnerability in the otp feature that fails to track the last accepted code timestamp. Attackers who observe a valid TOTP code can replay it during the drift window to bypass the second authentication factor.
When was CVE-2026-82470 made public?
CVE-2026-82470 was made public on August 23, 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 August 29, 2026. EchelonGraph's copy of the record carries a last-modified date of September 11, 2026; the record at its source may have been updated since.
Is CVE-2026-82470 actively exploited?
CVE-2026-82470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-82470?
CVE-2026-82470 has a CVSS base score of 5.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-82470?
A fix for CVE-2026-82470 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-82470 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-82470

Explore →

Is Your Infrastructure Affected by CVE-2026-82470?

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

Book a Demo →Browse All CVEs