dbcve.org
10g08 0800gsm FirmwareOperating system · Binardat

CVE-2026-27515

CRITICAL · 9.1 CVSS v3.1 Published 2026-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Binardat 10G08-0800GSM network switch firmware versions prior to V300SP10260209 generate predictable numeric session identifiers in the web management interface. An attacker can guess valid session IDs and hijack authenticated sessions.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Binardat 10G08-0800GSM network switch firmware generates predictable numeric session identifiers in its web management interface. Attackers can exploit this by brute-forcing or guessing valid session IDs to hijack authenticated user sessions, gaining unauthorized access to the switch's administrative functions.

MitigationUpgrade firmware to version V300SP10260209 or later. If immediate upgrading is not feasible, restrict web management interface access to trusted IP addresses or VPN connections to reduce attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
10g08 0800gsm FirmwareOperating system
Affected:<= V300SP10260209

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device console or web interface and retrieve the model information. This is typically visible on the login page, in system information, or via CLI command 'show version' or 'system info'.
    Affected if The device is not a Binardat 10G08-0800GSM network switch
  2. Check the installed firmware version
    In the web management interface, navigate to System > Firmware or System > About. Alternatively, use CLI command 'show firmware-version' or 'ver'. Compare the displayed version against V300SP10260209.
    Affected if The firmware version is V300SP10260209 or any version earlier (numerically lower)
  3. Verify if web management interface is enabled
    Check the device configuration for HTTP/HTTPS management access. In CLI, use 'show ip http' or 'show management interface'. In the web interface, look under Network > Management or Administration > Access Settings.
    Affected if The web management interface (HTTP or HTTPS) is enabled and accessible
  4. Inspect session identifier format
    Log into the web management interface and examine the session cookie or token. Use browser developer tools (F12) > Application/Storage tab to view cookies, or capture a login response with a tool like curl or Burp. Check if the session ID appears as a simple sequential number.
    Affected if Session identifiers are simple numeric values without random characters (e.g., 12345, 67890 rather than alphanumeric strings)

You are affected if you have a Binardat 10G08-0800GSM switch running firmware V300SP10260209 or earlier with the web management interface enabled and session IDs that are predictable numeric values.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to version V300SP10260209 or later. If immediate upgrading is not feasible, restrict web management interface access to trusted IP addresses or VPN connections to reduce attack surface.

Recommended fix Moderate confidence

V300SP10260209

  1. Identify the current firmware version of the Binardat 10G08-0800GSM switch via the web management interface or CLI
  2. Obtain the V300SP10260209 firmware update from the official Binardat vendor support channels
  3. Access the switch web management interface and navigate to the firmware upgrade section
  4. Upload and apply the V300SP10260209 firmware file following Binardat's standard upgrade procedure
  5. Verify the upgrade was successful by checking the new firmware version in the system information
  6. Confirm session identifiers are no longer predictable by reviewing session ID generation behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 10g08 0800gsm Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,440.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27515 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27515 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data