# CVE-2026-125753: ABP Framework before 10.6.2 and 10.7.0 Path Traversal via Blogging File Endpoints


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-4x2h-f4f8-xjr6, GHSA-jpw7-jxqw-m2cj

## What is CVE-2026-125753?

CVE-2026-125753 is a high-severity vulnerability in abpframework abp, published on 10 Nov 2026. 

### Official description

ABP Framework 2.9.0 before 10.6.2 and 10.7.0 pre-releases before 10.7.0 contain a path traversal vulnerability in DefaultBlobFilePathCalculator that allows unauthenticated attackers to access files outside the blob container. Attackers can send %5C-encoded backslashes through the Blogging api/blogging/files/{name} endpoint on Windows hosts to read files like appsettings.json containing signing keys and connection strings.

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

## Which versions are affected by CVE-2026-125753?


## How do I fix CVE-2026-125753?

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

## Is CVE-2026-125753 being exploited?

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

Public exploit code:

- CVE-2026-125753 — path traversal out of the blob container in ABP Framework (github_poc): https://github.com/yuwkaaa/CVE-2026-125753

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-125753 and fix it if it is affected.

What it is: CVE-2026-125753 is a high-severity vulnerability in abpframework abp, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125753 in the wild and no public exploit code.

Affected product: abpframework abp. 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-2026-125753/ (Markdown: https://insights.sbomify.com/CVE-2026-125753/index.md)
```

## Sources

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

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