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

CVE-2025-67229 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

How to fix or mitigate CVE-2025-67229?

Within 24 hours: Inventory all systems and applications built with ToDesktop Builder v0.32.1 and assess exposure. Within 7 days: Implement network segmentation to restrict ToDesktop traffic and deploy certificate pinning at the application level if feasible; contact ToDesktop for patch timeline and interim guidance. Within 30 days: Migrate to a patched version of ToDesktop Builder or alternative technology; conduct security audit of all applications built with vulnerable version.

Builder CVE-2025-67229

CRITICAL

Improper Certificate Validation (CWE-295)

2026-01-23 cve@mitre.org

Authentication Bypass Builder Todesktop

9.8

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-295 OWASP Top 10:2025 A07:2025 - Authentication Failures ASVS 5.0 V12 - Secure Communication Certificate validation
Impact	CVSS 9.8 — ToDesktop converts web apps to desktop applications. MITM during build enables injecting malicious code into the resulting desktop app, affecting all downstream users.
Exploit ScenarioDerived	An attacker performs a MITM attack on the network where ToDesktop Builder runs, injecting malicious code into the build pipeline. The resulting desktop application contains the attacker's payload, which executes on every end user's machine.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.

No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

ToDesktop Builder v0.32.1 has an improper certificate validation vulnerability allowing man-in-the-middle attackers to inject malicious code into desktop application builds.

Earlier versions of this analysis (1)

v1 Mar 12, 2026 - 21:54 CVSS 9.8

Certificate validation bypass in ToDesktop Builder enables supply chain attacks on desktop apps.

RemediationAI

Update ToDesktop Builder. Build in trusted network environments. Verify build artifacts with code signing.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

ToDesktop Builder v0.32.1 does not properly validate TLS certificates (CWE-295), allowing MITM attackers to intercept and modify traffic during the desktop application build process.

Know when Builder gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 9.8 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

DescriptionCVE.org

An improper certificate validation vulnerability exists in ToDesktop Builder v0.32.1 This vulnerability allows an unauthenticated, on-path attacker to spoof backend responses by exploiting insufficient certificate validation.

Executive ViewAI

Why It Matters

A critical vulnerability in ToDesktop Builder v0.32.1 allows attackers positioned on the network path to intercept and forge backend communications, potentially compromising any application built with this tool. Organizations using ToDesktop for production applications face immediate risk of data theft, unauthorized transactions, and loss of customer trust until remediation is deployed.

Business Impact: Severe

Compensating Controls

Implement network segmentation and VPN enforcement to reduce on-path attacker surface; deploy SSL/TLS inspection and certificate pinning at application level if technically feasible; restrict ToDesktop Builder deployments to isolated development environments only; monitor for suspicious backend traffic patterns; consider disabling ToDesktop-built applications in production until vendor patch is released and validated.

Threat Intelligence Overview

EPSS Score

0.0%

Top 97% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity CRITICAL

CISA KEV No

Public POC No

EPSS 0.0%

Patch available No

Active threat No

Deciding rule

CRITICAL severity

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.