CVE-2025-62774VulnerabilityPublished 22 Oct 2025

CVE-2025-62774: Mercku M6a · Insufficient Entropy

Affects Mercku M6aSource CVE Database V5

Not known to be exploited · CVSS 3.1 Low.

Data as of 25 Oct 2026, 19:02 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 8% 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:L/I:N/A:N

Attack Vector: Adjacent
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: 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: None: There is no loss of integrity within 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 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
Mercku M6a	Affected =0	Fixed in–

AI-suggested

1. Network Segmentation: Isolate Mercku M6a devices on separate VLANs or network segments to limit attacker access to the adjacent network required for exploitation. 2. Access Controls: Restrict management interface access to trusted IP addresses and use strong authentication methods where possible. 3. Monitoring and Logging: Implement enhanced monitoring of authentication events and session token usage to detect anomalies indicative of token prediction or session hijacking attempts. 4. Firmware Updates: Regularly check for vendor firmware updates addressing this vulnerability and apply patches promptly once available. 5. Use VPN or Encrypted Channels: Where feasible, encapsulate management traffic within VPN tunnels or encrypted channels to prevent token interception or prediction. 6. Vendor Engagement: Engage with Mercku support to obtain timelines for patches or recommended workarounds. 7. Token Regeneration Policies: If configurable, reduce session token lifetime or enforce token regeneration to limit window of exploitation. These measures go beyond generic advice by focusing on network architecture and operational controls tailored to the specific token predictability issue.

Description

On Mercku M6a devices through 2.1.0, the authentication system uses predictable session tokens based on timestamps.

Impact

For European organizations, the primary impact is the potential compromise of session confidentiality on Mercku M6a devices, which could lead to unauthorized access to network resources or management interfaces. While the vulnerability does not affect integrity or availability, session hijacking could facilitate lateral movement or data exposure within corporate or critical infrastructure networks. Organizations relying on Mercku M6a devices for wireless connectivity in sensitive environments, such as government agencies, healthcare, or finance, may face increased risk if attackers can predict session tokens. The low CVSS score reflects the difficulty of exploitation and limited impact scope, but the threat is more significant in environments with high-value assets or where network segmentation is weak. The lack of known exploits reduces immediate risk, but the predictable nature of tokens means attackers with sufficient access could exploit this vulnerability. European entities should consider this vulnerability in their risk assessments, particularly where Mercku devices are deployed in perimeter or internal network segments.

CWE-331Insufficient Entropy (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
Implementation
Determine the necessary entropy to adequately provide for randomness and predictability. This can be achieved by increasing the number of bits of objects such as keys and seeds.
OWASP Cheat Sheets
Session Management (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
V3.2.2 (opens in a new tab)
V3.2.4 (opens in a new tab)
V2.3.1 (opens in a new tab)
Attack patterns
Session Credential Falsification through Prediction (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:40 UTC

WeaknessesCWE-331

Technical details

References

Community reviews

Related threats