CVE-2026-82470

MEDIUMPre-NVD 5.45.4—
EchelonGraph scoreHIGH confidence

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, ghsa, secondary
Trending — 3 sources updated this week
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

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

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.4(high)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
15%
KEV
Not listed

Published

August 29, 2026

Last Modified

September 11, 2026

Advisory Details (4)

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

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
generic

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

https://github.com/jeremyevans/rodauth
github Patch Available

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 rangeFixed inDependents
ruby-rodauth2.42.0-1 ... 2.46.0-1 (6 versions)——

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-19 05:13 UTCEG score recompute
  2. 2026-09-19 05:13 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 06:56 UTCEG score recompute
  5. 2026-09-18 06:56 UTCGHSA enrichment
  6. 2026-09-17 08:38 UTCEG score recompute
  7. 2026-09-17 08:38 UTCGHSA enrichment
  8. 2026-09-16 14:08 UTCEPSS rescore
  9. 2026-09-16 10:20 UTCEG score recompute
  10. 2026-09-16 10:20 UTCGHSA enrichment
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-15 12:01 UTCEG score recompute
  13. 2026-09-15 12:01 UTCGHSA enrichment
  14. 2026-09-15 03:12 UTCEPSS rescore
  15. 2026-09-15 03:12 UTCEPSS rescore
  16. 2026-09-14 13:43 UTCEG score recompute
  17. 2026-09-14 13:43 UTCGHSA enrichment
  18. 2026-09-13 15:11 UTCGHSA enrichment
  19. 2026-09-12 16:53 UTCEG score recompute
  20. 2026-09-12 16:53 UTCGHSA enrichment
  21. 2026-09-11 18:35 UTCEG score recompute
  22. 2026-09-11 18:35 UTCGHSA enrichment
  23. 2026-09-11 14:53 UTCEPSS rescore
  24. 2026-09-11 14:53 UTCEPSS rescore
  25. 2026-09-11 01:01 UTCEG score recompute
Show 38 more
  1. 2026-09-11 01:01 UTCGHSA enrichment
  2. 2026-09-10 02:43 UTCGHSA enrichment
  3. 2026-09-09 04:24 UTCEG score recompute
  4. 2026-09-09 04:23 UTCGHSA enrichment
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-08 06:05 UTCEG score recompute
  7. 2026-09-08 06:05 UTCGHSA enrichment
  8. 2026-09-07 07:45 UTCEG score recompute
  9. 2026-09-07 07:45 UTCGHSA enrichment
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-06 09:24 UTCEG score recompute
  12. 2026-09-06 09:24 UTCGHSA enrichment
  13. 2026-09-05 15:31 UTCEPSS rescore
  14. 2026-09-05 11:07 UTCEG score recompute
  15. 2026-09-05 11:07 UTCGHSA enrichment
  16. 2026-09-04 12:46 UTCGHSA enrichment
  17. 2026-09-03 14:26 UTCGHSA enrichment
  18. 2026-09-02 16:07 UTCEG score recompute
  19. 2026-09-02 16:07 UTCGHSA enrichment
  20. 2026-09-02 14:12 UTCEPSS rescore
  21. 2026-09-01 17:49 UTCEG score recompute
  22. 2026-09-01 17:49 UTCGHSA enrichment
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-09-01 04:40 UTCEPSS rescore
  26. 2026-08-31 19:29 UTCEG score recompute
  27. 2026-08-31 19:29 UTCGHSA enrichment
  28. 2026-08-31 18:33 UTCEG score recompute
  29. 2026-08-31 18:33 UTCGHSA enrichment
  30. 2026-08-31 14:07 UTCEG score recompute
  31. 2026-08-31 14:07 UTCGHSA enrichment
  32. 2026-08-30 19:18 UTCEPSS rescore
  33. 2026-08-30 19:17 UTCEPSS rescore
  34. 2026-08-30 15:46 UTCEG score recompute
  35. 2026-08-30 15:46 UTCGHSA enrichment
  36. 2026-08-29 17:28 UTCEG score recompute
  37. 2026-08-29 16:41 UTCEG score recompute
  38. 2026-08-29 16:37 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82470?
CVE-2026-82470 is a medium vulnerability 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 disclosed?
CVE-2026-82470 was first published in the National Vulnerability Database on August 29, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82470 actively exploited?
CVE-2026-82470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-82470?
CVE-2026-82470 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-82470?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82470, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs