Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

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

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.

Timeline

  1. ID reserved

    By VulDB

  2. Published

  3. · 2 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-5526, by who scored it
Scored byCVSSScoreVector
VulDBCNA (assigner)4.0Medium6.9CVSS: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
VulDBCNA (assigner)3.1High7.3CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:W/RC:R
VulDBCNA (assigner)3.0High7.3CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P/RL:W/RC:R
VulDBCNA (assigner)2.0High7.5AV:N/AC:L/Au:N/C:P/I:P/A:P/E:POC/RL:W/RC:UR
NVDNVD · Analyzed4.0Medium5.5CVSS: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/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
EPSS (exploitation in 30 days)
0.38% · top 68% of all CVEs (13 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: yes · Technical impact: partial
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 6.9.

Affected products

  • Tenda · 4G03 Pro

    • affected 1.0
    • affected 1.1
    • affected 04.03.01.0
    • affected 04.03.01.1
    • affected 04.03.01.2
    • affected 04.03.01.3
    • affected 04.03.01.4
    • affected 04.03.01.5
    • affected 04.03.01.6
    • affected 04.03.01.7
    • affected 04.03.01.8
    • affected 04.03.01.9
    • affected 04.03.01.10
    • affected 04.03.01.11
    • affected 04.03.01.12
    • affected 04.03.01.13
    • affected 04.03.01.14
    • affected 04.03.01.15
    • affected 04.03.01.16
    • affected 04.03.01.17
    • affected 04.03.01.18
    • affected 04.03.01.19
    • affected 04.03.01.20
    • affected 04.03.01.21
    • affected 04.03.01.22
    • affected 04.03.01.23
    • affected 04.03.01.24
    • affected 04.03.01.25
    • affected 04.03.01.26
    • affected 04.03.01.27
    • affected 04.03.01.28
    • affected 04.03.01.29
    • affected 04.03.01.30
    • affected 04.03.01.31
    • affected 04.03.01.32
    • affected 04.03.01.33
    • affected 04.03.01.34
    • affected 04.03.01.35
    • affected 04.03.01.36
    • affected 04.03.01.37
    • and 18 more

References

References4

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-5526 badge
[![CVE-2026-5526](https://cveledger.app/badge/CVE-2026-5526.svg)](https://cveledger.app/cve/CVE-2026-5526)

Record last updated .