Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-78167 – Authentication Bypass – ipTIME T16000M 14.20.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-78167 is a critical improper authentication vulnerability in the EFM ipTIME T16000M router/switch, version 14.20.2. The flaw resides in the httpcon_check_session_url function of the device’s Session Validation Handler, allowing remote, unauthenticated attackers to bypass session validation. It carries the maximum CVSS v3.1 base score of 10.0, and a public proof-of-concept exploit is available.

Technical details

  • Root cause: The httpcon_check_session_url function in the Session Validation Handler component fails to properly validate session state, allowing session/authentication checks to be bypassed.
  • Trigger conditions: An attacker sends a crafted HTTP request to the device’s management interface that manipulates the session validation logic; no valid credentials or prior session are required.
  • Attack vector: Network-based, remotely exploitable with low attack complexity and no privileges or user interaction required.
  • Impact: Full compromise of confidentiality, integrity, and availability of the device is possible, consistent with the CVSS impact metrics (C:H/I:H/A:H) and the scope-changed (S:C) vector, indicating potential impact beyond the vulnerable component itself.

Affected software

  • EFM ipTIME T16000M, firmware version 14.20.2

Severity

  • CVSS v3.1 Base Score: 10.0 (CRITICAL)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: No vendor patch has been confirmed as of this writing; the vendor was reportedly contacted about the issue but did not respond. Check EFM/ipTIME’s official support channels for a firmware update addressing this issue and apply it as soon as it is released.
  • If no patch is available:
    • Do not expose the ipTIME T16000M management/web interface to the internet; restrict access to trusted internal networks only.
    • Place the device behind a VPN or firewall rule limiting inbound access to the administrative interface.
    • Monitor device logs for unexpected session or authentication activity.
    • Consider replacing or isolating the device if it cannot be taken offline from the public internet until a fix is available.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: ipTIME T16000M

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge