Is CVE-2026-71495 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-71495 being exploited in the wild.

How severe is CVE-2026-71495?

Critical severity, with a CVSS score of 10, published 6 November 2026.

Which products and versions are affected?

Open-Wanderer Wanderer before 0.20.0.

How is CVE-2026-71495 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-71495?

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.

CVE-2026-71495: Wanderer SSRF in trail download endpoint

CVE-2026-71495 · Severity: critical · CVSS 10 · Published 2026-11-06

Wanderer is a self-hosted adventure trail database. When not configured as a private instance, an unauthenticated attacker can exploit a server-side request forgery (SSRF) vulnerability in the trail download endpoint to access internal services, cloud metadata endpoints, and perform network reconnaissance or denial of service attacks.

Technologies: Open-Wanderer Wanderer. Vendors: Open-Wanderer.

Quick answers

Is CVE-2026-71495 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-71495 being exploited in the wild.
How severe is CVE-2026-71495?: Critical severity, with a CVSS score of 10, published 6 November 2026.
Which products and versions are affected?: Open-Wanderer Wanderer before 0.20.0.
Is there a fix for CVE-2026-71495?: Yes: fixed in 0.20.0. Until then: Enable the PUBLIC_PRIVATE_INSTANCE configuration setting to require authentication for API access. This prevents unauthenticated requests from reaching the vulnerable endpoint. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-71495 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-71495?: 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.20.0

Enable the PUBLIC_PRIVATE_INSTANCE configuration setting to require authentication for API access. This prevents unauthenticated requests from reaching the vulnerable endpoint.

Technical details

The POST /api/v1/trail/download handler accepts a user-controlled JSON url parameter and passes it directly to event.fetch() without validation when PUBLIC_PRIVATE_INSTANCE is not set to true. This allows unauthenticated requests to reach internal services (PocketBase at db:8090, Meilisearch at search:7700), cloud metadata addresses (169.254.169.254), and other network destinations. The fix adds authentication gating, protocol/hostname allowlisting, DNS-resolved IP validation against private/reserved ranges, connection pinning, and redirect rejection.

Affected products

open-wanderer Wanderer before 0.20.0

Timeline

2026-11-06: disclosed
2026-07-06: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.