Rodauth before 2.47.0 contains an authentication bypass vulnerability in the jwt_refresh route that issues new JWT access tokens without requiring a refresh token. Attackers can present an access token to the refresh route via non-POST methods to obtain a new valid access token, enabling indefinite account access with temporary token possession.
CVE-2026-82469
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).
- Lower severity and no public exploit yet
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, 2026Rodauth before 2.47.0 Authentication Bypass via jwt_refresh | Advisories | VulnCheck
https://www.vulncheck.com/advisories/rodauth-before-2.47.0-authentication-bypass-via-jwt-refreshGitHub - jeremyevans/rodauth: Ruby's Most Advanced Authentication Framework · GitHub
https://github.com/jeremyevans/rodauthjwt_refresh route doesn't require refresh token to create new access token · Advisory · jeremyevans/rodauth · GitHub
https://github.com/jeremyevans/rodauth/security/advisories/GHSA-w4fg-qf56-62m2commit 8174690cef74 (jeremyevans/rodauth)
Fix landed in jeremyevans/rodauth commit 8174690cef74 — awaiting tagged release
https://github.com/jeremyevans/rodauth/commit/8174690cef743177111fb1d9184d129ff4700933Vendor Advisories for CVE-2026-82469(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
Frequently asked(4)
What is CVE-2026-82469?
When was CVE-2026-82469 disclosed?
What is the CVSS score of CVE-2026-82469?
How do I remediate CVE-2026-82469?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-82469
Is Your Infrastructure Affected by CVE-2026-82469?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.