Skip to content
Networks

CVE-2026-27519

8.7
High
EPSS 0.19%Feb 25, 2026

RC4 with static key in Binardat switch firmware enables data decryption.

common questions

Is CVE-2026-27519 being exploited?

Not confirmed. CVE-2026-27519 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-27519?

CVE-2026-27519 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-27519?

Not known from our data. No patch reference has been recorded for CVE-2026-27519, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-27519 affect?

CVE-2026-27519 affects Binardat 10G08-0800GSM switch firmware (V300SP10260209 and earlier). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-27519?

Apply firmware update when released; fix RC4 usage and hard-coded key.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Binardat 10G08-0800GSM switch firmware (V300SP10260209 and earlier)
impact

Attacker can decrypt protected values and breach confidentiality due to static RC4 key embedded in client-side JS.

action required

Patch when possible

affected versions
Binardat Ltd. 10G08-0800GSM Network Switch
  • affected<= V300SP10260209

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free