# CVE-2025-52645: Supply chain in AION

> Attackers can inject unverified or modified model artifacts into HCL AION due to insufficient authenticity verification, leading to integrity issues or unintended behavior.

- **Severity:** Low 1.9 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Mar 2026
- **Updated:** 16 Mar 2026
- **Also known as:** GHSA-3qgf-4qfv-p6fh

## What is CVE-2025-52645?

CVE-2025-52645 is a low-severity vulnerability in HCL AION, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

HCL AION is affected by a vulnerability where model packaging and distribution mechanisms may not include sufficient authenticity verification. This may allow the possibility of unverified or modified model artifacts being used, potentially leading to integrity concerns or unintended behaviour.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Hcltech Aion.

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

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

## Is CVE-2025-52645 being exploited?

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

## Other vulnerabilities in HCL AION

- [CVE-2025-52650](https://insights.sbomify.com/CVE-2025-52650/): HCL AION is susceptible to Inline script execution allowed in CSP vulnerability (high 8.2)
- [CVE-2025-52632](https://insights.sbomify.com/CVE-2025-52632/): HCL AION is susceptible to Missing Secure Attribute in Encrypted Session (SSL) Cookie vulnerability (medium 6.5)
- [CVE-2025-52644](https://insights.sbomify.com/CVE-2025-52644/): HCL AION is affected by a vulnerability where certain user actions are not adequately audited or logged. (medium 5.8)
- [CVE-2025-52627](https://insights.sbomify.com/CVE-2025-52627/): HCL AION is susceptible to Incorrect Permission Assignment for Critical Resource (medium 5.5)
- [CVE-2025-52624](https://insights.sbomify.com/CVE-2025-52624/): HCL AION is susceptible to Bypass of the script allow list configuration vulnerability (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52645 is a low-severity vulnerability in HCL AION, published on 16 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-52645 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-52645/ (Markdown: https://insights.sbomify.com/CVE-2025-52645/index.md)
```

## Sources

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

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