# CVE-2025-69621: Path traversal in n/a

> Attackers can overwrite critical files via the import process, potentially leading to arbitrary code execution or information disclosure.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Feb 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-p229-4rm7-jjq6

## What is CVE-2025-69621?

CVE-2025-69621 is a high-severity path traversal vulnerability in n/a, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An arbitrary file overwrite vulnerability in the file import process of Comic Book Reader v1.0.95 allows attackers to overwrite critical internal files, potentially leading to arbitrary code execution or exposure of sensitive information.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2025-69621 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69621 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69621 is a high-severity path traversal vulnerability in n/a, published on 4 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-69621 exists.

Affected product: n/a. 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-69621/ (Markdown: https://insights.sbomify.com/CVE-2025-69621/index.md)
```

## Sources

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

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