Skip to main content
CVE-2025-55049VulnerabilityPublished

CVE-2025-55049: Baicells NEUTRINO430 · CWE-1394

Affects Baicells NEUTRINO430Source CVE Database V5

0

Not known to be exploited · CVSS 9.1 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.1Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

AI-suggested

Immediate mitigation should focus on replacing the default cryptographic keys with unique, securely generated keys for each device. Baicells should be engaged to provide a firmware update or patch that removes the use of default keys and enforces secure key management practices. Network operators should audit their deployed NEUTRINO430 devices to identify affected versions and isolate vulnerable units until patched. Implement network segmentation and strict access controls to limit exposure of vulnerable devices to untrusted networks. Employ monitoring and anomaly detection to identify unusual traffic patterns indicative of exploitation attempts. If possible, deploy additional encryption layers at higher network levels to reduce reliance on device-level cryptography. Organizations should also review and update their incident response plans to address potential exploitation scenarios involving compromised cryptographic keys. Finally, ensure that all future device deployments follow best practices for cryptographic key management, including unique key provisioning and secure storage.

Description

Use of Default Cryptographic Key (CWE-1394)

References

Community reviews

Loading reviews…