CVE-2025-26409VulnerabilityPublished 11 Feb 2025Updated 3 Nov 2025

CVE-2025-26409: Wattsense Bridge · Missing Protection Mechanism for Alternate Hardware Interface

Affects Wattsense BridgeSource CVE Database V5

Not known to be exploited · CVSS 6.8 Medium.

Data as of 25 Oct 2026, 19:02 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 26% 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 11 Feb 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-25.

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
Wattsense Wattsense Bridge	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-26409, European organizations should immediately update all Wattsense Bridge devices to firmware version BSP 6.4.1 or later, which contains the fix for this vulnerability. Physical security controls must be enhanced to restrict unauthorized access to device PCBs, including securing device enclosures, deploying tamper-evident seals, and monitoring access to equipment rooms or installation sites. Organizations should conduct physical audits to identify devices installed in vulnerable locations and relocate or secure them as necessary. Network segmentation should be employed to isolate building automation devices from critical IT infrastructure to limit the impact of any compromise. Additionally, implement logging and monitoring to detect unusual device behavior that could indicate exploitation attempts. Regularly review and update asset inventories to ensure all affected devices are accounted for and patched. Finally, coordinate with Wattsense support for guidance on secure deployment best practices and firmware updates.

Description

A serial interface can be accessed with physical access to the PCB of Wattsense Bridge devices. After connecting to the interface, access to the bootloader is possible, as well as a Linux login prompt. The bootloader access can be used to gain a root shell on the device. This issue is fixed in recent firmware versions BSP >= 6.4.1.

Impact

For European organizations, the impact of this vulnerability is significant in environments where Wattsense Bridge devices are deployed for building automation, energy management, or critical infrastructure monitoring. An attacker with physical access could gain root control over the device, potentially leading to unauthorized data access, manipulation of device functions, or disruption of building systems such as HVAC, lighting, or energy metering. This could result in operational downtime, safety risks, and data breaches. Since the vulnerability requires physical access, the risk is elevated in locations with insufficient physical security controls or where devices are installed in publicly accessible or poorly secured areas. The compromise of these devices could also serve as a foothold for lateral movement within organizational networks, increasing the overall risk posture. Given the high confidentiality, integrity, and availability impact, organizations must prioritize remediation to prevent potential sabotage or espionage activities.

CWE-1299Missing Protection Mechanism for Alternate Hardware Interface (opens in a new tab)
Base weakness
The lack of protections on alternate paths to access control-protected assets (such as unprotected shadow registers and other external facing unguarded interfaces) allows an attacker to bypass existing protections to the asset that are only performed against the primary path.
Requirements
Protect assets from accesses against all potential interfaces and alternate paths.
Architecture and Design
Protect assets from accesses against all potential interfaces and alternate paths.
Implementation
Protect assets from accesses against all potential interfaces and alternate paths.
OWASP ASVS 4.0.3
V1.14.1 (opens in a new tab)
V1.2.3 (opens in a new tab)
V1.2.2 (opens in a new tab)
Attack patterns
USB Memory Attacks (opens in a new tab)
Functionality Bypass (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-1191On-Chip Debug and Test Interface With Improper Access Control (opens in a new tab)
Base weakness
The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface.
Architecture and Design · Separation of Privilege
If feasible, the manufacturer should disable the JTAG interface or implement authentication and authorization for the JTAG interface. If authentication logic is added, it should be resistant to timing attacks. Security-sensitive data stored in registers, such as keys, etc. should be cleared when entering debug mode.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (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 4 Nov 2025, 00:22 UTC

WeaknessesCWE-1299, CWE-1191

Technical details

References

Community reviews

Related threats