Quick answers
- Is CVE-2026-34460 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34460 being exploited in the wild.
- How severe is CVE-2026-34460?
- Medium severity, with a CVSS score of 5.4, published 2 June 2026.
- Which products and versions are affected?
- NamelessMC <= 2.2.4.
- Is there a fix for CVE-2026-34460?
- A patch was published on 2026-06-02: Fix released in version 2.2.5 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-34460 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34460?
- Check whether you run NamelessMC 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
NamelessMC fails to validate the OAuth 'state' parameter server-side before exchanging the authorization code for an access token. The vulnerability exists in the OAuth callback handling logic within 'core/classes/Misc/NamelessOAuth.php' and 'modules/Core/pages/oauth.php'. An attacker can initiate an OAuth flow, capture their own valid callback URL, and trick a victim into navigating to it. Because the application does not verify that the state parameter matches the victim's session, it processes the attacker's authorization code, effectively logging the victim into the attacker's account. This is a classic OAuth login CSRF (session swapping) attack. The issue is resolved in version 2.2.5 by implementing proper state generation and verification.
Affected products
- NamelessMC NamelessMC <= 2.2.4
Timeline
- 2026-05-31: advisory: GitHub Security Advisory published by maintainers
- 2026-06-02: disclosed: CVE published to NVD
- 2026-06-02: patched: Fix released in version 2.2.5