CVE-2026-78887

LOWPre-NVD 3.73.7—
EchelonGraph scoreHIGH confidence

Score 3.7 from GitHub Security Advisory published 2026-08-25. a secondary CVSS source baseline 3.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.7EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.7Exploit: None knownExposed: 0

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

A weakness has been identified in liketrek TREK up to 3.0.22. This impacts the function validateShareTokenForAsset of the component Journey Photo Proxy. Executing a manipulation can lead to incorrect authorization. The attack can be launched remotely. This attack is characterized by high complexity. The exploitability is said to be difficult. Upgrading to version 3.1.0 will fix this issue. You should upgrade the affected component.

CVSS v3
3.7
EG Score
3.7(high)
EG Risk
21(Track)
EG Risk 21/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
Severity37% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 25, 2026

Last Modified

August 26, 2026

References (6)

Vendor Advisories for CVE-2026-78887(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 46× 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-09-20 20:16 UTCEPSS rescore
  2. 2026-09-20 08:56 UTCEG score recompute
  3. 2026-09-20 08:56 UTCGHSA enrichment
  4. 2026-09-18 19:28 UTCEPSS rescore
  5. 2026-09-17 15:09 UTCEG score recompute
  6. 2026-09-17 15:09 UTCGHSA enrichment
  7. 2026-09-16 14:08 UTCEPSS rescore
  8. 2026-09-16 05:15 UTCEPSS rescore
  9. 2026-09-15 03:12 UTCEPSS rescore
  10. 2026-09-15 03:12 UTCEPSS rescore
  11. 2026-09-14 21:22 UTCEG score recompute
  12. 2026-09-14 21:22 UTCGHSA enrichment
  13. 2026-09-12 03:35 UTCEG score recompute
  14. 2026-09-12 03:35 UTCGHSA enrichment
  15. 2026-09-11 14:53 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-09 09:48 UTCEG score recompute
  18. 2026-09-09 09:48 UTCGHSA enrichment
  19. 2026-09-08 22:01 UTCEPSS rescore
  20. 2026-09-06 16:01 UTCEG score recompute
  21. 2026-09-06 16:01 UTCGHSA enrichment
  22. 2026-09-06 13:48 UTCEPSS rescore
  23. 2026-09-04 05:07 UTCEPSS rescore
  24. 2026-09-03 22:14 UTCEG score recompute
  25. 2026-09-03 22:14 UTCGHSA enrichment
Show 21 more
  1. 2026-09-02 14:12 UTCEPSS rescore
  2. 2026-09-01 13:54 UTCEPSS rescore
  3. 2026-09-01 04:40 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-09-01 04:22 UTCEG score recompute
  6. 2026-09-01 04:21 UTCGHSA enrichment
  7. 2026-08-30 19:18 UTCEPSS rescore
  8. 2026-08-30 19:17 UTCEPSS rescore
  9. 2026-08-30 01:22 UTCEPSS rescore
  10. 2026-08-29 10:34 UTCEG score recompute
  11. 2026-08-29 10:34 UTCGHSA enrichment
  12. 2026-08-28 21:42 UTCEPSS rescore
  13. 2026-08-27 14:25 UTCEPSS rescore
  14. 2026-08-26 16:44 UTCEG score recompute
  15. 2026-08-26 16:44 UTCGHSA enrichment
  16. 2026-08-26 14:47 UTCEPSS rescore
  17. 2026-08-25 18:28 UTCEG score recompute
  18. 2026-08-25 18:28 UTCGHSA enrichment
  19. 2026-08-25 13:22 UTCEG score recompute
  20. 2026-08-25 12:52 UTCEG score recompute
  21. 2026-08-25 12:51 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78887?
CVE-2026-78887 is a low vulnerability published on August 25, 2026. A weakness has been identified in liketrek TREK up to 3.0.22. This impacts the function validateShareTokenForAsset of the component Journey Photo Proxy. Executing a manipulation can lead to incorrect authorization. The attack can be launched remotely. This attack is characterized by high…
When was CVE-2026-78887 disclosed?
CVE-2026-78887 was first published in the National Vulnerability Database on August 25, 2026, with the most recent update on August 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78887 actively exploited?
CVE-2026-78887 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 78.0% of all scored CVEs.
What is the CVSS score of CVE-2026-78887?
CVE-2026-78887 has a CVSS v3 base score of 3.7 (NVD).
How do I remediate CVE-2026-78887?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78887, 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-78887

Explore →

Is Your Infrastructure Affected by CVE-2026-78887?

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

Start Free Scan →Browse All CVEs