CVE-2026-133115: Redmine 6.1.0 before 6.1.6 and 7.0.0 before 7.0.3 OAuth Scope Bypass in Project Creation
Redmine 6.1.0 before 6.1.6 and 7.0.0 before 7.0.3 contains an incorrect authorization vulnerability that lets OAuth clients exceed token scope during project creation. A client with only project-creation scope can set ispublic, enabledmodulenames and inheritmembers, making projects public and granting parent-project members subproject access.
Frequently Asked Questions
Which deployments are affected?
Redmine versions 6.1.0 through 6.1.5 and 7.0.0 through 7.0.2 are affected. The issue applies where OAuth clients can create projects using tokens limited to project-creation scope.
What access does an attacker need?
An attacker needs an OAuth client token with permission to create projects. No user interaction is required, but the token must have project-creation scope.
What can a scoped OAuth client do beyond its intended permissions?
It can set is_public, enabled_module_names, and inherit_members when creating a project. This can expose a new project publicly and grant parent-project members access to the created subproject.
How can I determine whether this has been exploited?
Review projects created through OAuth for unexpected public visibility, enabled modules, or inherited membership settings. Pay particular attention to subprojects whose parent-project members received access unexpectedly.