VulnerabilityPublished 20 Jan 2026

CVE-2025-13925: IBM Aspera Console · Sensitive Data in Logs

Affects IBM Aspera ConsoleSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.9 Medium.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

4.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 20 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBMAspera Console	Affected =3.4.7	Fixed in–

CPE configurations (1)

cpe:2.3:a:ibm:aspera_console:3.4.7:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-13925, European organizations should implement the following specific measures: 1) Restrict local privileged access strictly to trusted personnel and enforce the principle of least privilege to minimize the number of users who can access log files. 2) Review and harden file system permissions on log directories to ensure only necessary system processes and administrators can read logs. 3) Implement log management solutions that can redact or encrypt sensitive information before it is written to disk. 4) Monitor access to log files using file integrity monitoring and audit logs to detect unauthorized access attempts. 5) If possible, disable or reduce logging verbosity related to sensitive operations until a vendor patch is available. 6) Engage with IBM support to obtain updates on patch availability and apply fixes promptly once released. 7) Conduct internal audits to identify any sensitive data currently stored in logs and securely purge or archive such data. 8) Train system administrators on the risks of sensitive data exposure through logs and best practices for secure log management. These steps go beyond generic advice by focusing on access control, log sanitization, and monitoring tailored to this specific vulnerability.

Description

IBM Aspera Console 3.4.7 stores potentially sensitive information in log files that could be read by a local privileged user.

Impact

For European organizations, the primary impact of CVE-2025-13925 is the potential exposure of sensitive information stored in log files to local privileged users. This could lead to unauthorized disclosure of credentials or other confidential data, increasing the risk of further compromise or lateral movement within networks. Organizations in sectors such as finance, media, government, and critical infrastructure that rely on IBM Aspera Console for secure file transfers are particularly at risk. The vulnerability does not affect system integrity or availability directly but undermines trust in the confidentiality of sensitive operations. Given the requirement for local privileged access, the threat is more pronounced in environments where multiple administrators or users have elevated privileges, or where insider threats are a concern. The lack of a patch increases the urgency for interim mitigations. Additionally, regulatory frameworks in Europe such as GDPR impose strict requirements on protecting sensitive data, so exposure through logs could lead to compliance issues and potential fines.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7256544 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (1)

Description

AI analysisMachine-generated, updated 20 Jan 2026, 16:05 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats