CVE Intelligence
Analysis AI-assisted

CVE-2026-27515: Binardat 10G08-0800GSM Network Switch Predictable Session Identifiers

CVE-2026-27515 affects the Binardat 10G08-0800GSM network switch firmware before V300SP10260209, whose web management interface generates predictable numeric session identifiers. According to the record, an attacker could guess valid session IDs and hijack authenticated sessions. The record lists a CVSS base score of 9.1 (critical), and no confirmed exploitation appears in the sources consulted.

Published Oct 24, 2026 · Updated Oct 24, 2026 · Ler em português

Overview

CVE-2026-27515 is a weakness classified as CWE-330 (Use of Insufficiently Random Values) in the web management interface of the Binardat 10G08-0800GSM network switch. The record describes firmware versions prior to V300SP10260209 as affected. Sources consulted include the VulnCheck advisory and the NVD entry.

Impact

  • The description states that an attacker can guess valid session IDs and hijack authenticated sessions.
  • The record gives a CVSS base score of 9.1 (critical) with high confidentiality and integrity impact and no availability impact in the vector.
  • The SSVC data in the record marks the issue as automatable with total technical impact and exploitation status none.

Affected products and versions

  • Binardat 10G08-0800GSM Network Switch firmware, listed in the record with the boundary written as up to and including V300SP10260209.
  • Binardat 10G08-0800GSM Network Switch, listed in the record with the boundary written as before V300SP10260209.
  • The record uses both notations at the boundary, so the exact treatment of the V300SP10260209 build needs confirmation from the vendor.
  • The record's fixes field is empty. This does not mean no fix exists; it means the record does not identify one.

Exploitation status

  • The record shows the vulnerability is not listed in the CISA KEV catalog.
  • No confirmed exploitation appears in the sources consulted.
  • The EPSS probability is 0.00521 with a percentile of 0.43415 in the record.

Remediation and mitigation

  • Inventory Binardat 10G08-0800GSM switches and compare firmware versions against the boundary V300SP10260209.
  • Prioritize updating affected devices to a firmware build that the vendor confirms is not affected, and verify that build against the vendor's own documentation.
  • Restrict access to the web management interface to trusted administrative networks and disable it where it is not required.
  • Limit the number of simultaneous administrative sessions where the device allows it, and end sessions after administrative work.

Detection guidance

  • Review management interface logs for logins or sessions from unexpected source addresses or at unusual times.
  • Watch for administrative sessions that appear without a matching login event from an authorized operator.
  • Correlate switch management logs with network access records to spot anomalous administrative activity.

Limitations of the available information

  • The record does not describe how the session identifiers are generated, so the technical details of the weakness are not confirmed beyond the description.
  • No fixed version is stated in the record.
  • The record uses inconsistent boundary notation (up to and including versus before) for the same version string.
  • The EPSS date in the record (2026-10-23) is later than the publication date (2026-02-24) and should be verified against the source.

Frequently asked questions

What is the weakness in CVE-2026-27515?

The web management interface generates predictable numeric session identifiers, classified as CWE-330. According to the description, this lets an attacker guess valid session IDs.

Which versions are affected?

The record lists Binardat 10G08-0800GSM firmware and switch entries with the boundary V300SP10260209, written with inconsistent notation. Confirm the exact boundary with the vendor.

Is this vulnerability known to be exploited?

It is not listed in the CISA KEV catalog in the record, and no confirmed exploitation appears in the sources consulted.

What should administrators do now?

Inventory affected devices, restrict management interface access to trusted networks, and update to a build the vendor confirms is not affected.

This analysis was drafted with AI assistance from verified source data and automatically checked against it.