CVE-2026-9430
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 · uneditedA vulnerability was determined in Tenda F1202 1.2.0.20(408). Affected by this issue is the function formGstDhcpSetSer of the file /goform/GstDhcpSetSerof. Executing a manipulation of the argument dips can lead to stack-based buffer overflow. It is possible to launch the attack remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceStack-based buffer overflow in Tenda F1202 router firmware 1.2.0.20(408). The formGstDhcpSetSer function in /goform/GstDhcpSetSerof processes the 'dips' argument without proper bounds checking, allowing remote attackers to overflow a stack buffer via specially crafted HTTP requests.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the router label or access the web interface and look for the model number (F1202) in the system info or status pageAffected if The device is not a Tenda F1202 router, then it is not affected by this specific CVE
-
Determine the firmware versionAccess the router web interface, navigate to System Settings or Administration section, and locate the firmware version. Alternatively, check the vendor support page for the F1202 and compare your installed version to any listed versions that address this vulnerabilityAffected if The installed firmware version is older than the patched version that addresses CVE-2026-9430
-
Verify web interface accessibilityAttempt to access the router web interface over HTTP/HTTPS from the local network using the router's IP address (commonly 192.168.0.1 or 192.168.1.1)Affected if The web interface is accessible and responds, meaning the vulnerable endpoint could potentially be reached
-
Test for vulnerable endpoint exposureSend a crafted HTTP POST request to http://<router-ip>/goform/GstDhcpSetSerof with the 'dips' parameter containing an overly long string (e.g., 200+ characters). Use a tool like curl: curl -X POST -d 'dips=AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA...' http://192.168.0.1/goform/GstDhcpSetSerofAffected if The router accepts the request and does not properly sanitize the 'dips' parameter, which could indicate the vulnerability is present
If you are running a Tenda F1202 router with a firmware version that has not been patched for CVE-2026-9430 and the router web interface is accessible, your 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.
From vendor dataApply vendor firmware patch when available; until then, restrict administrative interface access to trusted networks only using firewall rules or VPN, as the vulnerability is remotely exploitable without authentication.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9430 — 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-2026-9430 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