CVE-2025-8206VulnerabilityPublished 26 Jul 2025Updated 28 Jul 2025

CVE-2025-8206: Comodo Dragon · Cross Site Scripting

Affects Comodo DragonSource CVE Database V5

Not known to be exploited · CVSS 2.3 Low.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 4.0 base score

2.3Low

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system 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 to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 26 Jul 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-26.

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
Comodo Dragon	Affected =134.0.6998.179	Fixed in–

AI-suggested

Given the absence of an official patch, European organizations should implement the following specific mitigations: 1) Immediately audit and identify all instances of Comodo Dragon browser usage within the organization and restrict its use where possible, especially in high-risk environments. 2) Educate users about the risks of clicking on unknown or suspicious links, emphasizing the need for caution with links received via email or messaging platforms. 3) Employ web filtering solutions to block access to known malicious URLs and implement Content Security Policy (CSP) headers on internal web applications to reduce the impact of potential XSS attacks. 4) Monitor network traffic for unusual DNS queries or suspicious activity that might indicate exploitation attempts targeting the IP DNS Leakage Detector component. 5) Consider deploying endpoint protection tools capable of detecting script injection or anomalous browser behavior. 6) Encourage users to switch to alternative, actively maintained browsers until Comodo releases a security update addressing this vulnerability. 7) Maintain up-to-date backups and incident response plans to quickly respond to any successful exploitation attempts.

Description

A vulnerability, which was classified as problematic, was found in Comodo Dragon up to 134.0.6998.179. This affects an unknown part of the component IP DNS Leakage Detector. The manipulation leads to cross site scripting. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations, the impact of this vulnerability is relatively limited but should not be dismissed. Organizations using Comodo Dragon as a browser, especially in privacy-sensitive environments, could face targeted phishing or session hijacking attacks leveraging this XSS flaw. The vulnerability could be exploited to steal session cookies, manipulate web content, or conduct social engineering attacks. While the overall risk is low due to the high complexity and required user interaction, sectors handling sensitive data such as finance, healthcare, and government could be more concerned. Additionally, organizations with remote or hybrid workforces might see increased exposure if employees use vulnerable versions of Comodo Dragon. The lack of vendor response and patch availability means organizations must rely on mitigation strategies until an official fix is released. The vulnerability does not pose a direct threat to critical infrastructure or cause system-wide disruptions but could be a vector for targeted attacks against specific users or groups.

Summary

CVE-2025-8206 is a cross-site scripting (XSS) vulnerability identified in Comodo Dragon browser versions up to 134.0.6998.179. The vulnerability resides in the IP DNS Leakage Detector component, which is responsible for detecting potential DNS leaks that could compromise user privacy. The flaw allows an attacker to inject malicious scripts remotely, potentially executing arbitrary code in the context of the victim's browser session. However, exploitation complexity is high, requiring specific conditions to be met, and no privileges or authentication are required. User interaction is necessary, as the victim must visit a crafted malicious webpage or link to trigger the vulnerability. The vulnerability has been publicly disclosed, but no patches or vendor responses have been provided. The CVSS v4.0 base score is 2.3, indicating a low severity primarily due to the high attack complexity, lack of privilege requirement, and limited impact on confidentiality and availability. The vulnerability does not affect confidentiality or availability but has a limited impact on integrity, as it allows script injection that could lead to session hijacking or phishing attacks. No known exploits are currently observed in the wild, but the public disclosure increases the risk of future exploitation attempts.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Aug 2025, 01:01 UTC

Technical details

References

Community reviews

Related threats