/

CVE-2026-78167

Severity:

CRITICAL RISK

(10.0)

Improper Authentication (CWE-287) in ipTIME T16000M

CVE-2026-78167

Deferred

Vulnerability type

Category:

Improper Authentication

CWE:

CWE-287

Impact:

Authentication Bypass and Unauthorized Access

Severity:

CRITICAL RISK

(10.0)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A critical improper authentication vulnerability affects the EFM ipTIME T16000M router in its Session Validation Handler. A remote attacker may bypass expected session checks and gain unauthorized access when the vulnerable request path is reachable.

Affected context

The weakness occurs in the httpcon_check_session_url function of the Session Validation Handler in EFM ipTIME T16000M firmware 14.20.2. Risk is higher when the device exposes the affected management or session-validation interface to untrusted networks and the handler fails to reliably verify session state.

Exploit preconditions

  • Attack surface: Network-accessible router session or management interface - Required access: Remote network connectivity to the affected service; valid

credentials may not be required if authentication checks can be bypassed

  • Trigger point: Processing of a request by httpcon_check_session_url - Why exploitation is possible: The session validation logic may accept a

request without adequately establishing that the requester is authenticated

Why this happens

The underlying bug is an authentication-state validation failure. A session handler does not consistently enforce the relationship between a request and a valid authenticated session, allowing an unauthenticated or insufficiently authenticated request to reach protected functionality. This maps to CWE-287: Improper Authentication, which covers failures to correctly verify the identity or authentication state of a requester.

Potential impact

  • An attacker may bypass authentication controls
  • Unauthorized users could access protected router functionality
  • Device configuration or network settings could be exposed or altered
  • The router could be used as a foothold for further attacks
  • Availability or confidentiality of connected services could be affected

General mitigation guidance

Mitigation generally focuses on making authentication checks centralized, explicit, and fail-closed. Session validation should use secure, server-side state, reject missing or malformed authentication context, and apply the same authorization checks to every protected operation. Management interfaces can be isolated from untrusted networks, administrative access can be minimized, and device services can run with the least privilege available. Input trust should be reduced by treating all client-controlled session identifiers and request metadata as untrusted. Defense-in-depth controls such as secure session expiration, transport protection, and monitoring of authentication failures can further limit exposure.

How teams detect issues like this

Detection approaches include static analysis and code review for session checks that rely on client-controlled state, inconsistent authentication branches, or protected handlers reachable before identity verification. Test suites can exercise protected endpoints with absent, expired, malformed, and mismatched session context and verify fail-closed behavior. Network monitoring and policy enforcement can identify unexpected access to management interfaces, repeated authentication failures, and successful requests lacking an associated authenticated session. Automated security review tools may help flag authentication logic requiring manual confirmation.

Sources

SourceLink
github.comgithub.com/AdminSafe/CVE/issues/2
github.comgithub.com/AdminSafe/CVE/issues/3
vuldb.comvuldb.com/cve/CVE-2026-78167
vuldb.comvuldb.com/submit/874154
vuldb.comvuldb.com/submit/874302
vuldb.comvuldb.com/vuln/394556
vuldb.comvuldb.com/vuln/394556/cti

Frequently asked

questions

Yes. The description indicates that remote exploitation is possible when an

attacker can reach the affected session validation interface.

Not necessarily. An authentication bypass may allow protected functionality to

be reached without valid credentials, although network exposure and deployment

controls still affect practical exploitability.

Ensure every protected request undergoes consistent server-side authentication

and authorization checks, with invalid or missing session state rejected by

default.

Centralize session validation, test negative authentication cases, restrict

management interfaces to trusted networks, and monitor for anomalous access to

protected router functions.

Find out what's already
exploitable in your codebase.