dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-11439

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 found in theonedev onedev up to 15.0.5. Affected by this issue is some unknown functionality of the file /projects/ of the component Parent Project Handler. The manipulation of the argument project.parentId results in improper authorization. The attack may be performed from remote. Upgrading to version 15.0.6 can resolve this issue. It is recommended to upgrade the affected component.

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 · high confidence

The OneDev project management application versions up to 15.0.5 contain an improper authorization vulnerability in the Parent Project Handler for the /projects/ endpoint. Attackers can manipulate the project.parentId argument to bypass authorization checks and potentially access or modify parent project relationships without proper permissions.

MitigationUpgrade OneDev to version 15.0.6 which contains the fix for this authorization bypass. Since this is a remote authorization flaw, limiting network exposure to the /projects/ API endpoint can provide interim defense-in-depth.

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
    Check the running onedev instance version through the web UI (typically at /~onestein or via the application startup logs) or by querying the API at /api/version
    Affected if The installed version is lower than 15.0.6 and the /projects/ endpoint is accessible over the network
  2. Confirm web interface accessibility
    Verify that the onedev web interface is reachable and the /projects/ endpoint responds to HTTP requests
    Affected if The /projects/ endpoint is publicly or internally accessible without additional authentication barriers beyond onedev's normal login
  3. Check parent project functionality usage
    Review existing projects in onedev to determine if any projects have a parent project configured (visible in project settings under 'Parent Project' field)
    Affected if The onedev instance contains projects with parent projects configured, enabling the vulnerable Parent Project Handler code path
  4. Verify authorization configuration
    Inspect the onedev authorization settings and project membership configurations to confirm whether the /projects/ endpoint accepts the project.parentId parameter
    Affected if Users with limited permissions can submit requests to /projects/ with manipulated parentId values and bypass intended authorization checks

A user is affected if onedev version is below 15.0.6, the web interface is accessible, and the vulnerable Parent Project Handler handles requests to the /projects/ endpoint with manipulable parentId parameters.

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 to version 15.0.6 which contains the fix for this authorization bypass. Since this is a remote authorization flaw, limiting network exposure to the /projects/ API endpoint can provide interim defense-in-depth.

Recommended fix High confidence

15.0.6

  1. Download OneDev version 15.0.6 from the official repository or release page
  2. Stop the currently running OneDev instance
  3. Install or replace the OneDev installation with version 15.0.6
  4. Restart the OneDev service
  5. Verify the upgrade was successful by checking the version number in the admin panel or via CLI
  6. Test that the Parent Project Handler functionality at /projects/ works correctly with proper authorization controls

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11439 — 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-11439 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