Quick answers
- Is CVE-2026-82469 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82469 being exploited in the wild.
- How severe is CVE-2026-82469?
- Medium severity, with a CVSS score of 5.4, published 29 August 2026.
- Which products and versions are affected?
- Jeremy Evans Rodauth before 2.47.0.
- Is there a fix for CVE-2026-82469?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-82469 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82469?
- Check whether you run Jeremy Evans Rodauth at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the jwt_refresh route where new JWT access tokens are issued without proper validation of the HTTP method. An attacker can present an access token to the refresh route via GET or other non-POST methods to obtain a new valid access token. The root cause is insufficient enforcement of POST-method requirements and missing validation that a valid refresh token must be provided. The attack requires only network access to the vulnerable endpoint and possession of a temporary access token. The fix, available in version 2.47.0 and later, removes the Authorization response header from responses to non-POST requests or requests that do not accept JSON, preventing token issuance in these cases.
Affected products
- Jeremy Evans Rodauth before 2.47.0
Timeline
- 2026-08-29: disclosed