CVE-2026-41056
Credentialed cross-origin data exposure via misconfigured CORS in WWBN AVideo <= 29.0.
Is CVE-2026-41056 being exploited?
Not confirmed. CVE-2026-41056 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-41056?
CVE-2026-41056 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41056?
Yes. A fix has been recorded for CVE-2026-41056. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41056 affect?
CVE-2026-41056 affects WWBN AVideo <= 29.0, plugin/API/get.json.php, plugin/API/set.json.php. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41056?
Apply fix CAF705F; disable allowAll; enforce strict Origin/CORS.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Exposed via credentialed CORS: attacker reads PII and livestream keys, can perform privileged actions.
Immediate action required
- affected<= 29.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.