CVE-2026-35109 · Vendor
NO FIX YET
HCL AION serves some pages over HTTPS in a way that lets the browser or an intermediate proxy store them in a cache. Someone who can read that cache may retrieve sensitive information from the cached responses.
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.
Organisations running HCL AION where sensitive pages can end up in shared or browser caches. The sources do not name affected versions or the conditions under which caching occurs, so the exact exposure is unknown.
Not affected if unknown
Who cares enterprise, hcl-aion
Unknown from the sources.
No fix yet, per the sources.
HCL AION is affected by a vulnerability where pages served over HTTPS could be cached by the browser or intermediate proxies. Sensitive information in cached responses may be retrieved by an unauthorized user with access to the cache, 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:N/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.