CVE-2026-4493
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 A18 Pro 02.03.02.28. The impacted element is the function sub_423B50 of the file /goform/setMacFilterCfg of the component MAC Filtering Configuration Endpoint. Executing a manipulation of the argument deviceList can lead to stack-based buffer overflow. The attack may be performed from remote. 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 confidenceA stack-based buffer overflow vulnerability exists in the Tenda A18 Pro firmware version 02.03.02.28 within the MAC filtering configuration endpoint (/goform/setMacFilterCfg). The vulnerable function sub_423B50 fails to properly bounds-check the deviceList parameter before copying it to a stack-allocated buffer, allowing remote attackers to overflow the buffer and potentially execute arbitrary code on the affected device.
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 modelAccess the device web interface or check the device label/metadata to confirm the model is Tenda A18 ProAffected if Device is not a Tenda A18 Pro unit
-
Check the installed firmware versionLog into the device web interface and navigate to the system settings or firmware upgrade page to view the current firmware version, or use commands like 'cat /proc/version' or 'ver' via telnet/SSH if availableAffected if Firmware version is 02.03.02.28 or earlier unpatched versions
-
Verify MAC filtering functionality is accessibleLog into the device web interface and check if there is a MAC filtering configuration section under Wireless or Security settingsAffected if MAC filtering feature is present and configurable in the web interface
-
Confirm network exposure of the management interfaceCheck if the device web interface (typically on ports 80 or 443) is accessible from untrusted networks by scanning the device IP from an external location or reviewing firewall rulesAffected if The web management interface is exposed to untrusted networks (WAN or public networks)
-
Check if MAC filtering is enabledIn the device web interface, verify whether MAC filtering has been configured or enabled in the wireless security or access control settingsAffected if MAC filtering is enabled or configured with a device list
The device is affected if it is a Tenda A18 Pro running firmware version 02.03.02.28 with the MAC filtering feature accessible and enabled, especially if the management interface is exposed to untrusted networks.
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 updates when available; if no patch exists, restrict network access to the device's web management interface and consider disabling MAC filtering functionality until a fix is released.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4493 — 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-4493 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