Skip to content
major vulnerability· requires attention

Affects HCL BigFix AEX, an enterprise endpoint/patch management product; exploitation can expose data or compromise managed systems across organizations.

Applications

CVE-2026-67073

8.6
High
EPSS n/aOct 29, 2026

Unrestricted file upload and access-control flaw in HCL BigFix AEX allowing data theft or system compromise

common questions

Is CVE-2026-67073 being exploited?

Not confirmed. CVE-2026-67073 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-67073?

CVE-2026-67073 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-67073?

Not known from our data. No patch reference has been recorded for CVE-2026-67073, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-67073 affect?

CVE-2026-67073 affects HCL BigFix AEX. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-67073?

Apply vendor patch/mitigations, restrict upload access, and review logs

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
HCL BigFix AEX
impact

Attackers can upload malicious/unauthorized files and download uploaded content, enabling data exfiltration, unauthorized access, or system compromise.

action required

Immediate action required

affected versions
HCL Software BigFix AEX
  • affectedv13.0.0.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved