CVE-2026-82470 jeremyevans CVE debrief

Who should care

Defenders responsible for Rodauth deployments should assess exposure and verify the version in use. This vulnerability may impact systems relying on Rodauth for authentication. Operators of Rodauth-protected systems should review authentication factor configurations to ensure secure TOTP code usage. Security teams should monitor for potential TOTP code reuse attempts and review compensating controls for exposed systems while remediation is scheduled and

Why it matters

CVE-2026-82470 is a medium-severity vulnerability in Rodauth that allows TOTP code reuse, potentially bypassing the second authentication factor. Defenders should verify the Rodauth version and upgrade to 2.47.0 or later to address this vulnerability.

• Potential bypass of second authentication factor
• Possible unauthorized access to Rodauth-protected systems
• Need to verify Rodauth version and upgrade to 2.47.0 or later
• Potential for TOTP code reuse during drift window

Technical summary

The Rodauth library before version 2.47.0 contains a time-based one-time password reuse vulnerability in the otp feature. This vulnerability fails to track the last accepted code timestamp, allowing attackers who observe a valid TOTP code to replay it during the drift window to bypass the second authentication factor. The vulnerability has a CVSS score of 5.1 and is classified as medium-severity. Defenders should prioritize verifying the version of Rodauth in use and upgrading to version 2.47.0 or later to address this vulnerability.

Defensive priority

Defenders should prioritize verifying the version of Rodauth in use and upgrading to version 2.47.0 or later to address this vulnerability.

Recommended defensive actions

• Verify the version of Rodauth in use and upgrade to version 2.47.0 or later
• Review authentication factor configurations to ensure secure TOTP code usage
• Monitor for potential TOTP code reuse attempts
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and CVSS score. However, the exact scope of affected deployments and the number of potential victims are unknown.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.