Skip to main content

CVE-2026-115739Trellix DLP on-prem extensions hard-coded cryptographic key

Low priorityMedium6.0EPSS 0.33%, higher than 27% of scored CVEs

CVE-2026-115739 is a hard-coded cryptographic key in Trellix DLP on-prem extensions, rated medium (6.0 on CVSS 4.0).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Received

What it is

An encryption or signing key is built into the product and shared by every install.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker sign in with credentials the vendor shipped or stored unprotected.

Is it being exploited?

There is no public report of exploitation yet. EPSS estimates a 0.33% chance of exploitation activity in the next 30 days, higher than 27% of scored CVEs.

What to do

  1. No fixed version is listed yet. Find every place Trellix DLP on-prem extensions runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. While there is no fix, review who holds accounts that can reach it.

Description from NVD

Hard-coded Cryptographic Key vulnerability exists in the DLP on-prem extensions version 11.13.1 and earlier allows a remote attacker to decrypt credentials and evidence files.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Credentials kept in code, configuration, images or firmware. The flaw sits between a stored secret and anyone who can read where it is kept.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Between a stored secret and anyone who can read where it is kept. An attacker who crosses it can sign in with credentials the vendor shipped or stored unprotected.

Questions to answer about your own systems

  • Where does Trellix DLP on-prem extensions run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.