VulnerabilityPublished 22 Oct 2025

CVE-2025-62772: Mercku M6a · Authentication Bypass by Primary Weakness

Affects Mercku M6aSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

3.1Low

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

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

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

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

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

Attack Vector: Adjacent: The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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: None: There is no loss of confidentiality within 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 Oct 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 26 Oct 2026.

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 or the CVSS exploit maturity 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
Mercku M6a	Affected =0	Fixed in–

AI-suggested

Monitor Mercku’s official communications for firmware updates addressing this vulnerability and apply patches promptly once available.
Implement network segmentation to isolate Mercku M6a devices from critical systems, limiting the impact of potential unauthorized access.
Enforce strict access controls and logging on device management interfaces to detect unusual login patterns or token reuse.
Use VPNs or secure tunnels for remote management to reduce the risk of token interception.
Regularly rotate session tokens or force re-authentication by rebooting devices or restarting management services where possible.
Employ network intrusion detection systems (NIDS) to monitor for suspicious activity targeting Mercku devices.
Educate network administrators about the risks of long-lived session tokens and encourage vigilance in credential management.
Consider alternative devices or vendors with stronger session management policies for high-security environments.

Description

On Mercku M6a devices through 2.1.0, session tokens remain valid for at least months in some cases.

Impact

For European organizations, the primary impact of CVE-2025-62772 lies in the potential unauthorized access to Mercku M6a devices due to long-lived session tokens. This could allow attackers to bypass authentication controls and modify device settings, potentially undermining network integrity and security posture. While the vulnerability does not directly compromise confidentiality or availability, unauthorized configuration changes could lead to degraded network performance or exposure to further attacks. Organizations relying on these devices for critical network infrastructure or remote access may face increased risk of lateral movement by attackers. The low CVSS score suggests limited immediate risk, but the persistence of valid tokens over months increases the attack window, especially in environments with weak monitoring or token management. European entities with Mercku devices deployed in sensitive or high-security contexts should consider this vulnerability a moderate operational risk. The lack of known exploits reduces urgency but does not eliminate the threat, as attackers could develop methods to capture tokens through other means such as network sniffing or social engineering.

CWE-305Authentication Bypass by Primary Weakness (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The authentication algorithm is sound, but the implemented mechanism can be bypassed as the result of a separate weakness that is primary to the authentication error.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (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 29 Oct 2025, 04:39 UTC

WeaknessesCWE-305

Technical details

References

Community reviews

Related threats