CVE-2026-86189: WWBN AVideo vulnerability
CVE-2026-86189 affects WWBN AVideo. The published description indicates a remote or untrusted-network exploitation path.
What happened
php that allows unauthenticated attackers to write files to arbitrary locations by supplying a caller-chosen path in the avideoRelativePath parameter. A security weakness in WWBN AVideo is being tracked as CVE-2026-86189. CVE-2026-86189 affects WWBN AVideo.
CVE-2026-86189 currently carries a CRITICAL 9 8 severity signal in the retained vulnerability data. Attackers can replay any previously issued ciphertext as a notifyCode token, which is decrypted but never validated, to bypass authentication and write files to the application root and subdirect. WWBN AVideo contains a path traversal vulnerability in notify.
A path-traversal weakness can allow crafted input to make an application reach files or directories outside the location it was supposed to access. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of WWBN AVideo becomes part of the attack condition. The published description indicates a remote or untrusted-network exploitation path.
The flaw is described as a path traversal vulnerability.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
php that allows unauthenticated attackers to write files to arbitrary locations by supplying a caller-chosen path in the avideoRelativePath parameter.
Attackers can replay any previously issued ciphertext as a notifyCode token, which is decrypted but never validated, to bypass authentication and write files to the application root and subdirect
CVE-2026-86189 currently carries a CRITICAL 9.8 severity signal in the retained vulnerability data.
CVE-2026-86189: WWBN AVideo contains a path traversal vulnerability in notify.ffmpeg.json.php that allows unauthenticated attackers to write files to arbitrary locati
A security weakness in WWBN AVideo is being tracked as CVE-2026-86189. The flaw is described as a path traversal vulnerability. A path-traversal weakness can allow crafted input to make an application reach files or directories outside the location it was supposed to access. The available description indicates that the vulnerable path can be reached remotely or from an untrusted network, so the exposure of WWBN AVideo becomes part of the attack condition. php that allows unauthenticated attackers to write files to arbitrary locations by supplying a caller-chosen path in the avideoRelativePath parameter. Attackers can replay any previously issued ciphertext as a notifyCode token, which is decrypted but never validated, to bypass authentication and write files to the application root and subdirect.
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Required condition: an affected WWBN AVideo instance is reachable from a network position available to the attacker.
attacker-controlled network input reaches the vulnerable function on the affected WWBN AVideo service.
the reported path traversal is triggered inside WWBN AVideo, crossing the security boundary described by the advisory or vulnerability record.
successful exploitation can bypass the authentication boundary described in the reporting and reach functionality that should require trusted access.
Identify remotely reachable WWBN AVideo; remove unnecessary exposure; apply the vendor fix or mitigation; then review service, network and identity telemetry for exploitation attempts or unexpected follow-on activity.
Why this matters to you
CVE-2026-86189 matters because the practical risk is not the score alone — it is whether WWBN AVideo exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is CRITICAL 9.8. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of WWBN AVideo.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for WWBN AVideo.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.