CVE-2025-12943
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 · uneditedImproper certificate validation in firmware update logic in NETGEAR RAX30 (Nighthawk AX5 5-Stream AX2400 WiFi 6 Router) and RAXE300 (Nighthawk AXE7800 Tri-Band WiFi 6E Router) allows attackers with the ability to intercept and tamper traffic destined to the device to execute arbitrary commands on the device. Devices with automatic updates enabled may already have this patch applied. If not, please check the firmware version and update to the latest. Fixed in: RAX30 firmware 1.0.14.108 or later. RAXE300 firmware 1.0.9.82 or later
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 confidenceThe vulnerability exists in the firmware update mechanism of NETGEAR RAX30 and RAXE300 routers, where certificate validation is not properly implemented. This allows a man-in-the-middle attacker who can intercept traffic destined to the device to tamper with firmware updates and execute arbitrary commands with elevated privileges.
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< 1.0.14.108< 1.0.9.82CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLocate the model number on the device label or log into the router admin interface (typically at 192.168.1.1) and check the status or device info page to confirm whether the device is a RAX30 or RAXE300Affected if Router is a NETGEAR RAX30 or RAXE300
-
Check installed firmware versionIn the router admin interface, navigate to the Advanced tab or Status page and locate the firmware version field. The version is typically displayed as a number such as 1.0.x.xAffected if Unable to retrieve firmware version from admin interface
-
Compare version against affected rangesIf the router is a RAX30, verify the firmware version is 1.0.14.108 or higher. If the router is a RAXE300, verify the firmware version is 1.0.9.82 or higher. Check the exact version number shown in the admin interface against these thresholdsAffected if RAX30 firmware is below 1.0.14.108 OR RAXE300 firmware is below 1.0.9.82
-
Verify automatic update status (optional context)In the router admin interface under Advanced > Administration > Firmware Update or similar, check whether automatic firmware updates are enabled. This does not detect the vulnerability but helps assess update exposureAffected if Not applicable for vulnerability detection - this provides context only
If the device is a RAX30 running firmware below 1.0.14.108 or a RAXE300 running firmware below 1.0.9.82, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.9.821.0.14.108
Update router firmware to RAX30 version 1.0.14.108 or later, and RAXE300 version 1.0.9.82 or later. If automatic updates are enabled, verify the patch has been applied; otherwise, manually download and install the latest firmware from NETGEAR's official support page.
RAX30: firmware 1.0.14.108 or later | RAXE300: firmware 1.0.9.82 or later
- Access the router's web administration interface by entering the router's IP address in a web browser
- Log in with administrator credentials
- Navigate to the Administration or Advanced settings section
- Locate the Firmware Update or Router Update option
- Check the current firmware version displayed (ensure it is below 1.0.14.108 for RAX30 or below 1.0.9.82 for RAXE300)
- If the version is vulnerable, download the latest firmware from the official NETGEAR support website (kb.netgear.com or www.netgear.com) for your specific model
- In the router's firmware update page, select the option to upload the downloaded firmware file
- Wait for the firmware upload and installation to complete - do not power off the router during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12943 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-12943 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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