# CVE-2025-3606: Vestel AC Charger Exposure of Sensitive System Information to an Unauthorized Control Sphere

> An attacker can access sensitive files containing credentials on Vestel AC Chargers, potentially leading to further device compromise.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2025
- **Updated:** 25 Apr 2025
- **Also known as:** GHSA-7rfh-xp3x-jh62

## What is CVE-2025-3606?

CVE-2025-3606 is a high-severity vulnerability in Vestel AC Charger EVC04, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vestel AC Charger 
version 

3.75.0 contains a vulnerability that 
could enable an attacker to access files containing sensitive 
information, such as credentials which could be used to further 
compromise the device.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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


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

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

## Is CVE-2025-3606 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-3606 is a high-severity vulnerability in Vestel AC Charger EVC04, published on 24 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3606 in the wild and no public exploit code.

Affected product: Vestel AC Charger EVC04. 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-3606/ (Markdown: https://insights.sbomify.com/CVE-2025-3606/index.md)
```

## Sources

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

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