CVE-2025-36753
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 · uneditedThe SWD debug interface on the Growatt ShineLan-X communication dongle is available by default, allowing an attacker to attain debug access to the device and to extracting secrets or domains from within the device
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 confidenceThe SWD (Serial Wire Debug) interface on the Growatt ShineLan-X communication dongle is exposed and accessible by default, providing direct debug access to the device's microcontroller. An attacker with physical or proximity access can connect to this interface to dump firmware, extract cryptographic keys, credentials, and other sensitive data stored on the device.
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>= 3.6.0.0, < 3.6.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
- 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.
-
Check the installed firmware versionAccess the device's administrative interface or use the manufacturer's diagnostic tool to retrieve the current firmware version. This is typically found in the device status or system information page.Affected if The installed firmware version is >= 3.6.0.0 and < 3.6.0.2
-
Inspect the device hardware for exposed debug headerPhysically examine the Growatt ShineLan-X dongle for a visible debug header (typically a 10-pin or 20-pin connector) or exposed test points on the PCB near the microcontroller.Affected if A debug header or test points are present and accessible on the device
-
Verify SWD interface accessibilityAttempt to connect to the device using standard SWD debugging tools (such as ST-LINK, J-Link, or OpenOCD) via the debug pins or header if present.Affected if The SWD interface responds and allows connection without requiring authentication or special flags
-
Check for disabled debug fusesConsult the device's documentation or use hardware analysis tools to read the microcontroller's configuration fuses to determine if debug access has been locked out.Affected if The debug interface is accessible and fuses are not configured to disable SWD access
A user is affected if the device runs firmware version 3.6.0.0 through 3.6.1.x (or unpatched) AND the SWD debug interface is physically present and accessible on the hardware.
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 data3.6.0.2
Disable the SWD debug interface in production firmware by configuring appropriate hardware fuses, and physically remove or disable the debug header on production units to prevent unauthorized debug access.
- 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-2025-36753 — 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-36753 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