# CVE-2026-5526: Tenda 4G03 Pro httpd access control

> Remote attackers can bypass access controls on the Tenda 4G03 Pro router's httpd service due to improper authorization checks.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Apr 2026
- **Updated:** 6 Apr 2026
- **Also known as:** GHSA-6j5r-7fc4-q42h

## What is CVE-2026-5526?

CVE-2026-5526 is a medium-severity missing authorization vulnerability in Tenda 4G03 Pro, published on 4 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A security flaw has been discovered in Tenda 4G03 Pro up to 1.0/1.1/04.03.01.53/192.168.0.1. Affected by this vulnerability is an unknown functionality of the file /bin/httpd. The manipulation results in improper access controls. The attack may be performed from remote. The exploit has been released to the public and may be used for attacks.

Weakness: CWE-284 (Improper Access Control), CWE-266 (Incorrect Privilege Assignment)

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

It affects 1 product.


Products: Tenda 4g03 Pro Firmware.

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

No fix has been published for CVE-2026-5526 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5526 being exploited?

There is no known exploitation of CVE-2026-5526 in the wild and no public exploit code.

## Other vulnerabilities in Tenda 4G03 Pro

- [CVE-2026-5527](https://insights.sbomify.com/CVE-2026-5527/): Tenda 4G03 Pro ECDSA P-256 Private Key server.key hard-coded key (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5526 and fix it if it is affected.

What it is: CVE-2026-5526 is a medium-severity missing authorization vulnerability in Tenda 4G03 Pro, published on 4 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5526 in the wild and no public exploit code.

Affected product: Tenda 4G03 Pro. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5526/ (Markdown: https://insights.sbomify.com/CVE-2026-5526/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5526
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5526
- OSV: https://osv.dev/vulnerability/CVE-2026-5526

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5526/
Summaries are generated and may contain mistakes; the official description above is the record.