Quick answers
- Is CVE-2026-107247 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107247 being exploited in the wild.
- How severe is CVE-2026-107247?
- High severity, with a CVSS score of 8.1, published 11 November 2026.
- Which products and versions are affected?
- Revive Adserver 6.0.0 through 6.0.8.
- Is there a fix for CVE-2026-107247?
- 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-107247 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-107247?
- 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
The vulnerability is an authorization bypass caused by a parameter precedence regression in global input registration. Authenticated users can supply object identifiers in the GET query string while submitting different identifiers in the POST body; permission checks use the GET value but subsequent operations use the POST value, causing the application to operate on unintended objects. This affects cross-agency resource access and modification in versions 6.0.0–6.0.8.
Affected products
- Revive Adserver 6.0.0 through 6.0.8
Timeline
- 2026-11-11: disclosed