# CVE-2025-54872: onion-site-template tor Secrets Baked Into Image

> Attackers can compromise websites by accessing hardcoded Tor secrets in the onion-site-template image, leading to unauthorized control and data exposure.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-mj8m-c8w9-rw55

## What is CVE-2025-54872?

CVE-2025-54872 is a high-severity vulnerability in Vessel9817 onion-site-template, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

onion-site-template is a complete, scalable tor hidden service self-hosting sample. Versions which include commit 3196bd89 contain a baked-in tor image if the secrets were copied from an existing onion domain. A website could be compromised if a user shared the baked-in image, or if someone were able to acquire access to the user's device outside of a containerized environment. This is fixed by commit bc9ba0fd.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-54872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54872 is a high-severity vulnerability in Vessel9817 onion-site-template, published on 5 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54872 in the wild and no public exploit code.

Affected product: Vessel9817 onion-site-template. 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-54872/ (Markdown: https://insights.sbomify.com/CVE-2025-54872/index.md)
```

## Sources

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

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