CVE-2026-50741: Revive Adserver · Code Injection
Affects Revive AdserverSource CVE Database V5
Mentioned vulnerabilities
Not known to be exploited · CVSS 8.8 High.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 4.9% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 26 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| ReviveAdserver | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, monitor for updates from the vendor. No temporary or official fixes are currently documented.
Description
Bypass to the fix for CVE-2026-34916. Variants of such vectors have been also reported by phucrio and offsetmd. The fix can be bypassed either by sending a disallowed but otherwise valid plugin identifier as `type`, or using the `ox.setChannelTargeting` XML-RPC API method.