CVE-2025-36745
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 · uneditedSolarEdge SE3680H ships with an outdated Linux kernel containing unpatched vulnerabilities in core subsystems. An attacker with network or local access can exploit these flaws to achieve remote code execution, privilege escalation, or disclosure of sensitive information.
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 confidenceThe SolarEdge SE3680H solar inverter ships with an outdated Linux kernel containing multiple unpatched vulnerabilities in core kernel subsystems. Attackers with network or local access can exploit these kernel-level flaws to achieve remote code execution, escalate privileges to root, or exfiltrate sensitive data from 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>= 4.0, < 4.22CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Confirm device modelIdentify the solar inverter make and model through physical inspection, network scanning (e.g., nmap, SNMP enumeration), or the SolarEdge monitoring portal. Verify the device is specifically a SolarEdge SE3680H.Affected if The device is a SolarEdge SE3680H unit
-
Locate firmware versionAccess the device's web interface, management dashboard, or SolarEdge monitoring portal to view the current firmware version. This is typically found in the device settings, system information, or diagnostics section.Affected if Unable to retrieve the firmware version from the device or monitoring systems
-
Compare against affected rangeCheck the installed firmware version against the affected range: firmware versions greater than or equal to 4.0 and less than 4.22 are vulnerable. Note the exact version number (e.g., 4.15, 4.21).Affected if The firmware version falls within >= 4.0 and < 4.22
If the SolarEdge SE3680H is running firmware version 4.0 through 4.21, the device contains the outdated kernel with unpatched vulnerabilities and is affected by CVE-2025-36745.
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.22
Apply available vendor firmware updates for the SolarEdge SE3680H that include an updated Linux kernel with patched vulnerabilities; if no update is available, isolate the device on a restricted network segment and monitor for indicators of compromise.
4.22 or later
- Identify the current firmware version of the SolarEdge SE3680H device
- Access the device management interface or use the manufacturer's firmware update mechanism
- Upgrade the firmware to version 4.22 or later to address the outdated Linux kernel vulnerabilities
- After upgrading, verify the firmware version has been successfully applied
- Ensure the device is not directly exposed to untrusted networks to reduce attack surface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation4.0 h
- Testing12.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-36745 — 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-36745 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