# CVE-2025-27137: Dependency-Track vulnerable to local file inclusion via custom notification templates

> Attackers with SYSTEM_CONFIGURATION permission can read sensitive local files via Pebble template include tags, leaking information like /etc/passwd.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Feb 2025
- **Updated:** 25 Feb 2025

## What is CVE-2025-27137?

CVE-2025-27137 is a medium-severity path traversal vulnerability in DependencyTrack dependency-track, published on 24 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Dependency-Track is a component analysis platform that allows organizations to identify and reduce risk in the software supply chain. Dependency-Track allows users with the `SYSTEM_CONFIGURATION` permission to customize notification templates. Templates are evaluated using the Pebble template engine. Pebble supports an `include` tag, which allows template authors to include the content of arbitrary files upon evaluation. Prior to version 4.12.6, users of Dependency-Track with the `SYSTEM_CONFIGURATION` permission can abuse the `include` tag by crafting notification templates that `include` sensitive local files, such as `/etc/passwd` or `/proc/1/environ`. By configuring such a template for a notification rule (aka "Alert"), and having it send notifications to a destination controlled by the actor, sensitive information may be leaked. The issue has been fixed in Dependency-Track 4.12.6. In fixed versions, the `include` tag can no longer be used. Usage of the tag will cause template evaluation to fail. As a workaround, avoid assigning the `SYSTEM_CONFIGURATION` permission to untrusted users. The `SYSTEM_CONFIGURATION` permission per default is only granted to members of the `Administrators` team. Assigning this permission to non-administrative users or teams is a security risk in itself, and highly discouraged.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2025-27137 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27137 is a medium-severity path traversal vulnerability in DependencyTrack dependency-track, published on 24 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27137 exists.

Affected product: DependencyTrack dependency-track. 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-27137/ (Markdown: https://insights.sbomify.com/CVE-2025-27137/index.md)
```

## Sources

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

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