Quick answers
- Is CVE-2026-77168 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77168 being exploited in the wild.
- How severe is CVE-2026-77168?
- Medium severity, with a CVSS score of 4.3, published 11 November 2026.
- Which products and versions are affected?
- Revive Adserver 6.0.8 and earlier.
- Is there a fix for CVE-2026-77168?
- Yes: fixed in Revive Adserver 6.0.9. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77168 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-77168?
- Check whether you run Revive 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.
How to fix
- Fixed in: Revive Adserver 6.0.9
Technical details
A leftover, unused state-changing handler in tracker-invocation.php accepts request parameters without CSRF token validation. An attacker can exploit this via a crafted cross-site request that executes with the victim's authenticated session credentials. The vulnerability requires victim interaction and an authenticated session; the unused handler was removed in version 6.0.9.
Affected products
- Revive Adserver 6.0.8 and earlier
Timeline
- 2026-11-11: disclosed
- 2026-11-11: patched: Fixed in version 6.0.9