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

> An attacker can read arbitrary files on the web server by manipulating tile request parameters in MapTiler Tileserver-php.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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:** 29 Jul 2025
- **Updated:** 20 Jan 2026
- **Also known as:** GHSA-cw3g-mjrp-g48q

## What is CVE-2025-44137?

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

### Official description

MapTiler Tileserver-php v2.0 is vulnerable to Directory Traversal. The renderTile function within tileserver.php is responsible for delivering tiles that are stored as files on the server via web request. Creating the path to a file allows the insertion of "../" and thus read any file on the web server. Affected GET parameters are "TileMatrix", "TileRow", "TileCol" and "Format"

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Maptiler Tileserver Php.

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

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

## Is CVE-2025-44137 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44137 exists.

Public exploit code:

- https://github.com/mheranco/CVE-2025-44137 (github_poc): https://github.com/mheranco/CVE-2025-44137
- MapTiler Tileserver-php v2.0 - Unauthenticated File Read (nuclei): http/cves/2025/CVE-2025-44137.yaml

## Other vulnerabilities in n/a

- [CVE-2025-44136](https://insights.sbomify.com/CVE-2025-44136/): Cross-site scripting in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44137 is a high-severity path traversal vulnerability in n/a, published on 29 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-44137 exists.

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-44137/ (Markdown: https://insights.sbomify.com/CVE-2025-44137/index.md)
```

## Sources

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

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