CVE-2026-35111 · Other
NO FIX YET
HCL AION does not send a correct Cross-Origin-Resource-Policy header, so other websites can load its resources. An attacker may be able to leak data across origins under certain conditions.
first public Nov 6, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
HCL AION is an enterprise product, so exposure depends on whether a team runs it and serves resources a cross-origin page could load. The sources do not name affected versions or the specific configuration, so the exact scope is unknown.
Who cares hcl-aion
Unknown from the sources.
No fix yet, per the sources.
HCL AION is affected by a vulnerability where the Cross-Origin-Resource-Policy (CORP) header was missing or insecure, allowing application resources to be loaded by other origins. This may expose resources to cross-origin data leakage, potentially resulting in unintended behavior or security impact under certain conditions.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.