CVE-2026-125753: ABP file read in blogging endpoint (high)

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.

Read the original 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.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional

Exploitation0/40No signal
Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
Reach?/20Unknown. No tracked technology or package matched
Severity8.2/10CVSS 8.2
No patch0/5No signal

What would change the score

Would score about 70 if added to CISA KEV
Would score about 65 if CISA's SSVC rates exploitation active
Would score about 30 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

Upgrade to a fixed version: 10.6.2, 10.7.0.
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.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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.

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.

Timeline

Nov 10, 2026, 3:22 PM UTCCVE published
Nov 10, 2026, 3:29 PM UTCFirst seen by cve.now
Nov 10, 2026, 4:40 PM UTCCISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
Nov 10, 2026, 4:40 PM UTCRecord last updated

Affected versions

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

Evidence 7

Vendor advisory · 1

Establishes: Affected and fixed versions.

Advisory
GitHub · abpframework/abp · Advisory GHSA-4x2h-f4f8-xjr6

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-125753
Record
NVD · CVE-2026-125753

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125753

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: cve.now feed data

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: vulncheck.com, github.com

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: cve.now feed data

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: vulncheck.com, github.com

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: vulncheck.com, github.com

ABP Framework before 10.6.2 and 10.7.0 Path Traversal via Blogging File Endpoints