dbcve.org
AionApplication · Hcl

CVE-2025-52648

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-16
Fix available
A fix is available. Upgrade to 2.1.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
HCL AION is affected by a vulnerability where offering images are not digitally signed. Lack of image signing may allow the use of unverified or tampered images, potentially leading to security risks such as integrity compromise or unintended behavior in the system

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

HCL AION is vulnerable due to the absence of digital signature verification for offering images. This means the system cannot verify the integrity or authenticity of images before deployment, potentially allowing attackers to deploy tampered or malicious images that could compromise system integrity or cause unintended behavior.

MitigationImplement digital signature verification for all offering images, ensuring only cryptographically signed images are accepted by the deployment pipeline.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AionApplication
Affected:>= 2.0, < 2.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed HCL AION version
    Locate the HCL AION installation directory and check the version information file, or run the product's version command (e.g., 'aion --version' or check the About dialog in the application). Compare the version number against the affected range: 2.0 to 2.1.1 (versions 2.0 through 2.1.1 are affected).
    Affected if The installed version is 2.0 or any version from 2.0.1 through 2.1.1.
  2. Locate offering image configuration
    Search for configuration files related to offering images in the HCL AION installation directory. Look for files named 'offering', 'image', or 'plugin' in the config or settings folders. Identify the directory path where offering images are stored or loaded from.
    Affected if The system stores or loads offering images from any configurable directory.
  3. Check for digital signature verification settings
    Examine the HCL AION configuration files and settings menus for any options related to 'signature verification', 'image validation', 'code signing', or 'integrity check'. Check both the main configuration file and any security-related settings sections.
    Affected if No signature verification option exists, or the verification feature is disabled or absent from the configuration.
  4. Inspect image loading mechanism
    Review the system's image loading logs or behavior to determine whether any cryptographic verification occurs when an offering image is loaded. Check if the loading process includes any signature validation step or rejection of unsigned images.
    Affected if Offering images are loaded without any signature validation step, or the system accepts images without verifying their digital signatures.

A user is affected if their HCL AION installation version falls between 2.0 and 2.1.1 AND the system loads offering images without performing digital signature verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.1.2 or later
Fixed in 2.1.2
Interim mitigation

Implement digital signature verification for all offering images, ensuring only cryptographically signed images are accepted by the deployment pipeline.

Recommended fix Moderate confidence

Aion 2.1.2

  1. Contact HCL support or visit support.hcl-software.com to obtain the Aion 2.1.2 upgrade package
  2. Review upgrade documentation specific to your Aion deployment mode
  3. Apply the upgrade to a test environment first to verify compatibility
  4. Deploy version 2.1.2 to production after successful testing
Caveat Unknown from provided description - verify with HCL release notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aion Scoped from the published advisory
  • Consultation8.0 h
  • Implementation32.0 h
  • Testing16.0 h
  • Review / QA8.0 h
64.0 hours of engineering $11,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $17,920.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52648 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-52648 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data