Skip to main content
VulnerabilityPublished

CVE-2025-48464: DuckDuckGo Browser · Information Exposure

Affects DuckDuckGo BrowserSource CVE Database V5

0

Not known to be exploited · CVSS 4.7 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
4.7Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
DuckDuckGo DuckDuckGo BrowserAffected
  • <=5.246.0
Fixed in–

AI-suggested

  1. Immediately update DuckDuckGo Browser to versions above 5.246.0 once patches are released by the vendor.
  2. Restrict local access to devices running DuckDuckGo Browser to trusted personnel only, minimizing the risk of local exploitation.
  3. Educate users about the risk of social engineering or phishing attempts that could trigger the required user interaction for exploitation.
  4. Implement endpoint security controls to detect and prevent unauthorized local access or suspicious activities related to browser data files.
  5. Monitor Sync account activity for unusual access patterns or login attempts, and enforce multi-factor authentication where possible.
  6. Consider isolating or sandboxing browsers used for sensitive activities to limit data exposure.
  7. Regularly audit and review browser extensions and configurations to reduce attack vectors.
  8. Coordinate with IT and security teams to integrate vulnerability scanning and patch management processes for browser software.

Description

Successful exploitation of the vulnerability could allow an unauthenticated attacker to gain access to a victim’s Sync account data such as account credentials and email protection information.

References

Community reviews

Loading reviews…