CVE-2025-25732VulnerabilityPublished 26 Aug 2025Updated 22 Oct 2025

CVE-2025-25732: n/a

Source CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

6.8Medium

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% 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:U/C:H/I:H/A:H

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

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: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Aug 2025
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

AI-suggested

1. Implement strict physical security controls to prevent unauthorized access to RSU hardware, especially the EEPROM interface. 2. Restrict network access to RSUs using network segmentation, firewalls, and VPNs to limit exposure to trusted administrators only. 3. Monitor RSU logs and network traffic for unusual activities indicative of attempted EEPROM access or password hash modifications. 4. Coordinate with Kapsch TrafficCom for firmware updates or patches addressing this vulnerability and plan timely deployment once available. 5. Employ integrity verification mechanisms for EEPROM contents, such as cryptographic checksums or secure boot processes, to detect unauthorized modifications. 6. Conduct regular security audits and penetration testing focused on RSU devices to identify and remediate access control weaknesses. 7. Develop incident response plans specific to RSU compromise scenarios to minimize operational impact. 8. Educate operational technology (OT) personnel on the risks and signs of exploitation related to this vulnerability.

Description

CVE-2025-25732 is a medium severity vulnerability affecting Kapsch TrafficCom RIS-9160 and RIS-9260 Roadside Units (RSUs) in specific firmware versions. The flaw stems from incorrect access control in the EEPROM component, allowing attackers to overwrite stored password hashes with their own. This enables privilege escalation to root without requiring authentication or user interaction. The vulnerability impacts confidentiality, integrity, and availability of the affected RSUs. Although no known exploits are currently reported in the wild, the potential for attackers to gain full control over critical traffic infrastructure devices is significant. European organizations operating these RSUs, especially in countries with extensive intelligent transportation systems, face increased risk. Mitigation requires strict physical and network access controls, firmware updates when available, and monitoring for anomalous device behavior. Countries with widespread deployment of Kapsch RSUs, such as Germany, Austria, and the Netherlands, are most likely to be affected given their advanced traffic management deployments. The vulnerability’s CVSS score of 6.8 reflects its medium severity, balancing the high impact with the requirement for physical or network proximity to exploit.

Impact

For European organizations, the impact of CVE-2025-25732 is substantial given the role of Kapsch TrafficCom RSUs in managing traffic flow, tolling, and road safety systems. Successful exploitation could lead to unauthorized root access, enabling attackers to alter traffic signals, disable safety features, or inject false data into traffic management systems. This could cause traffic disruptions, accidents, or facilitate broader network intrusions into connected infrastructure. The confidentiality of sensitive operational data would be compromised, integrity of traffic control commands could be violated, and availability of RSUs could be disrupted, potentially leading to denial of service conditions. Given the interconnected nature of European intelligent transportation networks, a compromised RSU could serve as a foothold for lateral movement into other critical systems. The lack of known exploits currently provides a window for proactive mitigation, but the medium severity rating underscores the need for urgent attention.

Summary

CVE-2025-25732 identifies a vulnerability in the EEPROM component of Kapsch TrafficCom RIS-9160 and RIS-9260 Roadside Units (RSUs), specifically in firmware versions 3.2.0.829.23, 3.8.0.1119.42, and 4.6.0.1211.28. The root cause is incorrect access control mechanisms that permit an attacker to overwrite password hashes stored in the EEPROM memory. By replacing legitimate password hashes with attacker-controlled hashes, an adversary can escalate privileges to root level on the device. This vulnerability falls under CWE-922 (Improper Restriction of Operations within the Bounds of a Memory Buffer), indicating a failure to properly restrict access to critical memory regions. Exploitation does not require prior authentication or user interaction, but does require access to the device’s EEPROM interface, which is typically accessible via network or physical means. The CVSS v3.1 base score is 6.8, reflecting a medium severity level with high impact on confidentiality, integrity, and availability. The vulnerability affects critical infrastructure components used in intelligent transportation systems, potentially allowing attackers to manipulate traffic data, disrupt operations, or gain persistent control over RSUs. No public patches or known exploits are currently reported, but the risk remains significant due to the critical nature of the affected devices.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (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

Description

AI analysisMachine-generated, updated 29 Oct 2025, 15:23 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats