CVE-2026-3828
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 · uneditedSome Hikvision switch products (discontinued since December 2023) are vulnerable to authenticated remote command execution due to insufficient input validation. Attackers with valid credentials can exploit this flaw by sending crafted packets containing malicious commands to affected devices, leading to arbitrary command execution.
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 confidenceAuthenticated remote command execution vulnerability in discontinued Hikvision switch products. Insufficient input validation allows attackers with valid credentials to send crafted packets containing malicious commands, achieving arbitrary command execution on the affected device.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 model and firmware versionAccess the device management interface or check the device label/CLI output for the exact model number and firmware version. Compare against Hikvision switch product lines discontinued in December 2023.Affected if The device is a Hikvision switch model that was discontinued in December 2023 and the firmware version falls within the vulnerable version range.
-
Verify if remote management interface is enabledCheck the device configuration for remote management or administrative access services (HTTP/HTTPS, telnet, SSH) that are exposed to network interfaces. Look for settings like 'Remote Management', 'Web Service', or similar enabling remote administrative access.Affected if Remote management or administrative interfaces are enabled and accessible from network segments accessible to potential attackers.
-
Assess credential exposure and policyReview who has access to administrative credentials for the device. Check if default credentials are in use, if credentials are shared widely, or if the device is accessible to untrusted network segments.Affected if Valid administrative credentials exist and could be obtained by an attacker, or if default credentials remain unchanged.
-
Check for suspicious command execution indicatorsReview device logs, audit trails, or network traffic logs for evidence of unexpected or unauthorized commands being executed, particularly commands containing shell metacharacters or unusual system modifications.Affected if Logs show commands that were not initiated by legitimate administrators, or unusual command patterns indicating potential exploitation.
You are affected if you operate a Hikvision switch product that was discontinued in December 2023, have remote administrative interfaces enabled, and possess credentials that could be obtained by an attacker.
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 dataSince the products are discontinued (December 2023) with no patch available, primary mitigation is replacement with supported hardware. Implement network segmentation and restrict administrative access to minimize exposure until replacement.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3828 — 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-3828 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