# CVE-2025-48464: Exposure of Sensitive Information

> Unauthenticated attackers can access sensitive Sync account data, including credentials and email protection information, in the DuckDuckGo Browser.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Oct 2025
- **Updated:** 8 Oct 2025
- **Also known as:** GHSA-4v24-3w3q-g36w

## What is CVE-2025-48464?

CVE-2025-48464 is a medium-severity vulnerability in DuckDuckGo Browser, published on 8 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-48464?


## How do I fix CVE-2025-48464?

No fix has been published for CVE-2025-48464 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-48464 being exploited?

There is no known exploitation of CVE-2025-48464 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48464 and fix it if it is affected.

What it is: CVE-2025-48464 is a medium-severity vulnerability in DuckDuckGo Browser, published on 8 Oct 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-48464 in the wild and no public exploit code.

Affected product: DuckDuckGo Browser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-48464/ (Markdown: https://insights.sbomify.com/CVE-2025-48464/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-48464
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-48464
- OSV: https://osv.dev/vulnerability/CVE-2025-48464

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-48464/
Summaries are generated and may contain mistakes; the official description above is the record.