/

CVE-2026-24455

Severity:

HIGH RISK

(7.5)

Cleartext Transmission of Sensitive Information

CVE-2026-24455

Awaiting Analysis

Vulnerability type

Category:

Cleartext Transmission of Sensitive Information

CWE:

CWE-319

Impact:

Credential Exposure and Account Compromise

Severity:

HIGH RISK

(7.5)

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

The embedded web interface of the device performs user authentication over plain HTTP using Basic Authentication without HTTPS/TLS.

Because traffic is only encoded and not encrypted, user credentials can be exposed to passive interception by attackers with access to the same network segment.

Affected context

This vulnerability appears in devices whose embedded web management interface:

  • Listens over HTTP only and does not support HTTPS/TLS
  • Uses HTTP Basic Authentication for login
  • Transmits credentials and session data in cleartext over local or remote networks

It becomes particularly risky in environments where devices share networks with untrusted users, guest clients, or other systems that could be monitored.

Exploit preconditions

  • Attack surface: Network access to the device's web management interface (typically over HTTP).
  • Required access: Ability to observe network traffic between the user's browser and the device (e.g., on the same LAN, Wi‑Fi, or routed path).
  • Trigger point: A legitimate user initiates a login or performs authenticated actions via the web interface.
  • Why exploitation is possible: HTTP Basic Authentication sends credentials in a reversible encoded form (e.g., Base64) over an unencrypted channel; passive network observers can capture and decode these credentials without needing to modify traffic.

Why this happens

The root cause is reliance on an unencrypted communication channel for transmitting sensitive authentication data.

By exposing HTTP Basic Authentication over plain HTTP instead of wrapping it in a secure transport (such as TLS), the design maps directly to CWE-319: Cleartext Transmission of Sensitive Information.

The pattern is an architectural weakness where confidentiality of credentials is assumed from encoding alone, rather than enforcing proper encryption in transit.

Potential impact

  • Attackers on the same network may capture usernames and passwords.
  • Compromise of administrative accounts on the device.
  • Unauthorized configuration changes, including altering network or security settings.
  • Use of captured credentials to access other systems if users reuse passwords.
  • Facilitation of further lateral movement and reconnaissance within the network.

General mitigation guidance

Effective mitigation focuses on ensuring that authentication data is never transmitted in cleartext and that management interfaces are protected by secure transport and access controls.

Common defensive patterns include:

  • Requiring HTTPS/TLS for all access to the web management interface, enforcing secure transport by default.
  • Configuring redirects from HTTP to HTTPS and disabling plain HTTP for authenticated endpoints.
  • Using modern authentication mechanisms that assume and verify encrypted transport layers.
  • Restricting management interface access to dedicated, trusted network segments or out-of-band management networks.
  • Applying least-privilege account policies and unique, strong credentials to reduce the impact of any single account compromise.

How teams detect issues like this

Organizations can detect this class of issue through:

  • Network security assessments that inspect management traffic for cleartext credentials or unencrypted HTTP logins.
  • Automated scanning tools that flag administrative interfaces exposed over HTTP instead of HTTPS.
  • Configuration and design reviews focusing on transport security for all authentication flows.
  • Static or policy-based checks (e.g., infrastructure-as-code or device configuration linting) that enforce TLS requirements on management services.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-050-03.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-050-03

Frequently asked

questions

It can be exploitable by any attacker who can observe network traffic between the user and the device, which might include remote attackers if the interface is exposed over routed or VPN-connected networks, or local attackers on the same LAN or Wi‑Fi network.

The attacker typically needs passive network access—such as being connected to the same switch, Wi‑Fi access point, or path through which the device management traffic flows—so they can sniff packets and capture the cleartext authentication exchange.

The most robust fix is to require encrypted transport (HTTPS/TLS) for all authentication and management operations, disable or strongly restrict HTTP, and ensure that certificate handling and configuration defaults make the secure path the only practical option.

Future designs should treat all credentials as sensitive data that must be protected in transit with strong encryption, mandate TLS for any login-capable interface, and enforce security-focused defaults so that administrators cannot accidentally deploy management services without proper transport security.

Find out what's already
exploitable in your codebase.