Skip to main content
CVE-2025-55048VulnerabilityPublished

CVE-2025-55048: Baicells NEUTRINO430, NOVA436Q, NOVA430e/430i, NOVA846, NOVA246, NOVA243, NOVA233, NOVA227 · Multiple CWE-78

Affects Baicells NEUTRINO430, NOVA436Q, NOVA430e/430i, NOVA846, NOVA246, NOVA243, NOVA233, NOVA227Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 46% 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:H

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-26.

What to do

AI-suggested

1. Immediate Network Segmentation: Isolate affected Baicells devices from critical network segments and limit their exposure to untrusted networks to reduce attack surface. 2. Access Control: Implement strict firewall rules to restrict management interfaces and control plane access to trusted IP addresses only. 3. Monitoring and Detection: Deploy network monitoring tools to detect unusual command execution patterns or anomalous traffic from Baicells devices. 4. Vendor Coordination: Engage with Baicells support to obtain timelines for patches or firmware updates addressing CVE-2025-55048. 5. Temporary Workarounds: If available, disable vulnerable services or features that process external input leading to command injection. 6. Incident Response Preparedness: Prepare for rapid incident response including device isolation, forensic analysis, and recovery procedures in case of exploitation. 7. Firmware Integrity Verification: Regularly verify firmware integrity and consider deploying devices with signed firmware to prevent unauthorized modifications. 8. Network Device Hardening: Apply best practices such as disabling unused services, changing default credentials, and enforcing strong authentication where possible. These steps go beyond generic advice by focusing on immediate containment, proactive detection, and vendor engagement specific to Baicells infrastructure.

Description

Multiple CWE-78

References

Community reviews

Loading reviews…