Quick answers
- Is CVE-2026-50741 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50741 being exploited in the wild.
- How severe is CVE-2026-50741?
- High severity, with a CVSS score of 8.8, published 26 June 2026.
- Which products and versions are affected?
- Revive-Adserver Adserver <= 6.0.7.
- Is there a fix for CVE-2026-50741?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-50741 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-50741?
- Check whether you run Revive-Adserver Adserver at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Revive Adserver (up to version 6.0.7) is vulnerable to a bypass of the fix for CVE-2026-34916, leading to improper control of generation of code (CWE-94). The vulnerability exists because the previous security patch can be circumvented by providing a disallowed but valid plugin identifier as the 'type' parameter, or by utilizing the 'ox.setChannelTargeting' XML-RPC API method. An attacker with low-privileged network access can exploit this to achieve remote code execution (RCE). The vulnerability was reported via HackerOne and affects versions up to and including 6.0.7.
Affected products
- Revive Adserver <= 6.0.7
Timeline
- 2026-06-26: advisory: NVD publication date