# CVE-2026-67074: HCL BigFix AEX is affected by multiple security vulnerabilities.

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

HCL BigFix AEX is affected by a Remote Code Execution Vulnerability . It may allow attackers to execute code with the privileges of the affected application or service, potentially leading to unauthorized access, data exposure, or system compromise.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- HCL Software / BigFix AEX: v13.0.0.1 (affected). Source: CNA: HCL

## Severity and prioritization

- CVSS 3.1: 9.1 (critical); CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H; source: CNA: HCL

- CISA KEV: No listing in collected sources

- EPSS: 0.46% as of 2026-11-06; percentile 39.83%

- SSVC: exploitation none; automatable no; technical impact total; source ADP: CISA-ADP

- Weaknesses: CWE-94, CWE-78

## 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=KB0134281 (CNA: HCL)

## Provenance

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

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-67074; retrieved 2026-11-06; source updated Not reported

Revision: 5bfdcc9d3c2c1c0d791c1ee938fdcdfd88f77118b706eaeca1a28510bb7ee531

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

## 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.