What is the CVSS score of CVE-2025-13379?

CVE-2025-13379 has a CVSS 3.1 base score of 8.6 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L. EPSS exploitation probability: 0.1%.

How to fix or mitigate CVE-2025-13379?

Within 24 hours: Audit Aspera Console deployments to confirm versions and inventory all affected systems; restrict network access to Aspera Console to trusted IPs only. Within 7 days: Deploy WAF rules to block SQL injection patterns targeting Aspera endpoints; implement database access logging and alerting for anomalous queries. Within 30 days: Upgrade to patched version (3.4.9 or later when available); if upgrade is not possible, prepare isolated test environment and plan migration timeline.

Aspera Console CVE-2025-13379

HIGH

SQL Injection (CWE-89)

2026-02-05 psirt@us.ibm.com

SQLi IBM Aspera Console

8.6

CVSS 3.1 · NVD

View

Vulnerability Assessment

Weakness	CWE CWE-89 OWASP Top 10:2025 A05:2025 - Injection ASVS 5.0 V1 - Encoding and Sanitization Parameterized queries, prepared statements MITRE ATT&CK 2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. Sign in to read
Impact	CVSS 8.6 (HIGH). Attack vector: Network. Complexity: Low. Privileges required: None. User interaction: None. Exploitable via remote/network.
Exploit ScenarioDerived	A remote attacker could exploit this vulnerability to view, add, modify, or delete information in the back-end database.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 12, 2026

IBM Aspera Console 3.4.0 through 3.4.8 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database. [CVSS 8.6 HIGH]

RemediationAI

Monitor vendor advisories for a patch. Use parameterized queries. Implement input validation. Restrict network access to the affected service where possible.

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Classified as CWE-89 (SQL Injection). Affects Aspera Console. IBM Aspera Console 3.4.0 through 3.4.8 is vulnerable to SQL injection. A remote attacker could send specially crafted SQL statements, which could allow the attacker to view, add, modify, or delete information in the back-end database.

Know when Aspera Console gets its next vulnerability

Watch products and get an email when something new is published
Check this CVE against your own stack and servers
Exploit and PoC references, threat intelligence from 22 sources

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.6 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

Low

Availability

Low

DescriptionCVE.org

Executive ViewAI

Why It Matters

IBM Aspera Console versions 3.4.0-3.4.8 contain a critical SQL injection vulnerability (CVSS 8.6) that could allow attackers to breach, modify, or destroy database contents without authentication. Any organization running affected versions faces immediate risk of data theft, data manipulation, or operational disruption until remediation is completed.

Business Impact: High

Compensating Controls

Implement network segmentation to restrict Aspera Console access to authorized users only; deploy Web Application Firewall (WAF) rules to detect and block SQL injection payloads; enable detailed database query logging and real-time alerting; disable unnecessary Aspera Console features if possible; consider running Aspera Console in read-only mode if business operations permit; monitor vendor advisory channels for patch availability and apply immediately upon release.

Threat Intelligence Overview

EPSS Score

0.1%

Top 67% exploitable

Data Quality

3 sources

Confidence: Low

NVD

CVE.org

EPSS

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.1%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.