dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-12056

HIGH · 8.3 CVSS v4.0 Published 2025-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
88/100
Remediation priority · High
No privileges Zero-click

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 · unedited
Out-of-bounds Read in Shelly Pro 3EM (before v1.4.4) allows Overread Buffers.

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 confidence

An out-of-bounds read vulnerability in Shelly Pro 3EM devices before firmware version 1.4.4 allows an attacker to read beyond allocated buffer boundaries, potentially exposing sensitive data from memory.

MitigationUpdate Shelly Pro 3EM firmware to version 1.4.4 or later to patch the vulnerability.

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
Adjacent
Complexity
Low
Privileges
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Access the Shelly Pro 3EM web interface
    Open a web browser and navigate to the device IP address or hostname. Look for a Device Info, Status, or About section typically found in Settings or the main dashboard.
    Affected if The firmware version displayed is lower than 1.4.4
  2. Check firmware version via local REST API
    Send an HTTP GET request to http://<device-ip>/rpc/Shelly.GetDeviceInfo or similar endpoint. Examine the JSON response for the 'fw_id' or 'version' field.
    Affected if The returned version number is less than 1.4.4 or the version string indicates a build before 1.4.4
  3. Check firmware version via Shelly cloud or mobile app
    Log into the Shelly cloud account or Shelly mobile app, locate the Shelly Pro 3EM device, and view the device information section which typically displays the current firmware version.
    Affected if The listed firmware version is below 1.4.4
  4. Identify if the out-of-bounds read trigger is accessible
    Review whether the device has external network exposure or unauthenticated API endpoints that could be reached by an attacker to trigger the vulnerable code path. Check device network configuration and firewall settings.
    Affected if The device is reachable from untrusted networks and the firmware version is below 1.4.4

A Shelly Pro 3EM is affected if its installed firmware version is below 1.4.4 and the device has network exposure that could allow an attacker to trigger the out-of-bounds read.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Shelly Pro 3EM firmware to version 1.4.4 or later to patch the vulnerability.

Recommended fix High confidence

v1.4.4 or later

  1. Access the Shelly Pro 3EM device web interface or Shelly mobile application
  2. Navigate to the device Settings or Device Info section
  3. Locate the Firmware Update option
  4. Check the current firmware version (ensure it is before v1.4.4)
  5. Update the firmware to version 1.4.4 or later
  6. Verify the update was successful by confirming the new firmware version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-12056 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-12056 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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