CVE-2026-48745

CRITICALPre-NVD 9.39.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (25th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source

Also known asEUVD-2026-37510 (ENISA EUVD)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 9.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Traccar Client is a GPS tracking mobile app for sending location updates to private servers using the open-source Traccar platform. In versions 9.7.19 and below, a single crafted deep link can silently hijack all GPS tracking parameters and redirect telemetry to an attacker-controlled server. The app registers a custom org.traccar.client://config deep-link scheme that silently writes attacker-supplied parameters (server URL, device ID, accuracy, distance, and interval) into the app's persistent configuration with no confirmation, notification, or visual indication. A single crafted link delivered via SMS, email, a webpage, or any installed app can therefore reconfigure the app the moment the victim taps it, with no special permissions required. As a result, an attacker can covertly redirect all of the victim's GPS telemetry to their own server at maximum precision and frequency, and the change persists across restarts. This gives the attacker continuous, real-time tracking of the victim's location. This issue has been fixed in version 9.7.20.

CVSS v3
9.3
EG Score
9.3CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
25th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 17, 2026

Last Modified

October 25, 2026

Advisory Details (2)

Auto-updated Oct 8, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Silent configuration Hijack via unauthenticated org.traccar.client://config deep link - full GPS telemetry redirection on v9.7.19 (build 136) - latest release · Advisory · traccar/traccar-client · GitHub

https://github.com/traccar/traccar-client/security/advisories/GHSA-vm6j-6g39-gj97
GitHub commit Patch Available

commit 23558b0ae390 (traccar/traccar-client)

Patch available: traccar/traccar-client v9.7.20 (contains commit 23558b0ae390)

https://github.com/traccar/traccar-client/commit/23558b0ae390f8480b2233da07410b5aeaafba09

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 187 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 87 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:46 UTCEG score recompute
  2. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  3. 2026-10-31 18:18 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  5. 2026-10-30 19:43 UTCEG score recompute
  6. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  7. 2026-10-29 21:16 UTCEG score recompute
  8. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  9. 2026-10-28 22:49 UTCEG score recompute
  10. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  11. 2026-10-28 00:23 UTCEG score recompute
  12. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  13. 2026-10-27 01:55 UTCEG score recompute
  14. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-25 20:55 UTCEG score recompute
  16. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  17. 2026-10-25 14:23 UTCEG score recompute
  18. 2026-10-24 22:28 UTCEG score recompute
  19. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  20. 2026-10-24 00:00 UTCEG score recompute
  21. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  22. 2026-10-23 01:32 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  24. 2026-10-22 03:05 UTCEG score recompute
  25. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
Show 75 more
  1. 2026-10-21 04:37 UTCEG score recompute
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  3. 2026-10-20 06:10 UTCEG score recompute
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-19 07:36 UTCEG score recompute
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-18 03:34 UTCEG score recompute
  8. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-17 06:16 UTCEG score recompute
  10. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  11. 2026-10-16 07:28 UTCEG score recompute
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-15 06:21 UTCEG score recompute
  14. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  15. 2026-10-14 02:03 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  17. 2026-10-12 22:22 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  19. 2026-10-12 16:00 UTCEG score recompute
  20. 2026-10-11 19:43 UTCEG score recompute
  21. 2026-10-11 16:58 UTCEG score recompute
  22. 2026-10-11 14:22 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  25. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  26. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  27. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  28. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  29. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  30. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  31. 2026-10-03 16:19 UTCOSV refresh
  32. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  33. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  34. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  35. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  36. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  37. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  38. 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  39. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  41. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  42. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  43. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  44. 2026-09-14 03:12 UTCEG score recompute
  45. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  47. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  48. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  49. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  50. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  51. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  52. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  54. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-08-30 22:27 UTCEG score recompute
  56. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  59. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  62. 2026-08-24 22:28 UTCEG score recompute
  63. 2026-08-23 04:33 UTCEG score recompute
  64. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  65. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  66. 2026-08-21 01:11 UTCEG score recompute
  67. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  68. 2026-08-20 08:17 UTCEG score recompute
  69. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  70. 2026-08-19 08:13 UTCEG score recompute
  71. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  72. 2026-08-17 14:26 UTCEG score recompute
  73. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  74. 2026-08-16 21:12 UTCEG score recompute
  75. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 25th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-48745?
CVE-2026-48745 is a critical-severity vulnerability; its CVE record was published on June 17, 2026. Traccar Client is a GPS tracking mobile app for sending location updates to private servers using the open-source Traccar platform. In versions 9.7.19 and below, a single crafted deep link can silently hijack all GPS tracking parameters and redirect telemetry to an attacker-controlled server. The…
When was the CVE record for CVE-2026-48745 published?
The CVE record for CVE-2026-48745 was published on June 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 25, 2026; the record at its source may have been updated since.
Is CVE-2026-48745 actively exploited?
CVE-2026-48745 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (25th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48745?
CVE-2026-48745 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48745?
A fix for CVE-2026-48745 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48745?

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

Book a Demo →Browse All CVEs