Quick answers
- Is CVE-2026-104464 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-104464 being exploited in the wild.
- How severe is CVE-2026-104464?
- High severity, with a CVSS score of 8.6, published 2 October 2026.
- Which products and versions are affected?
- YesWiki before 4.6.7.
- Is there a fix for CVE-2026-104464?
- No fixed version is recorded yet. Restrict access to pages containing Bazar elements or disable the abonnements sync action in ActivityPubService until the patched version is deployed. 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-104464 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-104464?
- 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
Restrict access to pages containing Bazar elements or disable the abonnements sync action in ActivityPubService until the patched version is deployed.
Technical details
A server-side request forgery (SSRF) vulnerability exists in BazarAction's abonnements sync branch, which passes an attacker-controlled actor URL directly to HTTP requests without validation. The flaw is reachable via unauthenticated GET requests to pages with Bazar elements and allows attackers to chain attacker-controlled outbox first/next links across multiple fetches, with responses stored as readable entries. No ACL, CSRF, or URL scheme/IP filtering is applied in ActivityPubService::syncActorPosts.
Affected products
- YesWiki YesWiki before 4.6.7
Timeline
- 2026-10-02: disclosed
- 2026-10-02: advisory