CVE-2026-47147
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 · uneditedIn EmberZNet v9.0.2 and earlier, malformed OTA requests can drive the OTA server parser into out-of-bounds reads. A limited amount of data from RAM is read back to the requester. The size and location of this data is limited. These requests must come from a device that has already joined the network. Only devices supporting the OTA Server cluster may be impacted.
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 confidenceIn EmberZNet v9.0.2 and earlier, the OTA server parser lacks proper bounds checking when processing malformed OTA requests, leading to out-of-bounds memory reads. An authenticated network device (one that has already joined) sending specially crafted OTA requests can trigger this condition, causing limited RAM data to be leaked back to the requester.
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<= 9.0.2CVSS 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
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/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 installed EmberZNet versionConsult your product documentation, firmware metadata, or check the EmberZNet library version included in your build. This is typically visible in release notes, build artifacts, or the NCP (Network Co-Processor) firmware version string.Affected if The installed version is 9.0.2 or any earlier version (e.g., 9.0.1, 9.0.0, 8.x series).
-
Confirm OTA server functionality is enabledVerify whether your EmberZNet device is configured to run an OTA (Over-The-Air) server. Check your application configuration files, NCP firmware settings, or the device runtime status for OTA server enablement.Affected if The OTA server feature is active and the device is capable of serving OTA updates to other nodes.
-
Review joined network devicesCheck the list of devices that have successfully joined your EmberZNet network. This is typically available through your network management interface, NCP command interface, or by querying the trust center neighbor table.Affected if Any devices beyond the OTA server itself are present in the joined device list, regardless of their trust status.
-
Inspect OTA request logs or trafficMonitor OTA request activity on your network, either through network traffic capture, device logs with OTA debugging enabled, or an IDS/sniffer watching for OTA cluster messages (Cluster ID 0x0019).Affected if You observe malformed OTA request packets or unusual request patterns originating from joined devices.
Your environment is affected if you are running EmberZNet version 9.0.2 or earlier AND have the OTA server enabled with any joined devices in the network.
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 dataUpdate EmberZNet to a version beyond v9.0.2 once available. Until then, restrict network join permissions to trusted devices and monitor for anomalous OTA request patterns.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47147 — 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-47147 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