Wanderer: SSRF Vulnerability in /api/v1/trail/download - Unvalidated URL Leads to Internal Network Access
Wanderer v0.19.3 and earlier are affected when PUBLIC_PRIVATE_INSTANCE is not set to true, which lets unauthenticated users reach the endpoint. Fixed in 0.20.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.20.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 0.20.0.
- 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? →
- 27/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, has a server-side request forgery flaw in its trail download endpoint, which fetches attacker-supplied URLs without validation when PUBLIC_PRIVATE_INSTANCE is not set to true. An attacker can remotely, without logging in, use it to read data returned by internal services and cloud metadata addresses, perform internal network reconnaissance, or cause a denial of service.
Read the original description
Wanderer is a self-hosted trail database for saving and sharing adventures. Prior to 0.20.0, when PUBLIC_PRIVATE_INSTANCE is not set to true, the unauthenticated POST /api/v1/trail/download handler passes the attacker-controlled JSON url field directly to event.fetch() and returns the fetched response. This allows requests to internal services such as db:8090 and search:7700, cloud metadata addresses, and other network destinations, exposing returned data and permitting internal network reconnaissance or denial of service. This issue is fixed in version 0.20.0.
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
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 0.20.0.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- open-wanderer wanderer
fixed in 0.20.0
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-71495
Is CVE-2026-71495 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 /api/v1/trail/download endpoint accepts a URL without validating it, so the server can be made to send requests to internal services and cloud metadata endpoints and return the responses to the requester.Source: github.com
Which versions are affected by CVE-2026-71495?
wanderer: before 0.20.0.Source: cve.now feed data
Am I affected, and how do I check?
Wanderer v0.19.3 and earlier are affected, but only when PUBLIC_PRIVATE_INSTANCE is not set to true, since that setting leaves the endpoint reachable by unauthenticated users. Check the installed version and the PUBLIC_PRIVATE_INSTANCE setting.Source: github.com
How do I fix CVE-2026-71495?
Upgrade to Wanderer v0.20.0 or later, which contains the fix.Source: github.com