What is the CVSS score of CVE-2026-27849?

CVE-2026-27849 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2026-27849?

Within 24 hours: Inventory all MR9600 (v1.0.4.205530) and MX4200 (v1.0.13.210200) devices and isolate affected units from production networks if operationally feasible. Within 7 days: Implement network segmentation to restrict access to TLS-SRP update ports and disable the update functionality if not critical to operations; enable enhanced logging and monitoring for suspicious activity on these devices. Within 30 days: Contact Meraki support for patch availability and timeline; develop a staged deployment plan for patching; conduct forensic analysis to detect any prior exploitation.

CVE-2026-27849

CRITICAL

OS Command Injection (CWE-78)

2026-02-25 a6d3dc9e-0591-4a13-bce7-0f5b31ff6158

Command Injection

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Mar 12, 2026 - 21:55 vuln.today

CVE Published

Feb 25, 2026 - 17:25 nvd

CRITICAL 9.8

DescriptionCVE.org

Due to missing neutralization of special elements, OS commands can be injected via the update functionality of a TLS-SRP connection, which is normally used for configuring devices inside the mesh network. This issue affects MR9600: 1.0.4.205530; MX4200: 1.0.13.210200.