# CVE-2025-32063: Enabling SSH server on Infotainment ECU

> A misconfiguration in Bosch Infotainment ECUs enables SSH and disables the firewall at startup, allowing unauthorized remote access.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A: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:** 15 Feb 2026
- **Updated:** 17 Feb 2026
- **Also known as:** GHSA-p4c6-vgj5-cp35

## What is CVE-2025-32063?

CVE-2025-32063 is a medium-severity vulnerability in Bosch Infotainment system ECU, published on 15 Feb 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

There is a misconfiguration vulnerability inside the Infotainment ECU manufactured by BOSCH. The vulnerability happens during the startup phase of a specific systemd service, and as a result, the following developer features will be activated: the disabled firewall and the launched SSH server.

First identified on Nissan Leaf ZE1 manufactured in 2020.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-32063 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-32063 is a medium-severity vulnerability in Bosch Infotainment system ECU, published on 15 Feb 2026. 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-32063 in the wild and no public exploit code.

Affected product: Bosch Infotainment system ECU. 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-32063/ (Markdown: https://insights.sbomify.com/CVE-2025-32063/index.md)
```

## Sources

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

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