CVE-2025-32056VulnerabilityPublished 22 Jan 2026

CVE-2025-32056: Bosch Infotainment system ECU · Use of Predictable Algorithm in Random Number Generator

Affects Bosch Infotainment system ECUSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

Attack Vector: Physical
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: Low
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
BoschInfotainment system ECU	Affected =283C30861E	Fixed in–

AI-suggested

Given the absence of publicly available patches, European organizations should implement several practical mitigations: 1) Engage with Bosch and vehicle manufacturers to obtain and deploy firmware updates as soon as they become available. 2) Implement network segmentation within the vehicle's CAN bus architecture to isolate critical security functions and limit attacker lateral movement. 3) Deploy anomaly detection systems on CAN traffic to identify unusual patterns indicative of sniffing or replay attacks. 4) Restrict physical access to vehicle diagnostic ports and CAN interfaces to prevent unauthorized connection. 5) Educate vehicle operators and maintenance personnel about the risks of connecting unauthorized devices to the vehicle network. 6) Collaborate with automotive cybersecurity specialists to conduct penetration testing and vulnerability assessments focused on the infotainment and ECU systems. 7) Monitor threat intelligence feeds for emerging exploits targeting this vulnerability to enable rapid response.

Description

The anti-theft protection mechanism can be bypassed by attackers due to weak response generation algorithms for the head unit. It is possible to reveal all 32 corresponding responses by sniffing CAN traffic or by pre-calculating the values, which allow to bypass the protection. First identified on Nissan Leaf ZE1 manufactured in 2020.

Impact

For European organizations, particularly automotive manufacturers, suppliers, and fleet operators, this vulnerability poses a risk of unauthorized access to vehicle systems protected by the anti-theft mechanism. Attackers could bypass security controls, potentially enabling theft, unauthorized vehicle control, or manipulation of infotainment and related vehicle functions. This undermines the confidentiality and integrity of vehicle security systems, which could lead to reputational damage, financial loss, and safety risks. The impact is heightened in Europe due to the widespread adoption of electric vehicles like the Nissan Leaf and the presence of Bosch as a major automotive supplier. Additionally, regulatory requirements in Europe emphasize vehicle cybersecurity, so exploitation could lead to compliance issues. While the vulnerability does not directly affect vehicle availability, the potential for unauthorized access to vehicle systems could indirectly impact operational continuity and user safety.

CWE-1241Use of Predictable Algorithm in Random Number Generator (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The device uses an algorithm that is predictable and generates a pseudo-random number.
Architecture and Design
It is highly recommended to use a true random number generator (TRNG) to ensure the security of encryption schemes. Hardware-based TRNGs generate unpredictable, unbiased, and independent random numbers because they employ physical phenomena, e.g., electrical noise, as sources to generate random numbers.
Implementation
It is highly recommended to use a true random number generator (TRNG) to ensure the security of encryption schemes. Hardware-based TRNGs generate unpredictable, unbiased, and independent random numbers because they employ physical phenomena, e.g., electrical noise, as sources to generate random numbers.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
Attack patterns
Cryptanalysis (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 22 Jan 2026, 15:51 UTC

WeaknessesCWE-1241

Technical details

References

Community reviews

Related threats