# CVE-2026-21850: 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-controlled input could be included in HTTP response headers without proper neutralization of CR/LF characters. This may allow an attacker to inject headers or split responses, 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: V 2.6.0 (affected). Source: CNA: HCL

## Severity and prioritization

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

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: exploitation none; automatable yes; technical impact partial; source ADP: CISA-ADP

- Weaknesses: CWE-113

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

## Provenance

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

Revision: 95cd9acf6b7b1a0ae792061ae05529468be960e6e45915140087e2223d231c24

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

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