# CVE-2026-12588: Denial of service in Trellix HX Console

> An attacker can cause a Denial of Service on Trellix HX Console by sending crafted data that triggers excessive resource consumption during decompression.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-h467-wgwr-q697

## What is CVE-2026-12588?

CVE-2026-12588 is a medium-severity denial of service vulnerability in Trellix HX Console, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An attacker with access to an HX 10.0.0  and previous versions, may send specially-crafted data to the HX console. The malicious detection would then trigger decompression of a large file that consumes an excessive amount of system resources thus causing a Denial of Service.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

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


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

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

## Is CVE-2026-12588 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12588 is a medium-severity denial of service vulnerability in Trellix HX Console, published on 14 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12588 in the wild and no public exploit code.

Affected product: Trellix HX Console. 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-12588/ (Markdown: https://insights.sbomify.com/CVE-2026-12588/index.md)
```

## Sources

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

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