CVE-2026-38065
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 · uneditedTenda 5G03 V05.03.02.04 (Version 1.0) is vulnerable to Command injection in the function action_ims_on_with_apn via the ims_apn parameter.
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 confidenceThe Tenda 5G03 router firmware V05.03.02.04 contains a command injection vulnerability in the action_ims_on_with_apn function. The ims_apn parameter is directly used in a system command execution context without proper input sanitization, allowing an attacker to inject arbitrary shell commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 device modelAccess the router web management interface and check the device information page, or log into the router via SSH and check /proc/cpuinfo or similar for model identificationAffected if The device is not a Tenda 5G03 router, then it is not affected by this specific CVE
-
Check the firmware versionIn the router web interface, navigate to System Settings > Firmware Upgrade or Administration > Device Info to view the firmware version. Alternatively, check via CLI if accessibleAffected if The firmware version is not V05.03.02.04 (or if the version cannot be determined to be different from this specific affected version)
-
Verify web management interface accessibilityAttempt to access the router web interface on the default IP (typically 192.168.0.1 or 192.168.1.1) via HTTP/HTTPSAffected if The web interface is exposed to untrusted networks (such as WAN/Internet), which would allow remote exploitation
-
Check if IMS/5G functionality is enabledIn the router web interface, look for IMS settings, 5G settings, or mobile network configuration sections where the ims_apn parameter would be usedAffected if The device has IMS or mobile network configuration features exposed and accessible through the web interface
The device is affected only if it is a Tenda 5G03 router running firmware V05.03.02.04 with the web management interface accessible and IMS/mobile network configuration features enabled.
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 dataRestrict access to the device's web management interface from untrusted networks immediately. The vendor should release a firmware update that implements proper input validation and escaping on the ims_apn parameter before passing it to any system call.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-38065 — 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-38065 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