Quick answers
- Is CVE-2026-34912 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-34912 being exploited in the wild.
- How severe is CVE-2026-34912?
- 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-34912?
- 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-34912 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-34912?
- 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 Revive Adserver versions 6.0.6 and earlier. The flaw is located in the zone-include.php script and the corresponding API endpoints, which fail to perform adequate ownership validation when linking banners or campaigns to a zone. An authenticated attacker with low privileges can exploit this by submitting requests to link their managed zones to assets (banners/campaigns) belonging to different manager accounts on the same instance. This results in inconsistent ownership relationships and unauthorized modification of ad delivery configurations. The issue has been addressed by adding ownership validation to ensure assets can only be linked to zones managed by the same account.
Affected products
- Revive Adserver 6.0.6 and earlier
Timeline
- 2026-06-23: advisory: NVD publication date
- 2026-06-23: disclosed: HackerOne report published