Quick answers
- Is CVE-2026-116825 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116825 being exploited in the wild.
- How severe is CVE-2026-116825?
- Medium severity, with a CVSS score of 6.5, published 27 October 2026.
- Which products and versions are affected?
- YesWiki 4.6.2 before 4.7.0.
- Is there a fix for CVE-2026-116825?
- 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-116825 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-116825?
- 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
HttpSignatureService::verifySignature() validates cryptographic integrity and body digest but never compares the Date header against current server time and maintains no nonce or seen-signature tracking. An attacker with access to historical HTTP request logs (reverse proxy, WAF, shared hosting, or debug output) can replay a captured signed POST to /api/forms/{formId}/actor/inbox with no time window restriction, since ActivityPub keys persist indefinitely. The public inbox endpoint has no authentication requirement, and re-executed actions pass all ownership checks because they originate from the legitimate actor that originally signed them.
Affected products
- YesWiki YesWiki 4.6.2 before 4.7.0
Timeline
- 2026-10-12: disclosed
- 2026-10-27: advisory