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

> Unauthenticated attackers can access sensitive directories and subdirectories in Pro-Bit software, leading to information disclosure.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Apr 2026
- **Updated:** 28 Apr 2026

## What is CVE-2025-69428?

CVE-2025-69428 is a high-severity path traversal vulnerability in n/a, published on 27 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Pro-Bit before v1.77.4 allows unauthenticated attackers to directly access sensitive directory and its subdirectories.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

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


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

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

## Is CVE-2025-69428 being exploited?

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

Public exploit code:

- A critical access control vulnerability in locally deployed Pro-Bit application in versions less than v1.77.4 allows unauthenticated attackers to directly access sensitive directory and its subdirectories. (github_poc): https://github.com/jasetpen/CVE-2025-69428

## Fix prompt for AI coding agents

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

What it is: CVE-2025-69428 is a high-severity path traversal vulnerability in n/a, published on 27 Apr 2026. 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-69428 in the wild and no public exploit code.

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-69428/ (Markdown: https://insights.sbomify.com/CVE-2025-69428/index.md)
```

## Sources

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

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