Dependency-Track vulnerable to local file inclusion via custom notification templates
Summary
Vulnerability reported (CVE-2025-27137). Confidential information can be exposed externally. Exploitable via SYSTEM_CONFIGURATION.
Original description
The description as published by the source.
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.
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-27137 has been found.
Attackers can target a specific entry point like SYSTEM_CONFIGURATION over the network to misuse the product.
Confidential information can be exposed externally.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "CVE-2025-27137" on the vendor's site.
CVE-2025-27137 — CWE-73
Attack vector: local / no user interaction
Attack surface: SYSTEM_CONFIGURATION / include / Administrators
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-73) has been reported. Attackers reach the vulnerable code path via SYSTEM_CONFIGURATION.
Check the vendor advisory for the affected versions. Attack surface: SYSTEM_CONFIGURATION / include / Administrators.
Severity: ?. Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで影響コンポーネントを特定する。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- patch github.com
- report github.com
- web pebbletemplates.io