# CVE-2025-36743: SolarEdge SE3680H - Exposed Debug interface

> Unauthenticated attackers can access an exposed debug interface on SolarEdge SE3680H inverters to disclose system internals and execute debug commands.

- **Severity:** High 8.6 (`CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2025
- **Updated:** 6 Jan 2026
- **Also known as:** GHSA-3v8j-7v8f-5qp2

## What is CVE-2025-36743?

CVE-2025-36743 is a high-severity vulnerability in SolarEdge SE3680H, published on 12 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

SolarEdge SE3680H has an exposed debug/test interface accessible to unauthenticated actors, allowing disclosure of system internals and execution of debug commands.

## Which versions are affected by CVE-2025-36743?

It affects 1 product.


Products: Solaredge Se3680h Firmware.

## How do I fix CVE-2025-36743?

No fix has been published for CVE-2025-36743 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-36743 being exploited?

There is no known exploitation of CVE-2025-36743 in the wild and no public exploit code.

## Other vulnerabilities in SolarEdge SE3680H

- [CVE-2025-36745](https://insights.sbomify.com/CVE-2025-36745/): SolarEdge SE3680H contains Linux Kernel vulnerabilities (high 8.6)
- [CVE-2025-36744](https://insights.sbomify.com/CVE-2025-36744/): SolarEdge SE3680H - Information Exposure during Bootloader Loop (low 2.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-36743 and fix it if it is affected.

What it is: CVE-2025-36743 is a high-severity vulnerability in SolarEdge SE3680H, published on 12 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-36743 in the wild and no public exploit code.

Affected product: SolarEdge SE3680H. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-36743/ (Markdown: https://insights.sbomify.com/CVE-2025-36743/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-36743
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-36743
- OSV: https://osv.dev/vulnerability/CVE-2025-36743

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-36743/
Summaries are generated and may contain mistakes; the official description above is the record.