CVE-2026-54509

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 77% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.5Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

TREK is a collaborative travel planner. From 3.0.0 until 3.1.0, the GET /api/journeys/:id/share-link route in server/src/routes/journey.ts returns the result of getJourneyShareLink() from server/src/services/journeyShareService.ts without checking whether the authenticated requester can access the journey. Any ordinary authenticated user can enumerate sequential journey IDs and retrieve tokens from journey_share_tokens for another user's journey. The token grants unauthenticated access through GET /api/public/journey/:token to the shared journey's entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers. This issue is fixed in version 3.1.0.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
45(Track)
EG Risk 45/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
23%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 21, 2026

Advisory Details (3)

Auto-updated Aug 20, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
github_release Patch Available

v3.1.0

Patch available: liketrek/TREK v3.1.0

https://github.com/liketrek/TREK/releases/tag/v3.1.0
github_pr Patch Available

Release 3.1.0

Patch available: liketrek/TREK v3.1.0 (PR #1185 merged 2026-06-16)

https://github.com/liketrek/TREK/pull/1185
github Patch Available🟡 PoC Available

IDOR: any authenticated user can read another user's journey share token (full journey leak) · Advisory · liketrek/TREK · GitHub

https://github.com/liketrek/TREK/security/advisories/GHSA-mx6m-qxv8-w624

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 01:22 UTCEPSS rescore
  2. 2026-08-29 05:41 UTCEG score recompute
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-28 03:38 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 01:35 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-25 23:32 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 21:29 UTCEG score recompute
  11. 2026-08-23 19:26 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 17:24 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 15:21 UTCEG score recompute
  16. 2026-08-21 15:10 UTCEG score recompute
  17. 2026-08-20 22:24 UTCEG score recompute
  18. 2026-08-20 21:57 UTCEG score recompute
  19. 2026-08-20 21:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54509?
CVE-2026-54509 is a medium vulnerability published on August 20, 2026. TREK is a collaborative travel planner. From 3.0.0 until 3.1.0, the GET /api/journeys/:id/share-link route in server/src/routes/journey.ts returns the result of getJourneyShareLink() from server/src/services/journeyShareService.ts without checking whether the authenticated requester can access the…
When was CVE-2026-54509 disclosed?
CVE-2026-54509 was first published in the National Vulnerability Database on August 20, 2026, with the most recent update on August 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54509 actively exploited?
CVE-2026-54509 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.4% of all scored CVEs.
What is the CVSS score of CVE-2026-54509?
CVE-2026-54509 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-54509?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54509, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-54509

Explore →

Is Your Infrastructure Affected by CVE-2026-54509?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs