dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2026-27848

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
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
Due to missing neutralization of special elements, OS commands can be injected via the handshake of a TLS-SRP connection, which are ultimately run as the root user. This issue affects MR9600: 1.0.4.205530; MX4200: 1.0.13.210200.

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

A command injection vulnerability exists in the TLS-SRP handshake implementation of the affected routers (MR9600 and MX4200). Due to insufficient input validation, an attacker can inject arbitrary OS commands during the TLS-SRP authentication process, which are executed with root privileges.

MitigationApply vendor-supplied firmware updates to patch the command injection vulnerability in the TLS-SRP handshake; until then, restrict network access to management interfaces.

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

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
High

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

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. Confirm router model
    Access the router admin interface or check the device label to verify the exact model number is MR9600 or MX4200
    Affected if The router model is MR9600 or MX4200
  2. Identify firmware version
    Log into the router web interface or use the CLI command 'show version' or 'ubootenv -r' to retrieve the installed firmware version
    Affected if The installed firmware version is unpatched and falls within the vulnerable release range
  3. Verify TLS-SRP authentication status
    Access the router authentication settings (typically under Security or Wireless settings) and check whether TLS-SRP (Secure Remote Password) authentication is enabled for any SSID or network profile
    Affected if TLS-SRP authentication is currently enabled on the router
  4. Check management interface exposure
    Review the router's access control settings to determine if the management web interface or administrative ports (HTTP/HTTPS, SSH, telnet) are accessible from external/untrusted networks
    Affected if Management interfaces are exposed to untrusted networks while TLS-SRP is enabled
  5. Inspect for indicators of compromise
    Review router system logs for unexpected processes, unusual outbound connections, or authentication events from unknown sources during the TLS-SRP handshake timeframe
    Affected if Logs show suspicious commands execution or unauthorized authentication attempts targeting the SRP handshake

The environment is affected if the router is an MR9600 or MX4200 model with an unpatched firmware version and TLS-SRP authentication is enabled, allowing remote attackers to execute commands with root privileges during the TLS-SRP handshake.

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

Apply vendor-supplied firmware updates to patch the command injection vulnerability in the TLS-SRP handshake; until then, restrict network access to management interfaces.

Recommended fix Moderate confidence

Latest Netgear MR9600 and MX4200 firmware releases (contact Netgear or check support.netgear.com for specific version numbers containing the fix)

  1. Check the vendor's (Netgear) support website or contact Netgear security for the latest firmware versions for MR9600 and MX4200 routers
  2. Verify the current firmware version on affected devices using the router's admin interface or API
  3. Download the latest firmware version from Netgear's official support website
  4. Upload and apply the firmware update through the router's administration interface
  5. After update, verify the TLS-SRP implementation no longer accepts injectable special elements
  6. Confirm the device is running the patched firmware version
Caveat Standard firmware update risks apply - ensure backup of configuration and plan for brief downtime

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27848 — 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-27848 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