# CVE-2026-11439: theonedev Parent Project projects improper authorization


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Jun 2026
- **Updated:** 8 Jun 2026
- **Also known as:** GHSA-q98j-2qw6-gh6w

## What is CVE-2026-11439?

CVE-2026-11439 is a medium-severity vulnerability in theonedev onedev, published on 6 Jun 2026. 

### Official description

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.

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

## Which versions are affected by CVE-2026-11439?


## How do I fix CVE-2026-11439?

No fix has been published for CVE-2026-11439 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-11439 being exploited?

There is no known exploitation of CVE-2026-11439 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-11439 and fix it if it is affected.

What it is: CVE-2026-11439 is a medium-severity vulnerability in theonedev onedev, published on 6 Jun 2026. 
Exploitation: There is no known exploitation of CVE-2026-11439 in the wild and no public exploit code.

Affected product: theonedev onedev. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-11439/ (Markdown: https://insights.sbomify.com/CVE-2026-11439/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-11439
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-11439
- OSV: https://osv.dev/vulnerability/CVE-2026-11439

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-11439/
Summaries are generated and may contain mistakes; the official description above is the record.