# CVE-2026-115740: Server side request forgery vulnerability exists in the DLP on-prem extensions version 11.13.1 and earlier allows the file Prefix parameter


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 5 Nov 2026
- **Also known as:** GHSA-v56v-3qfh-cch5

## What is CVE-2026-115740?

CVE-2026-115740 is a medium-severity vulnerability in Trellix DLP on-prem extensions, published on 5 Nov 2026. 

### Official description

Server side request forgery vulnerability exists in the DLP on-prem extensions version 11.13.1 and earlier allows the file Prefix parameter in the OpenEventEvidenceFile.do endpoint accepts arbitrary UNC paths without validation. The server-side code attempts to open the specified file path, causing Windows to resolve the hostname and initiate SMB authentication to the attacker-controlled host.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-115740?


## How do I fix CVE-2026-115740?

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

## Is CVE-2026-115740 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-115740 and fix it if it is affected.

What it is: CVE-2026-115740 is a medium-severity vulnerability in Trellix DLP on-prem extensions, published on 5 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-115740 in the wild and no public exploit code.

Affected product: Trellix DLP on-prem extensions. 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-2026-115740/ (Markdown: https://insights.sbomify.com/CVE-2026-115740/index.md)
```

## Sources

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

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