Quick answers
- Is CVE-2026-44957 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44957 being exploited in the wild.
- How severe is CVE-2026-44957?
- 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-44957?
- 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-44957 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-44957?
- 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
A missing access control check exists in the XML-RPC API of Revive Adserver versions 6.0.6 and earlier. Specifically, various 'modify' methods fail to validate whether a user has the appropriate permissions to reassign an entity to a new parent entity. This vulnerability is categorized as Improper Access Control (CWE-284). An attacker with low-privileged API access—either through a secondary vulnerability like CVE-2026-34917 or via third-party extensions—can exploit this to create inconsistent ownership relationships. The vendor has addressed this by adding validation checks for parent entities in the affected API methods.
Affected products
- Revive Adserver 6.0.6 and earlier
Timeline
- 2026-06-23: disclosed
- 2026-06-23: advisory