dbcve.org
Jr6150 FirmwareOperating system · Netgear

CVE-2026-0419

HIGH · 8.0 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Insufficient input validation in NETGEAR JR6150 (AC750 WiFi Router 802.11ac Dual Band Gigabit released in 2014) allows users connected to the local WiFi Networks to execute operating system commands. NETGEAR JR6150 has reached End-of-Support phase as of 2018 , and no further security updates are planned. NETGEAR strongly recommends replacing these devices with newer NETGEAR models to ensure continued security support and updates. This vulnerability has been identified through firmware emulation in a controlled research environment and has not been verified on production hardware.

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 · high confidence

Insufficient input validation in NETGEAR JR6150 router firmware allows authenticated WiFi users to inject and execute arbitrary operating system commands on the underlying Linux-based firmware. This is a command injection vulnerability exploitable by any user with local WiFi network access.

MitigationReplace the End-of-Life (EoL 2018) NETGEAR JR6150 with a supported router model, as no security patches are available. If immediate replacement is not feasible, isolate the device on a restricted VLAN and strictly limit WiFi access to trusted personnel only.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jr6150 FirmwareOperating system
Affected:all versions

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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 device model is JR6150
    Log into the router admin interface (typically at 192.168.1.1) or check the device label on the router itself to verify the exact model number matches JR6150
    Affected if The device model is NETGEAR JR6150 - all firmware versions of this model are affected
  2. Check if WiFi is enabled
    Access the router's wireless settings page in the admin interface and verify whether the 2.4GHz or 5GHz WiFi radio is currently turned on
    Affected if WiFi is enabled and broadcastng - the vulnerability is exploited through authenticated WiFi access, so an active WiFi interface is required for exploitation
  3. Verify router is accessible on local network
    Attempt to ping the router's local IP address (commonly 192.168.1.1) from a computer connected to the same network to confirm the device is online and responding
    Affected if The router is powered on and connected to the network - an active device can be targeted by anyone with WiFi credentials
  4. Confirm you have WiFi credentials
    Determine whether you possess the current WiFi network name (SSID) and password used on this router
    Affected if You have valid WiFi credentials - the vulnerability requires only authenticated WiFi access, not administrator privileges, meaning any WiFi user can exploit it

If the device is a NETGEAR JR6150 with WiFi enabled and accessible on your network, and you or any WiFi user possess valid WiFi credentials, the environment is affected by this vulnerability.

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

Replace the End-of-Life (EoL 2018) NETGEAR JR6150 with a supported router model, as no security patches are available. If immediate replacement is not feasible, isolate the device on a restricted VLAN and strictly limit WiFi access to trusted personnel only.

Recommended fix High confidence
  1. The NETGEAR JR6150 router reached End-of-Support in 2018 and NETGEAR has explicitly stated no further security updates are planned.
  2. Replace the End-of-Life JR6150 with a currently supported NETGEAR router model to receive ongoing security patches.
  3. When selecting a replacement, choose a model that is still within NETGEAR's active support lifecycle to ensure future security updates.
Caveat Device replacement required - the JR6150 will no longer receive any security updates

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

Fix this in Jr6150 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,730
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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