# CVE-2025-26137: Path traversal in n/a

> An unauthenticated attacker can read arbitrary system files via Local File Inclusion in Systemic Risk Value, exposing sensitive information.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-xxjw-fx2f-9c38

## What is CVE-2025-26137?

CVE-2025-26137 is a high-severity path traversal vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Systemic Risk Value <=2.8.0 is vulnerable to Local File Inclusion via /GetFile.aspx?ReportUrl=. An unauthenticated attacker can exploit this issue to read arbitrary system files by supplying a crafted file path, potentially exposing sensitive information.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Systemic-Rm Risk Value.

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

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

## Is CVE-2025-26137 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-26138](https://insights.sbomify.com/CVE-2025-26138/): Missing authorization in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26137 is a high-severity path traversal vulnerability in n/a, published on 18 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26137 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-26137/ (Markdown: https://insights.sbomify.com/CVE-2025-26137/index.md)
```

## Sources

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

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