# CVE-2026-108013: HCL BigFix Platform is affected by security vulnerability around intermediate CA certificate bundle (CVE ID)


- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 24 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** GHSA-x7j6-r59g-9w4v

## What is CVE-2026-108013?

CVE-2026-108013 is a medium-severity vulnerability in HCL Software BigFix Platform, published on 24 Oct 2026. 

### Official description

BigFix Platform uses Mozilla CA certificate bundle (PEM). Versions of the bundle dated before 2026/10/20 still trust certificates whose private keys have been compromised. When BigFix Platform validates servers using such a bundle, an on-path attacker can impersonate remote servers and tamper with files downloaded by the application. The issue is resolved by using bundle version 2026/10/20 or later. The fixed bundle is available starting from BES Support v1520.

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


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

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

## Is CVE-2026-108013 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-108013 is a medium-severity vulnerability in HCL Software BigFix Platform, published on 24 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-108013 in the wild and no public exploit code.

Affected product: HCL Software BigFix Platform. 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-108013/ (Markdown: https://insights.sbomify.com/CVE-2026-108013/index.md)
```

## Sources

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

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