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.
CVE-2026-82470
MEDIUMPre-NVD 5.45.4
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 5.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: secondary
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 5.4Exploit: None knownExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(low)
- EG Risk
- 29(Track)EG Risk 29/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 computedSeverity54% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
August 29, 2026
Last Modified
August 29, 2026
Advisory Details (4)
Auto-updated Aug 29, 2026Patch 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-windowgeneric
GitHub - jeremyevans/rodauth: Ruby's Most Advanced Authentication Framework · GitHub
https://github.com/jeremyevans/rodauthgithub 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-58vcgithub_commit
commit 3bfd0a11bae7 (jeremyevans/rodauth)
Fix landed in jeremyevans/rodauth commit 3bfd0a11bae7 — awaiting tagged release
https://github.com/jeremyevans/rodauth/commit/3bfd0a11bae70935b1944e71dbe787dd0c3a62adVendor 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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 3× in last 7d / 3× 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.
- 2026-08-29 17:28 UTCEG score recompute
- 2026-08-29 16:41 UTCEG score recompute
- 2026-08-29 16:37 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-294
- CVE-2021-22640NVD 7.5EG 9.8CRITICAL
- CVE-2022-29334EG 9.8CRITICAL
- CVE-2022-22806EG 9.8EPSS p96CRITICAL
- CVE-2020-35551EG 9.8CRITICAL
- CVE-2018-19025EG 9.8CRITICAL
- CVE-2018-17932EG 9.8CRITICAL
- CVE-2019-18226EG 9.8CRITICAL
- CVE-2018-7790EG 9.8CRITICAL
- CVE-2017-3191EG 9.8EPSS p96CRITICAL
- CVE-2017-6034EG 9.8EPSS p91CRITICAL
Frequently asked(4)
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. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-82470?
CVE-2026-82470 has a CVSS v3 base score of 5.4 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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
Explore the affected products and dependency analysis for CVE-2026-82470
Is Your Infrastructure Affected by CVE-2026-82470?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.