CVE-2026-78167

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-24. A secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated
10.0EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 1.5%CVSS: 10.0Exploit: No code on recordExposed services: Not assessed

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

A weakness has been identified in EFM ipTIME T16000M 14.20.2. The impacted element is the function httpcon_check_session_url of the component Session Validation Handler. This manipulation causes improper authentication. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/100

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 (value × EchelonGraph’s weight)
Severity100% × 45%
The EG Score, 10.0 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
1.5%
EPSS %ILE
73rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

August 24, 2026

Last Modified

October 12, 2026

Advisory Details (2)

Auto-updated Oct 13, 2026
🔬 Proof of concept available. No fix on record yet.
Web page🟡 PoC Available

The ipTIME T16000M router is vulnerable to authentication bypass and arbitrary password reset in /sess-cgi/ · Issue #3 · AdminSafe/CVE · GitHub

https://github.com/AdminSafe/CVE/issues/3
Web page

The ipTIME T16000M router allows remote code execution (RCE) through a hidden backdoor in /sess-bin/d.cgi · Issue #2 · AdminSafe/CVE · GitHub

https://github.com/AdminSafe/CVE/issues/2

Vendor Advisories for CVE-2026-78167(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 23× in last 7d / 184× 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 366 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 266 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78167?
CVE-2026-78167 is a critical-severity vulnerability; its CVE record was published on August 24, 2026. A weakness has been identified in EFM ipTIME T16000M 14.20.2. The impacted element is the function httpconchecksession_url of the component Session Validation Handler. This manipulation causes improper authentication. Remote exploitation of the attack is possible. The exploit has been made…
When was the CVE record for CVE-2026-78167 published?
The CVE record for CVE-2026-78167 was published on August 24, 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 12, 2026; the record at its source may have been updated since.
Is CVE-2026-78167 actively exploited?
CVE-2026-78167 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.5% probability of exploitation in the next 30 days (73rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-78167?
CVE-2026-78167 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-78167?
No fix for CVE-2026-78167 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-78167 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-78167?

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

Book a Demo →Browse All CVEs