CVE-2019-12266
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 · uneditedStack-based Buffer Overflow vulnerability in Wyze Cam Pan v2, Cam v2, Cam v3 allows an attacker to run arbitrary code on the affected device. This issue affects: Wyze Cam Pan v2 versions prior to 4.49.1.47. Wyze Cam v2 versions prior to 4.9.8.1002. Wyze Cam v3 versions prior to 4.36.8.32.
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 confidenceStack-based buffer overflow vulnerability in Wyze Cam firmware allows an attacker to overwrite stack memory and execute arbitrary code by sending specially crafted network requests to the affected cameras.
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< 4.49.1.47< 4.9.8.1002< 4.36.8.32CVSS 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 your Wyze Cam modelLocate the model number on the device label or check in the Wyze mobile app under Device Settings > Device InfoAffected if The device is a Wyze Cam V2, Wyze Cam V3, or Wyze Cam Pan V2
-
Check installed firmware versionOpen the Wyze mobile app, select the camera, go to Device Settings > Device Info, and note the firmware version number displayedAffected if The displayed firmware version is below 4.49.1.47 for Cam Pan V2, below 4.9.8.1002 for Cam V2, or below 4.36.8.32 for Cam V3
-
Determine network exposureReview your network configuration to determine if the camera is accessible from untrusted networks. Check router firewall rules and port forwarding settings for the camera's IP addressAffected if The camera is directly accessible from the internet or an untrusted network segment
Your environment is affected if you have a Wyze Cam V2, V3, or Pan V2 running a firmware version lower than the respective thresholds and the camera is network-accessible to potential attackers.
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.
dbcve · scoped4.9.8.10024.36.8.324.49.1.47
Update Wyze Cam v2 to version 4.9.8.1002+, Cam v3 to version 4.36.8.32+, and Cam Pan v2 to version 4.49.1.47+ via Wyze's official firmware update mechanism.
Wyze Cam Pan V2: 4.49.1.47+ | Wyze Cam V2: 4.9.8.1002+ | Wyze Cam V3: 4.36.8.32+
- Identify the Wyze camera model (Cam Pan V2, Cam V2, or Cam V3) currently deployed
- Download the firmware update from the official Wyze support website for the specific camera model
- For Wyze Cam Pan V2: Upgrade to firmware version 4.49.1.47 or later
- For Wyze Cam V2: Upgrade to firmware version 4.9.8.1002 or later
- For Wyze Cam V3: Upgrade to firmware version 4.36.8.32 or later
- Follow Wyze's official firmware update instructions, typically through the Wyze app or Wyze website
- Verify the firmware version has been successfully applied after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12266 — 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-2019-12266 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