Quick answers
- Is CVE-2026-34913 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34913 being exploited in the wild.
- How severe is CVE-2026-34913?
- Medium severity, with a CVSS score of 4.3, published 23 June 2026.
- Which products and versions are affected?
- Revive-Adserver Adserver 6.0.6 and earlier.
- Is there a fix for CVE-2026-34913?
- 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-34913 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34913?
- 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
An improper access control vulnerability (CWE-284) exists in the 'campaign-trackers.php' script of Revive Adserver. The application fails to perform adequate ownership validation when a user attempts to link a tracker to a campaign. An authenticated attacker with low privileges can exploit this by submitting requests that associate their trackers with campaigns belonging to different advertisers or managers on the same instance. This results in unauthorized modification of campaign metadata and inconsistent ownership relationships. The issue is resolved in versions following 6.0.6 by implementing strict ownership validation to ensure campaigns only link to trackers owned by the same advertiser.
Affected products
- Revive Adserver 6.0.6 and earlier
Timeline
- 2026-06-23: disclosed
- 2026-06-23: advisory