dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-11440

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability was determined in theonedev onedev up to 15.0.5. This affects an unknown part of the file /repositories/{projectId}/default-branch of the component REST API. This manipulation of the argument project.defaultBranch causes improper authorization. It is possible to initiate the attack remotely. Upgrading to version 15.0.6 is able to mitigate this issue. Upgrading the affected component is advised.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The vulnerability exists in onedev's REST API endpoint /repositories/{projectId}/default-branch where manipulation of the project.defaultBranch argument allows improper authorization bypass. This is a remote API-level authorization flaw affecting the default branch configuration functionality.

MitigationUpgrade onedev from any version up to 15.0.5 to version 15.0.6 which contains the fix for this improper authorization vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify OneDev installation and version
    Locate the OneDev installation directory and check the version file or banner. Common locations include /opt/onedev, /home/onedev, or the service banner if running as a web application. Run: 'onedev --version' or check the about page in the web UI.
    Affected if The installed version is 15.0.5 or earlier (any version up to and including 15.0.5)
  2. Confirm REST API endpoint is accessible
    Verify that the OneDev web interface and REST API are reachable. The vulnerable endpoint is /repositories/{projectId}/default-branch. Check if the API responds to requests at your-onedev-server/api/repositories/{projectId}/default-branch
    Affected if The REST API is exposed and accepts requests without requiring elevated privileges
  3. Check for proper authorization configuration
    Review the OneDev authorization settings in the administration panel. Navigate to: Administration > Authorization > Permissions. Verify that users and groups have explicitly defined roles for repository management operations.
    Affected if Users with limited or no repository management permissions can access or manipulate the default-branch endpoint
  4. Audit recent default branch modifications
    Review OneDev audit logs or repository change history for any unauthorized modifications to default branch settings. Check the repository settings page for current default branch configuration and compare against expected values.
    Affected if Default branch settings have been changed without corresponding authorization in the audit log, or changes were made by users lacking repository admin permissions

You are affected if your OneDev installation is version 15.0.5 or earlier and the REST API endpoint /repositories/{projectId}/default-branch is accessible to users without proper repository management permissions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade onedev from any version up to 15.0.5 to version 15.0.6 which contains the fix for this improper authorization vulnerability.

Recommended fix High confidence

15.0.6

  1. 1. Back up your onedev instance data and configuration before proceeding with the upgrade
  2. 2. Stop the onedev service
  3. 3. Upgrade onedev to version 15.0.6 or later
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Restart the onedev service
  6. 6. Test the /repositories/{projectId}/default-branch REST API endpoint to confirm the improper authorization vulnerability is resolved

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11440 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11440 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data