Cyber Resilience

CVE-2026-0412

Netgear Jr6150 Firmware

Published
09 June 2026
Modified
18 June 2026
Patch / advisory
CVSS Score v4 4.3
Click a component to see what it means
Raw vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:D/RE:X/U:Amber
EPSS Score 0.0015 5th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-0412 is a medium-severity Improper Input Validation (CWE-20) vulnerability in Netgear Jr6150 Firmware. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique System Firmware (T1542.001); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-22 (Unsupported System Components) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Insufficient input validation vulnerability in NETGEAR JR6150 (AC750 WiFi Router 802.11ac Dual Band Gigabit released in 2014) allows administrators connected to the local network to make unauthorized modification of router software and functionality. NETGEAR JR6150 reached End-of-Support status in 2018…

more

and is no longer receiving security updates. 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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1542.001 System Firmware Stealth
Adversaries may modify system firmware to persist on systems.
T1601.001 Patch System Image Defense Impairment
Adversaries may modify the operating system of a network device to introduce new capabilities or weaken existing defenses.
Why these techniques?

Insufficient input validation enables unauthorized local modification of router firmware/software, directly mapping to system firmware and system image patching techniques.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-0419Same product: Netgear Jr6150
CVE-2026-0415Same vendor: Netgear
CVE-2026-0416Same vendor: Netgear
CVE-2026-0404Same vendor: Netgear
CVE-2016-10176Same vendor: Netgear
CVE-2026-0403Same vendor: Netgear
CVE-2026-0406Same vendor: Netgear
CVE-2026-9213Same vendor: Netgear
CVE-2025-12942Same vendor: Netgear
CVE-2026-9210Same vendor: Netgear

Affected Assets

netgear
jr6150 firmware
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-10 Information Input Validation
  • SA-22 Unsupported System Components
  • SI-7 Software, Firmware, and Information Integrity
Detect
Catch it (NIST detect / respond)
  • SI-7 Software, Firmware, and Information Integrity
Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly requires input validation on all external inputs to block the unauthorized software/functionality modifications described in CWE-20.

prevent

Mandates replacement of the EoS JR6150 (unsupported since 2018) whose lack of patches leaves the input-validation flaw permanently exposed.

preventdetect

Requires integrity verification of firmware and configuration to detect or block unauthorized modifications attempted via the flawed input paths.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require and enforce input validation during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

detects

Testing against a defined set of requirements and using code review plus vulnerability scanning forces validation of inputs and handling of unanticipated conditions, reducing the chance that malformed data will be accepted.

prevents

Secure-coding guidelines and mandatory security testing (including code scans) compel developers to validate and sanitize inputs at design and implementation time, lowering the incidence of malformed or malicious data reaching downstream components.

prevents

Mandating input controls that include integrity checks and input validation ensures that untrusted data is examined before use, blocking the root cause of many injection and malformed-data weaknesses.

prevents

Security-by-design principles explicitly call for data validation and sanitization at every layer, reducing the chance that malformed or malicious input will be processed without scrutiny.

prevents

Requiring language-specific secure coding standards, peer review, SAST and documented mitigation of common programming errors forces validation of all inputs before they are trusted.

none

Regular automated validation of system software and data content, combined with scanning of all inbound files, enforces input validation at the boundary before untrusted content is processed.

References