Quick answers
- Is CVE-2026-34736 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34736 being exploited in the wild.
- How severe is CVE-2026-34736?
- Medium severity, with a CVSS score of 5.3, published 2 April 2026.
- Which products and versions are affected?
- Open edX Platform >= maple, < ulmo.
- Is there a fix for CVE-2026-34736?
- 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-34736 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-34736?
- Check whether you run Open edX Platform 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
An authentication bypass vulnerability exists in the Open edX Platform due to the exposure of the 'activation_key' field in the REST API response at /api/user/v1/accounts/. While the OAuth2 password grant intentionally issues tokens to inactive users, the inclusion of the activation key in the UserReadOnlySerializer allows an attacker to obtain the key without email access. An attacker can register an account, obtain an OAuth2 token, retrieve their own activation key via the API, and then programmatically trigger the activation endpoint. This issue affects versions from the 'maple' release up to 'ulmo', where it has been patched by removing the key from the API response.
Affected products
- Open edX Open edX Platform >= maple, < ulmo
Timeline
- 2026-03-30: advisory: GitHub Security Advisory published
- 2026-04-02: disclosed: CVE published to NVD