# CVE-2026-66986: HCL AION is affected by multiple security vulnerabilities.

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

HCL AION is affected by a vulnerability where user sessions did not expire after a sufficient period of inactivity. An unattended authenticated session could be used by another person with access to the same system to view information or perform actions on behalf of the user, potentially resulting in unintended behavior or security impact under certain conditions.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- HCL Software / HCL AION: Version 2.7.0 (affected). Source: CNA: HCL

## Severity and prioritization

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

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-613

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

## Provenance

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

Revision: 6cffef054f074ff134a919ea0a8730817b470549726c38fb3725e25c57f1b6c3

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

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