Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7876 critical CVSS 9.1

Authentication Bypass in IBM Aspera HSTS for CP4I (CVE-2026-7876)

Summary

Authentication bypass in IBM Aspera HSTS for CP4I (CVE-2026-7876). Confidential information can be exposed externally.

Original description

The description as published by the source.

IBM Aspera HSTS for CP4I 1.5.1 through 1.5.19

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A weakness called CVE-2026-7876 was discovered in IBM Aspera HSTS for CP4I.
In plain terms, it is an authentication weakness that allows impersonation.
Severity is Critical (CVSS 9.1/10). If exploited, attackers can fully take over the affected system.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "IBM Aspera HSTS for CP4I CVE-2026-7876".

CVE-2026-7876 (IBM Aspera HSTS for CP4I). Severity: Critical / CVSSv3 9.1. Category: CWE-287.
Response plan:

  1. Check the vendor advisory for affected versions and the patched release.
  2. If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
  3. If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
  4. Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
    PoCs and fix commits: see the 'References' section, MITRE, and NVD.
❓ What is the problem

A weakness (CVE-2026-7876) in IBM Aspera HSTS for CP4I. In plain words, it is an authentication weakness that allows impersonation.

📍 Affected scope

Target versions of IBM Aspera HSTS for CP4I (see vendor advisory). If running in production, identify exposure immediately.

🔥 Severity

Severity: Critical (CVSS 9.1/10). If exploited, attackers can fully take over the affected system.

🔧 How to fix

Update to the patched release as listed in the vendor advisory. (Typical mitigation pattern for CWE-287)

🛡️ Workaround

If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.

🔍 Detection

Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details