What is the CVSS score of CVE-2025-5409?

CVE-2025-5409 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L. EPSS exploitation probability: 0.2%.

Which versions of Mist are affected by CVE-2025-5409?

A critical authentication vulnerability in Mist Community Edition versions up to 4.7.1 allows attackers to bypass access controls and generate unauthorized API tokens, potentially compromising cloud…. A patch is available.

Is there a public PoC exploit available for CVE-2025-5409?

Yes, a public proof-of-concept exploit is available for CVE-2025-5409. Prioritise patching immediately. EPSS: 0.2%.

How to fix or mitigate CVE-2025-5409?

Within 24 hours: Identify all systems running Mist Community Edition versions 4.7.1 and earlier; assess whether they have internet-facing API endpoints. Within 7 days: Upgrade to version 4.7.2 or later on all affected systems. Within 30 days: Conduct audit of API token creation logs from the past 90 days to detect potential unauthorized token generation and review all active API tokens for legitimacy.

Mist CVE-2025-5409

EUVD-2025-16588 HIGH

Incorrect Privilege Assignment (CWE-266)

2025-06-01 cna@vuldb.com

Information Disclosure Mist

7.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

Low

Integrity

Low

Availability

Low

Lifecycle Timeline

EUVD ID Assigned

Mar 14, 2026 - 16:42 euvd

EUVD-2025-16588

Analysis Generated

Mar 14, 2026 - 16:42 vuln.today

Patch released

Mar 14, 2026 - 16:42 nvd

Patch available

PoC Detected

Nov 25, 2025 - 14:58 vuln.today

Public exploit code

CVE Published

Jun 01, 2025 - 22:15 nvd

HIGH 7.3

DescriptionCVE.org

A vulnerability was found in Mist Community Edition up to 4.7.1. It has been classified as critical. This affects the function create_token of the file src/mist/api/auth/views.py of the component API Token Handler. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 4.7.2 is able to address this issue. The identifier of the patch is db10ecb62ac832c1ed4924556d167efb9bc07fad. It is recommended to upgrade the affected component.

AnalysisAI

Critical improper access control vulnerability in Mist Community Edition's API Token Handler (create_token function) that allows unauthenticated remote attackers to manipulate token generation. Affected versions up to 4.7.1 are vulnerable; the vulnerability has been publicly disclosed with exploitation techniques available, and upgrading to version 4.7.2 provides the necessary fix. The CVSS 7.3 score reflects medium-to-high severity with potential for confidentiality, integrity, and availability impact.

Technical ContextAI

The vulnerability exists in src/mist/api/auth/views.py within the create_token function of Mist Community Edition's REST API authentication layer. The root cause is classified as CWE-266 (Improper Privilege Management), indicating that the token creation endpoint fails to properly enforce access controls or privilege boundaries before issuing API tokens. This suggests attackers can bypass authentication or authorization checks during token generation, potentially allowing them to obtain tokens with elevated privileges or create tokens on behalf of other users. The affected component is part of the API authentication framework, making this a critical control point in the application's security posture. CPE context: cpe:2.3:a:mist:mist_community_edition:*:*:*:*:*:*:*:* (versions <= 4.7.1).

RemediationAI

action: Immediate Upgrade; details: Upgrade Mist Community Edition to version 4.7.2 or later. Patch commit db10ecb62ac832c1ed4924556d167efb9bc07fad addresses the improper access control in the create_token function.
action: Interim Mitigation (if upgrade delayed); details: Implement network-level access controls restricting access to the API token endpoint (typically /api/auth/token or similar) to trusted networks. Consider implementing rate limiting and monitoring for abnormal token creation patterns. Review audit logs for unauthorized token creation attempts.
action: Post-Patch Verification; details: After upgrading to 4.7.2, audit all API tokens for unauthorized or suspicious creation timestamps. Revoke any tokens created during the vulnerability window. Rotate credentials for service accounts that may have been compromised.
action: Monitoring; details: Implement logging and alerting on the /api/auth/token endpoint for: (1) Failed authentication attempts, (2) Token creation without proper authorization context, (3) Unusual token creation rates, (4) Tokens created for unexpected user accounts or service principals.

CVE-2025-5409 vulnerability details – vuln.today

Back