CVE-2026-62945

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 83% 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
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: None knownExposed: 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. Prior to 3.1.3, TREK file upload, update, and link actions accept attacker-controlled reservation_id, place_id, and assignment_id values without using findForeignLinkTarget() to verify that the referenced object belongs to the file's trip. An authenticated user with file-edit permission on any accessible trip can submit a foreign reservation identifier through POST /api/trips/:tripId/files/:id/link, POST /api/trips/:tripId/files, or PUT /api/trips/:tripId/files/:id. Subsequent reads through FILE_SELECT or getFileLinks() join the foreign reservation and return reservation_title, disclosing reservation existence and titles across private trip boundaries. This issue is fixed in version 3.1.3.

CVSS v3
4.3
EG Score
4.3(medium)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
KEV
Not listed

Published

August 20, 2026

Last Modified

August 21, 2026

Advisory Details (4)

Auto-updated Aug 20, 2026
Patch available. Sources: github_release, github, github_pr, github_commit.
github_release Patch Available

v3.1.3 — 8,000 stars 🌟

Patch available: liketrek/TREK v3.1.3

https://github.com/liketrek/TREK/releases/tag/v3.1.3
github_commit Patch Available

commit 03cdb4d27689 (liketrek/TREK)

Patch available: liketrek/TREK v3.1.3 (contains commit 03cdb4d27689)

https://github.com/liketrek/TREK/commit/03cdb4d27689922460ba87085d04b426d4d40d26
github_pr Patch Available

v3.1.3

Patch available: liketrek/TREK v3.1.3 (PR #1324 merged 2026-06-27)

https://github.com/liketrek/TREK/pull/1324
github Patch Available

Cross-trip reservation title disclosure via file links · Advisory · liketrek/TREK · GitHub

https://github.com/liketrek/TREK/security/advisories/GHSA-r4cp-666p-8f69

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 16× 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-28 00:55 UTCEG score recompute
  2. 2026-08-27 14:25 UTCEPSS rescore
  3. 2026-08-27 03:08 UTCEG score recompute
  4. 2026-08-26 14:46 UTCEPSS rescore
  5. 2026-08-26 05:21 UTCEG score recompute
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-25 07:33 UTCEG score recompute
  8. 2026-08-23 11:57 UTCEG score recompute
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 14:11 UTCEG score recompute
  11. 2026-08-21 23:49 UTCEPSS rescore
  12. 2026-08-21 16:21 UTCEG score recompute
  13. 2026-08-21 15:56 UTCEG score recompute
  14. 2026-08-20 22:24 UTCEG score recompute
  15. 2026-08-20 21:57 UTCEG score recompute
  16. 2026-08-20 21:56 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62945?
CVE-2026-62945 is a medium vulnerability published on August 20, 2026. TREK is a collaborative travel planner. Prior to 3.1.3, TREK file upload, update, and link actions accept attacker-controlled reservationid, placeid, and assignmentid values without using findForeignLinkTarget() to verify that the referenced object belongs to the file's trip. An authenticated user…
When was CVE-2026-62945 disclosed?
CVE-2026-62945 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-62945 actively exploited?
CVE-2026-62945 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 83.1% of all scored CVEs.
What is the CVSS score of CVE-2026-62945?
CVE-2026-62945 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-62945?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62945, 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-62945

Explore →

Is Your Infrastructure Affected by CVE-2026-62945?

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

Start Free Scan →Browse All CVEs