An issue in SJRC F11 SJ-GPS-PRO firmware build 2019-09-17 allows a remote attacker to obtain sensitive information via the tcp_actions() function
CVE-2026-52481
This high-severity CVE scores 7.5 under CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 70% 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).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.5
- EG Score
- 7.5(medium)
- EG Risk
- 65(Attend)EG Risk 65/100SSVC: Attend
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 computedSeverity75% × 45%Exploitation40% × 40%Automatability100% × 15%Action: Remediate soon — notable exploitation risk. - EPSS PROB
- 0%
- EPSS %ILE
- 30%
- KEV
- Not listed
Published
August 18, 2026
Last Modified
August 19, 2026
Advisory Details (1)
Auto-updated Aug 19, 2026GitHub - AshtonKopelevich/SJ-GPS-PRO-F11-Vulnerability · GitHub
https://github.com/AshtonKopelevich/SJ-GPS-PRO-F11-VulnerabilityWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 25× 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.
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 05:03 UTCEG score recompute
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 01:06 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-27 01:12 UTCEG score recompute
- 2026-08-26 14:46 UTCEPSS rescore
- 2026-08-26 01:10 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 01:19 UTCEG score recompute
- 2026-08-24 13:24 UTCEG score recompute
- 2026-08-23 01:37 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:48 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:57 UTCEG score recompute
- 2026-08-20 22:55 UTCEPSS rescore
- 2026-08-20 01:22 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 13:24 UTCEG score recompute
- 2026-08-19 13:00 UTCEG score recompute▲ 7.50
- 2026-08-19 12:57 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
- 2026-08-18 20:22 UTCNVD update
- 2026-08-18 19:53 UTCEG score recompute
- 2026-08-18 19:53 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-52481?
When was CVE-2026-52481 disclosed?
Is CVE-2026-52481 actively exploited?
What is the CVSS score of CVE-2026-52481?
How do I remediate CVE-2026-52481?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-52481
Is Your Infrastructure Affected by CVE-2026-52481?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.