dbcve.org
F3 FirmwareOperating system · Tenda

CVE-2026-27514

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-23
Fix available
A fix is available. Upgrade to after 12.01.01.55_multi or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Shenzhen Tenda F3 Wireless Router firmware V12.01.01.55_multi contains a sensitive information exposure vulnerability in the configuration download functionality. The configuration download response includes the router password and administrative password in plaintext. The endpoint also omits appropriate Cache-Control directives, which can allow the response to be stored in client-side caches and recovered by other local users or processes with access to cached browser data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Tenda F3 router firmware V12.01.01.55_multi has a sensitive information exposure vulnerability in its configuration download functionality. The endpoint returns the router's administrative password in plaintext within the configuration file response. Additionally, the missing Cache-Control headers allow browsers to cache this sensitive response, enabling local attackers to recover credentials from cached browser data.

MitigationImplement password hashing or encryption for stored credentials in configuration files, add no-store/no-cache Cache-Control headers to prevent caching of sensitive responses, and implement proper authentication/authorization checks for configuration download endpoints.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
F3 FirmwareOperating system
Affected:<= 12.01.01.55_multi

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Check the device label or web admin interface for the model name. The Tenda F3 is a 300Mbps Wireless N Router.
    Affected if The device is not a Tenda F3 router, then this specific CVE does not apply.
  2. Determine the firmware version
    Access the router's web admin interface (typically at 192.168.0.1) and navigate to System Settings or Status page to view the firmware version. Alternatively, check the version string in the firmware file if you have direct access.
    Affected if The installed firmware version is 12.01.01.55_multi or any version lower than this, meaning the firmware is at or below the affected version.
  3. Locate the configuration download endpoint
    Access the router's web admin interface and look for a configuration backup or export feature, often found under System Settings, Administration, or Maintenance menus. This is typically a button or link to download the router configuration file.
    Affected if The configuration download functionality exists and is accessible without additional authentication beyond the standard login.
  4. Inspect the downloaded configuration file for plaintext credentials
    Download the router configuration file (usually a .bin, .cfg, or .conf file) and open it in a text editor. Search for the admin password or related keywords to see if the router's administrative password appears in plaintext.
    Affected if The configuration file contains the router's admin password in plaintext (unhashed, unencrypted), indicating the sensitive information exposure vulnerability is present.
  5. Verify Cache-Control headers on configuration response
    Use browser developer tools (Network tab) or a command-line tool like curl with -I flag to examine the HTTP response headers when accessing the configuration download endpoint. Look for Cache-Control headers in the response.
    Affected if The response lacks Cache-Control headers with no-store or no-cache directives, meaning the sensitive configuration can be cached by browsers.

You are affected if you have a Tenda F3 router running firmware version 12.01.01.55_multi or lower, and the configuration download feature returns the admin password in plaintext without proper Cache-Control headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 12.01.01.55_multi
Interim mitigation

Implement password hashing or encryption for stored credentials in configuration files, add no-store/no-cache Cache-Control headers to prevent caching of sensitive responses, and implement proper authentication/authorization checks for configuration download endpoints.

Fix this in F3 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27514 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27514 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data