Quick answers
- Is CVE-2026-116208 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116208 being exploited in the wild.
- How severe is CVE-2026-116208?
- High severity, with a CVSS score of 8.1, published 25 October 2026.
- Which products and versions are affected?
- YesWiki 4.6.2 to before 4.7.0.
- Is there a fix for CVE-2026-116208?
- Yes: fixed in 4.7.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116208 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116208?
- Check whether you run YesWiki 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: 4.7.0
Technical details
The ActivityPubService::syncActorPosts handler processes remote Create, Update, and Delete activities without authorization checks, while the inbox handler enforces assertOwns() and sameHost() guards. An attacker can craft a malicious outbox containing cross-actor activities targeting third-party entries; when an admin syncs with the attacker's actor, these activities execute without validation. The vulnerability affects Delete (no assertOwns check), Create (no sameHost check), Update (no assertOwns check), and garbage-collection logic that mass-deletes entries without per-actor verification.
Affected products
- YesWiki YesWiki 4.6.2 to before 4.7.0
Timeline
- 2026-10-25: disclosed
- 2026-10-09: advisory: GitHub security advisory GHSA-cr64-h6xp-9g2j published