CVERadar
HIGH · CVSS 4.0 8.5EPSS n/aThreat level 43

CVE-2026-129258: CVE-2026-129258: A vulnerability was identified in Tenda AC18 15.03.05.05_multi/15.03.05.19 Build 6318. Aff…

Unknown · · NVD published 2026-11-14 · posted 2026-11-14 · last modified 2026-11-14

CVE-2026-129258 at a glance

CVE-2026-129258 is a high-severity vulnerability in the affected product, with a CVSS 4.0 base score of 8.5. NVD published it on 2026-11-14 and classifies the weakness as CWE-345. NVD does not list a fixed version, so the vendor advisory is the reference for the fix. CVERadar maps 1 MITRE ATT&CK technique across Defense Impairment, inferred from the CWE and the description. Its CVERadar threat level is 43/100.

What it is

A vulnerability was identified in Tenda AC18 15.03.05.05_multi/15.03.05.19 Build 6318. Affected by this vulnerability is an unknown functionality of the file /cgi-bin/upgrade of the component Firmware Upgrade Handler. Such manipulation of the argument upgradeFile leads to insufficient verification of data authenticity. The attack may be launched remotely. The exploit is publicly available and might be used.

WeaknessCWE-345 definition
CVSS vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P/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:X/RE:X/U:X (source: VulDB)
ATT&CK tacticsDefense Impairment

Defend the Chain

The attack chain for CVE-2026-129258 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.

Threat level 43/100
Defender level 1 · 0 XP
Chain links broken: 0/1

Pick a red technique card on the board, then choose the defence that stops it.

Defend against T1553 Subvert Trust Controls Inferred

Inferred from CWE CWE-345

Patches, mitigations and detection

Fixed versions

NVD does not list a fixed version for this CVE. Use the vendor advisory below.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

No vendor-tagged reference yet; see the full reference list.

MITRE ATT&CK mitigations for this chain

  • M1038 Execution Prevention (for T1553) : System settings can prevent applications from running that haven't been downloaded through the Apple Store (or other legitimate repositories) which can help mitigate some of these issues. Also enable application control solutions such as AppLocker and/or Device Guard to block the loading of malicious content.
  • M1028 Operating System Configuration (for T1553) : Windows Group Policy can be used to manage root certificates and the <code>Flags</code> value of <code>HKLM\\SOFTWARE\\Policies\\Microsoft\\SystemCertificates\\Root\\ProtectedRoots</code> can be set to 1 to prevent non-administrator users from making further root installations into their own HKCU certificate store.
  • M1026 Privileged Account Management (for T1553) : Manage the creation, modification, use, and permissions associated to privileged accounts, including SYSTEM and root.
  • M1024 Restrict Registry Permissions (for T1553) : Ensure proper permissions are set for Registry hives to prevent users from modifying keys related to SIP and trust provider components. Components may still be able to be hijacked to suitable functions already present on disk if malicious modifications to Registry keys are not prevented.
  • M1054 Software Configuration (for T1553) : HTTP Public Key Pinning (HPKP) is one method to mitigate potential [Adversary-in-the-Middle](https://attack.mitre.org/techniques/T1557) situations where and adversary uses a mis-issued or fraudulent certificate to intercept encrypted communications by enforcing use of an expected certificate.

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    If you are not sure which network devices you even have, LayerLogix can audit your network and flag outdated firmware.

    Sources