Wanderer: Unauthenticated Access to Private Trails and Comments via ActivityPub Endpoints
Affects Wanderer instances before 0.19.3 that expose the unauthenticated ActivityPub trail and comment endpoints. Fixed in 0.19.3.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.19.3
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.19.3.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 25/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Wanderer, a self-hosted trail database for saving and sharing adventures, can be attacked remotely without logging in. An unauthenticated attacker who can enumerate or guess record IDs through its ActivityPub endpoints can retrieve private trail names, descriptions, GPS coordinates, GPX file and photo URLs, and comments.
Read the original description
Wanderer is a self-hosted trail database for saving and sharing adventures. Prior to 0.19.3, the unauthenticated GET /activitypub/trail/{id} and GET /activitypub/comment/{id} endpoints call ActivitypubTrail() and ActivitypubComment() to return full trail and comment records without applying the PocketBase collection view rules. An attacker who can enumerate or guess record IDs can retrieve private trail names, descriptions, GPS coordinates, GPX file URLs, photo URLs, and comments. This issue is fixed in version 0.19.3.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 30 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.19.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- open-wanderer wanderer
fixed in 0.19.3
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62344
Is CVE-2026-62344 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The ActivityPub trail and comment endpoints return full trail and comment records to callers without any authorization check. This lets someone read the full content of private trails and comments, including GPS tracks, GPX file URLs and photos.Source: github.com, github.com
Which versions are affected by CVE-2026-62344?
wanderer: before 0.19.3.Source: cve.now feed data
Am I affected, and how do I check?
Wanderer versions before 0.19.3 are in the affected range, and the bug applies where the unauthenticated ActivityPub trail and comment endpoints are exposed. To check, compare the installed Wanderer version with 0.19.3.Source: github.com, github.com
How do I fix CVE-2026-62344?
Upgrade Wanderer to 0.19.3, which contains the security fixes for this issue.Source: github.com, github.com