Quick answers
- Is CVE-2026-62344 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-62344 being exploited in the wild.
- How severe is CVE-2026-62344?
- High severity, with a CVSS score of 7.5, published 6 November 2026.
- Which products and versions are affected?
- Open-Wanderer Wanderer before 0.19.3.
- Is there a fix for CVE-2026-62344?
- Yes: fixed in 0.19.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-62344 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-62344?
- Check whether you run Open-Wanderer Wanderer 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: 0.19.3
Technical details
The GET /activitypub/trail/{id} and GET /activitypub/comment/{id} endpoints fail to apply PocketBase collection view access controls before returning record data. An unauthenticated attacker can enumerate or predict numeric record IDs to retrieve private trails and comments without authorization. The vulnerability is an Insecure Direct Object Reference (IDOR) affecting the ActivitypubTrail() and ActivitypubComment() functions, which are now patched to enforce access control checks via CanAccessRecord().
Affected products
- open-wanderer Wanderer before 0.19.3
Timeline
- 2026-11-06: disclosed