CVE-2025-10933
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 · uneditedAn integer underflow vulnerability in the Silicon Labs Z-Wave Protocol Controller can lead to out of bounds memory reads.
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 confidenceAn integer underflow vulnerability in the Silicon Labs Z-Wave Protocol Controller allows out of bounds memory reads. This occurs when the protocol controller processes certain Z-Wave network messages that cause an integer arithmetic operation to underflow, resulting in incorrect memory offset calculations and reading beyond allocated buffers.
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
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Silicon Labs Z-Wave Protocol ControllerReview system documentation, device firmware, or network device inventory to confirm the presence of Silicon Labs Z-Wave protocol software. Check firmware images, IoT device manifests, or Z-Wave controller interfaces for Silicon Labs branding or Z-Wave implementation.Affected if The environment contains a Silicon Labs Z-Wave Protocol Controller implementation in firmware, software library, or IoT device.
-
Locate the Z-Wave firmware versionAccess the device firmware through manufacturer documentation, firmware extraction from device images, or query the Z-Wave controller interface for version information. Common methods: check device web UI, serial console, MQTT topics, or manufacturer release notes.Affected if The firmware version cannot be determined or is earlier than the patched release.
-
Compare installed version to affected rangeObtain the specific firmware version string (e.g., from boot logs, firmware metadata, or Z-Wave NIF frame) and cross-reference with vendor security advisories for CVE-2025-10933 to determine if it falls within vulnerable versions.Affected if The installed version is earlier than the vendor-provided patched version for this CVE.
-
Verify Z-Wave message processing is enabledConfirm the Z-Wave protocol stack is actively processing network messages. Check if the Z-Wave controller is in inclusion/exclusion mode, handling network commands, or actively communicating with nodes. Review network traffic captures for Z-Wave frames.Affected if The Z-Wave protocol controller is operational and processing Z-Wave network messages.
The environment is affected if it contains a Silicon Labs Z-Wave Protocol Controller with a firmware version earlier than the patched release, and the Z-Wave stack is actively processing network messages.
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 dataApply the vendor-supplied firmware update from Silicon Labs that addresses the integer underflow vulnerability in the Z-Wave Protocol Controller, and validate the fix in a staging environment before production deployment.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-10933 — 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-2025-10933 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