# CVE-2026-50739: Missing authorization in Adserver

> Low-privileged users can improperly link their trackers to campaigns owned by other managers, violating ownership controls in Revive Adserver.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-v78r-pfp2-f4c7

## What is CVE-2026-50739?

CVE-2026-50739 is a medium-severity missing authorization vulnerability in Revive-Adserver Revive Adserver, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A bypass for CVE‑2026‑34913 exists with proper ownership validation that had not been applied to the reverse operation of linking campaigns and trackers through the `tracker-campaigns.php` script in Revive Adserver 6.0.7 and earlier. As a result, a low‑privileged user could link their trackers to campaigns owned by other managers on the same instance, leading to inconsistent ownership relationships.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Revive-Adserver Revive Adserver.

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

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

## Is CVE-2026-50739 being exploited?

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

## Other vulnerabilities in Revive-Adserver Revive Adserver

- [CVE-2016-9124](https://insights.sbomify.com/CVE-2016-9124/): Security feature bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2016-9125](https://insights.sbomify.com/CVE-2016-9125/): Auth bypass in Revive Adserver All versions before 3.2.3 (critical 9.8)
- [CVE-2017-5830](https://insights.sbomify.com/CVE-2017-5830/): Deserialization in n/a (critical 9.8)
- [CVE-2016-9470](https://insights.sbomify.com/CVE-2016-9470/): Other in Revive Adserver All versions before 3.2.5 and 4.0.0 (critical 9.0)
- [CVE-2026-50741](https://insights.sbomify.com/CVE-2026-50741/): Code injection in Adserver (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50739 is a medium-severity missing authorization vulnerability in Revive-Adserver Revive Adserver, published on 26 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50739 in the wild and no public exploit code.

Affected product: Revive-Adserver Revive Adserver. 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-50739/ (Markdown: https://insights.sbomify.com/CVE-2026-50739/index.md)
```

## Sources

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

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