CVE-2026-35682
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 · uneditedAnviz CX2 Lite is vulnerable to an authenticated command injection via a filename parameter that enables arbitrary command execution (e.g., starting telnetd), resulting in root‑level access.
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 Anviz CX2 Lite biometric device suffers from an authenticated command injection vulnerability in the filename parameter. An authenticated attacker can inject arbitrary OS commands through this parameter, achieving root-level command execution on the device, such as starting telnetd.
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 dataall versionsCVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Anviz CX2 Lite device on your networkScan network for Anviz CX2 Lite devices by checking device web interface banner, DHCP logs, or SNMP device enumeration. Look for vendor identifier 'Anviz' and model 'CX2 Lite' in device metadata.Affected if Device is confirmed as Anviz CX2 Lite access control device
-
Confirm management interface accessibilityPerform network port scan targeting the device. Check if HTTP/HTTPS management ports are listening and accessible from network segments that contain untrusted users or are internet-facing.Affected if Device management interface is reachable from untrusted network segments
-
Verify authentication configurationAccess device web interface and review authentication settings. Check whether default credentials are still in use or if weak/simple passwords are configured.Affected if Default credentials are active or weak authentication is configured
-
Review logs for command injection indicatorsExamine device system logs and network traffic logs for patterns indicating command injection attempts. Look for unusual command strings, shell metacharacters, or unexpected system commands in request histories.Affected if Logs show command injection attempts or unauthorized command execution
-
Check for unexpected system behaviorMonitor device for abnormal behavior such as unexpected network connections, new processes, or modifications to system files that may indicate successful exploitation.Affected if Device exhibits signs of compromise or unauthorized command execution
You are affected if you have an Anviz CX2 Lite device with its management interface accessible from an untrusted network and the device uses default or weak authentication credentials.
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 dataImplement strict input validation and sanitization for the filename parameter to prevent command injection; update to vendor-patched firmware if available; apply network segmentation and restrict administrative access as compensating controls.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-35682 — 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-35682 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