CVE-2026-68486 · Package
NO FIX YET · SEE WHAT TO DO
Revive Adserver 6.0.8 and earlier lack ownership checks when linking campaigns to zones, so an authenticated manager or trafficker can link another agency's campaign to their own zone. The linked-campaign listing can then reveal that foreign campaign's name, type and identifier.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Teams that run self-hosted Revive Adserver 6.0.8 or earlier with multiple agencies or advertisers sharing one instance. The exposure needs an authenticated manager or a trafficker with zone-linking permissions, so single-tenant installs with trusted users carry less risk.
Not affected if single-agency-install, version-6.0.9-or-later
Who cares php, revive-adserver, self-hosted
6.0.8 range in the sources.6.0.9, which validates campaign ownership in the affected operations.An authorization bypass in campaign-zone linking in Revive Adserver 6.0.8 and earlier allows an authenticated manager, or a trafficker with zone-linking permissions, to associate another agency's campaign with their own zone. Campaign ownership checks are missing from the bulk-linking and single-link operations in zone-include.php and the XML-RPC campaign-linking method. Although agency filtering prevents foreign banners from being linked, the unauthorized association can expose the foreign campaign's name, type and identifier in the linked-campaign listing. The issue is fixed in Revive Adserver 6.0.9 by validating campaign ownership in the affected operations.
This page as .md · .json · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.