# CVE-2025-62310: HCL AION is affected by a vulnerability where encryption is not enforced for certain data transmissions or operations

> Attackers can intercept sensitive data transmitted by HCL AION due to missing encryption enforcement, risking unauthorized access to confidential information.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-87fr-h366-pw6q

## What is CVE-2025-62310?

CVE-2025-62310 is a medium-severity vulnerability in HCL AION, published on 14 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

HCL AION is affected by a vulnerability where encryption is not enforced for certain data transmissions or operations. This may expose sensitive information to potential interception or unauthorized access under specific conditions.

Weakness: CWE-319 (Cleartext Transmission of Sensitive Information)

## Which versions are affected by CVE-2025-62310?


## How do I fix CVE-2025-62310?

No fix has been published for CVE-2025-62310 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-62310 being exploited?

There is no known exploitation of CVE-2025-62310 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62310 and fix it if it is affected.

What it is: CVE-2025-62310 is a medium-severity vulnerability in HCL AION, published on 14 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-62310 in the wild and no public exploit code.

Affected product: HCL AION. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62310/ (Markdown: https://insights.sbomify.com/CVE-2025-62310/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62310
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62310
- OSV: https://osv.dev/vulnerability/CVE-2025-62310

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62310/
Summaries are generated and may contain mistakes; the official description above is the record.