dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2026-11441

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 identified in theonedev onedev up to 15.0.5. This vulnerability affects the function canAccessIssue of the file /issues/ of the component Pull Request Handler. Such manipulation of the argument issue leads to improper authorization. It is possible to launch the attack remotely. Upgrading to version 15.0.6 is able to resolve this issue. It is advisable 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

OneDev up to version 15.0.5 contains an improper authorization vulnerability in the Pull Request Handler component. The canAccessIssue function in /issues/ fails to properly validate authorization, allowing remote attackers to access issues they should not have permission to view.

MitigationUpgrade OneDev to version 15.0.6 or later to remediate this authorization bypass in the Pull Request Handler's issue access controls.

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 startup logs for the installed OneDev version number
    Affected if The installed version is lower than 15.0.6
  2. Confirm the Pull Request Handler component is enabled
    Check OneDev's plugin or feature configuration to verify the Pull Request Handler module is active
    Affected if Pull Request Handler is enabled and the version is below 15.0.6
  3. Verify network exposure of the issues endpoint
    Determine if the /issues/ endpoint is accessible over the network by reviewing web server configuration or firewall rules
    Affected if The /issues/ endpoint is externally accessible and the OneDev version is below 15.0.6
  4. Review access control configuration for issues
    Inspect OneDev's authorization settings for the issues module to confirm whether unauthenticated or low-privilege access is permitted
    Affected if Anonymous or unauthorized users can access issue data via the /issues/ endpoint

You are affected if OneDev version is below 15.0.6, the Pull Request Handler is enabled, and the /issues/ endpoint is accessible without proper authorization enforcement.

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 or later to remediate this authorization bypass in the Pull Request Handler's issue access controls.

Recommended fix High confidence

onedev version 15.0.6

  1. Check current onedev version to confirm it is 15.0.5 or earlier
  2. Stop the onedev service
  3. Create a backup of the onedev database and configuration files
  4. Download onedev version 15.0.6 from the official repository (https://code.onedev.io/onedev)
  5. Install or apply the version 15.0.6 upgrade following standard onedev upgrade procedures
  6. Start the onedev service
  7. Verify the upgrade was successful by checking the version number and testing the affected /issues/ endpoint
Caveat Patch releases typically have minimal breaking changes; review release notes for any migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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