Skip to main content
← Vulnerabilities

TOTOLINK A950RG Multi-SSID Configuration cstecgi.cgi delWiFiMultipleConfig stack-based overflow

Affects TOTOLINK A950RG firmware V4.1.2cu.5268_B20221104 and requires a valid session token for the handlers. No fix is listed in the checked facts.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

9.4CriticalCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. Affects TOTOLINK A950RG firmware V4.1.2cu.5268_B20221104 Requires a valid session token for the handlers

22Pcve.now Index 22 of 100 · methodology v3 · provisional
  • Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Reach: unknown (data gap). No tracked technology or package matched
  • Severity9.4/10CVSS 9.4
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 72 if added to CISA KEV
  • Would score about 67 if CISA's SSVC rates exploitation active
  • Would score about 29 if CISA's SSVC rates it automatable

CVE-2026-121599 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.4 (critical) and affects A950RG; no fixed version is listed yet.

Published
Last modified
Published
Not listed in CISA KEV
0.47% · 40th percentile
22/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post

Summary

The TOTOLINK A950RG router firmware, specifically its web management interface (cstecgi.cgi) used for Multi-SSID wireless configuration, is affected. A remote attacker could exploit a memory handling flaw in this interface to overflow a buffer, which could potentially allow them to crash the device or take control of it.

Read the original description

A vulnerability was detected in TOTOLINK A950RG 4.1.2cu.5268_B20221104. Affected is the function setWiFiMultipleConfig/delWiFiMultipleConfig of the file /cgi-bin/cstecgi.cgi of the component Multi-SSID Configuration. The manipulation of the argument wepkey2/wepkey3 results in stack-based buffer overflow. It is possible to launch the attack remotely. The exploit is now public and may be used.

What to do

  • Check whether your setup matches what the bug needs.

    Affects TOTOLINK A950RG firmware V4.1.2cu.5268_B20221104 Requires a valid session token for the handlers
  • Workaround: The checked facts give no fix and no workaround. The only access condition listed is the requirement for a valid session token for the handlers.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Affected versions

  • TOTOLINK A950RG

    4.1.2cu.5268_B20221104

Evidence 6

  1. Advisory
  2. Advisory
  3. Advisory
  4. Advisory
  5. Exploit
  6. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

FAQ

Questions about CVE-2026-121599

Is CVE-2026-121599 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A key value of 129 bytes or more overflows a stack buffer in the multi-SSID handlers, overwriting the saved return address. That can redirect control flow, which the advisory describes as a path to code execution through a ROP chain.Source: gist.github.com

Which versions are affected by CVE-2026-121599?

A950RG: version 4.1.2cu.5268_B20221104.Source: cve.now feed data

Am I affected, and how do I check?

The listed affected firmware is TOTOLINK A950RG V4.1.2cu.5268_B20221104, and the handlers require a valid session token. To check a device, compare its firmware version in the router's admin interface against that string.Source: gist.github.com

How do I fix CVE-2026-121599?

The checked facts name no fixed version and no workaround, so no upgrade target can be given from them.Source: gist.github.com

What if there's no patch?

The checked facts give no fix and no workaround. The only access condition listed is the requirement for a valid session token for the handlers.Source: gist.github.com