dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-11438

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 has been found in theonedev onedev up to 15.0.5. Affected by this vulnerability is an unknown functionality of the file /projects. The manipulation of the argument project.forkedFromId leads to improper authorization. The attack is possible to be carried out remotely. Upgrading to version 15.0.6 addresses this issue. Upgrading the affected component is recommended.

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

Improper authorization vulnerability in OneDev's project forking functionality. The project.forkedFromId parameter can be manipulated to bypass authorization checks, potentially allowing unauthorized users to fork projects they should not have access to.

MitigationUpgrade OneDev to version 15.0.6 which contains the fix for this authorization bypass in the project forking mechanism.

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. Confirm OneDev is installed
    Identify OneDev instances running in your environment. Check for the OneDev web application accessible on its configured port (typically 6610 or 8080). Look for OneDev processes or services running on the system.
    Affected if OneDev is installed and running in your environment
  2. Determine the installed OneDev version
    Access the OneDev web interface and navigate to the administration area, or check the version using the OneDev command-line interface if available. The version is typically displayed on the login page or in the 'About' section of the admin panel.
    Affected if The installed version is prior to 15.0.6
  3. Verify the forking feature is enabled
    In the OneDev administration console, navigate to the project settings or server settings. Look for a configuration option related to 'forking' or 'allow fork' within project or server configuration settings.
    Affected if Forking is enabled in OneDev settings
  4. Check external access to the /projects endpoint
    Review network access controls and firewall rules to determine if the /projects REST API endpoint is accessible to unauthorized users or external network sources. Inspect OneDev's role-based access control settings for the projects API.
    Affected if The /projects endpoint is accessible to users without proper project forking permissions

You are affected if your OneDev version is below 15.0.6, the forking feature is enabled, and the /projects endpoint is accessible to users who should not have fork authorization.

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 in the project forking mechanism.

Recommended fix High confidence

15.0.6

  1. Back up the current onedev installation and database before proceeding with the upgrade
  2. Stop the onedev service to prevent data inconsistency during upgrade
  3. Download onedev version 15.0.6 from the official source
  4. Replace the existing onedev installation files with the new version 15.0.6
  5. Start the onedev service after the files are replaced
  6. Verify that onedev version 15.0.6 is running correctly and the /projects functionality works as expected
Caveat Review release notes for version 15.0.6 to check for any changes that may affect existing workflows or configurations

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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