VulnerabilityPublished 27 Oct 2026

CVE-2026-18451: The HTML5 KVM-over-IP console authenticates with a token returned by the web interface

Source GCVE Database

Authoritative record:CVE-2026-18451· Low 3.1

Not known to be exploited · CVSS 3.1 Low.

Data as of 27 Oct 2026, 10:14 UTC

CVSS 3.1 base score

3.1Low

How severe the flaw is on the 0–10 CVSS scale.

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-3989-gjgc-5cm8

What to do

Affected software

Product	Affected	Fixed in
SMCIMBD-X12SPI	Affected =01.07.20	Fixed in–

AI-suggested

Since the vulnerability involves weak token generation, mitigation would typically involve updating the token generation mechanism to use cryptographically secure random tokens. Until a fix is available, monitoring for suspicious KVM session activity and restricting network access to the KVM interface may reduce risk.

Description

CVE-2026-18451 describes a vulnerability in the HTML5 KVM-over-IP console authentication mechanism where session tokens returned by the web interface can be guessed due to weaknesses in token generation. This could allow an attacker to take control of an active KVM session. The vulnerability has a low CVSS score of 3.1, indicating limited impact and exploitability.

Impact

An attacker who successfully guesses a valid session token can gain control over the KVM session, potentially allowing unauthorized remote management of the affected system. However, the impact is limited to confidentiality with no direct integrity or availability consequences. The low CVSS score reflects the high complexity of attack and requirement for user interaction, reducing the likelihood of exploitation.

Summary

The HTML5 KVM-over-IP console authenticates users using a session token provided by the web interface. The vulnerability arises from weaknesses in the token generation process, which may enable an attacker to predict or guess valid session tokens. Successful guessing of a token could allow unauthorized access and control over the KVM session. The CVSS 3.1 vector indicates network attack vector, high attack complexity, no privileges required, user interaction required, and low confidentiality impact with no integrity or availability impact.

CWE-337Predictable Seed in Pseudo-Random Number Generator (PRNG) (opens in a new tab)
Variant weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.
Use non-predictable inputs for seed generation.
Architecture and Design · Requirements · Libraries or Frameworks
Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems, or use the more recent FIPS 140-3 if possible.
Implementation
Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Oct 2026, 10:14 UTC

WeaknessesCWE-337

Technical details

References

Community reviews

Related threats