CVE-2026-5549
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 · uneditedA vulnerability was determined in Tenda AC10 16.03.10.10_multi_TDE01. Affected by this issue is some unknown functionality of the file /webroot_ro/pem/privkeySrv.pem of the component RSA 2048-bit Private Key Handler. Executing a manipulation can lead to use of hard-coded cryptographic key . The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized.
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 · high confidenceTenda AC10 router firmware 16.03.10.10 contains a hard-coded RSA 2048-bit private key stored in the file /webroot_ro/pem/privkeySrv.pem. This private key is shipped with the firmware and can be extracted by an attacker to decrypt VPN, SSH, or other encrypted communications, or to impersonate the router in cryptographic protocols.
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= 16.03.10.10_multi_tde01CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed firmware versionAccess the router admin panel or check via telnet/SSH, then navigate to System Settings or Firmware Upgrade to view the current version. Alternatively, check the firmware file name if you have access to the firmware image.Affected if The firmware version is exactly 16.03.10.10_multi_tde01
-
Locate the private key fileAccess the router filesystem via UART, Telnet, or by extracting the firmware image. Search for the file at /webroot_ro/pem/privkeySrv.pem.Affected if The file /webroot_ro/pem/privkeySrv.pem exists in the firmware or on the device filesystem
-
Verify the key is RSA 2048-bitOpen the privkeySrv.pem file and check the key header. An RSA 2048-bit private key will begin with '-----BEGIN RSA PRIVATE KEY-----' and the key modulus will be 2048 bits (256 bytes in hexadecimal).Affected if The file contains an RSA 2048-bit private key
-
Confirm the hardcoded key is presentCompare the private key in privkeySrv.pem against known compromised key databases or verify that the same key appears in multiple firmware images from the same version.Affected if The key in privkeySrv.pem is a known hardcoded key that is identical across firmware installations
A Tenda AC10 router is affected if it runs firmware version 16.03.10.10 and contains the hardcoded RSA private key at /webroot_ro/pem/privkeySrv.pem.
Generated from the published advisory. Verify against your own configuration.
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 dataReplace the hard-coded private key with a unique, cryptographically random RSA key pair generated for each device instance. Update firmware to a patched version if available from Tenda, or consider network segmentation to limit exposure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5549 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5549 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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