# CVE-2025-26138: Missing authorization in n/a

> Unauthorized users can access and download files belonging to others by manipulating a predictable ID parameter in the web application.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 18 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-mfc3-vh4c-cg3g

## What is CVE-2025-26138?

CVE-2025-26138 is a medium-severity missing authorization vulnerability in n/a, published on 18 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Systemic Risk Value <=2.8.0 is vulnerable to improper access control in /RiskValue/GroupingEntities/Controls/GetFile.aspx?ID=. Uploaded files are accessible via a predictable numerical ID parameter, allowing unauthorized users to increment or decrement the ID to access and download files they do not have permission to view.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Systemic-Rm Risk Value.

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

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

## Is CVE-2025-26138 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-26137](https://insights.sbomify.com/CVE-2025-26137/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26138 is a medium-severity missing authorization vulnerability in n/a, published on 18 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26138 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-26138/ (Markdown: https://insights.sbomify.com/CVE-2025-26138/index.md)
```

## Sources

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

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