# CVE-2026-108018: BigFix Mobile is affected by sensitive information disclosure

Status: published. Published: 2026-11-06. Updated: 2026-11-06.

The BigFix MCM admin portal is directly accessible from the internet without VPN or network restriction.  A client-side configuration file discloses non-sensitive environment details. Exposing the configuration file publicly increases the attack surface and the risk of unauthorized access attempts.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- HCLSoftware / BigFix MCM & Mobile: <= 3.7 (affected). Source: CNA: HCL

## Severity and prioritization

- CVSS 3.1: 6.3 (medium); CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N; source: CNA: HCL

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-497

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://support.hcl-software.com/csm?id=kb_article&sysparm_article=KB0135001 (CNA: HCL)

## Provenance

- CNA: HCL: https://www.cve.org/CVERecord?id=CVE-2026-108018; retrieved 2026-11-06; source updated 2026-11-06

Revision: 489b961b446fd287ae849e642357a7444d4efed6e7236f880a90a743eeb9ff54

Canonical: https://y2.dev/cve/CVE-2026-108018

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.