PatchTheCVECVE-2023-31580: light-oauth2 before version 2.1.27 obtains the public key without any verification
CVE-2023-31580 is a medium-severity flaw (CVSS 5.9) affecting light-oauth2. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
light-oauth2 before version 2.1.27 obtains the public key without any verification. This could allow attackers to authenticate to the application with a crafted JWT token.
Why this priority
- Public exploit reference
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 5.9 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.7% (top 47%) |
| CISA exploited list | No |
| Weakness | CWE-295 |
| Published | 2023-10-25 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2023-31580?
light-oauth2: upgrade to 2.1.27. Exact commands for each OS are on this page.
Is CVE-2023-31580 being exploited?
CVE-2023-31580 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2023-31580 affect?
CVE-2023-31580 affects light-oauth2. Severity is medium (CVSS 5.9). light-oauth2 before version 2.1.27 obtains the public key without any verification. This could allow attackers to authenticate to the application with a crafted JWT token.
How urgent is CVE-2023-31580?
Priority 44/100. Public exploit reference; Remotely exploitable, no login, no user action