# CVE-2026-105444: dotnet eShop Ordering API OrdersApi.cs GetOrderAsync resource injection

> Attackers can manipulate OrderNumber to access unauthorized order data via improper resource identifier control in the Ordering API.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Oct 2026
- **Updated:** 6 Oct 2026
- **Also known as:** GHSA-wvg3-r236-8v4g

## What is CVE-2026-105444?

CVE-2026-105444 is a medium-severity vulnerability in dotnet eShop, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security flaw has been discovered in dotnet eShop .NET 8. The impacted element is the function GetOrderAsync of the file src/Ordering.API/Apis/OrdersApi.cs of the component Ordering API. Performing a manipulation of the argument OrderNumber results in improper control of resource identifiers. The attack is possible to be carried out remotely. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-99 (Improper Control of Resource Identifiers)

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


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

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

## Is CVE-2026-105444 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-105444 is a medium-severity vulnerability in dotnet eShop, published on 5 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-105444 in the wild and no public exploit code.

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

## Sources

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

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