dbcve.org
Aspera OrchestratorApplication · Ibm

CVE-2025-13211

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-11
Fix available
A fix is available. Upgrade to 4.1.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
IBM Aspera Orchestrator 4.0.0 through 4.1.0 could allow an authenticated user to cause a denial of service in the email service due to improper control of interaction frequency.

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 · high confidence

IBM Aspera Orchestrator versions 4.0.0 through 4.1.0 contains a rate limiting vulnerability in the email service component. An authenticated user can send excessive email requests without proper frequency controls, causing denial of service in the email service.

MitigationImplement rate limiting and request throttling on the email service endpoint to restrict the number of emails an authenticated user can send within a given time window.

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
Aspera OrchestratorApplication
Affected:>= 4.0.0, < 4.1.1

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 IBM Aspera Orchestrator version
    Access the product's administration interface or check the installed package/version information. Common methods include viewing the About section in the web UI, checking the installed RPM/DEB package, or querying the application API for version metadata.
    Affected if The installed version is 4.0.0, 4.0.1, 4.0.2, 4.0.3, 4.0.4, 4.0.5, 4.0.6, 4.0.7, 4.0.8, 4.0.9, or 4.1.0 (any version from 4.0.0 through 4.1.0 inclusive).
  2. Confirm email service component is enabled
    Access the IBM Aspera Orchestrator administration interface and navigate to the email configuration or notification settings section. Verify whether the email service/notification feature is actively configured and operational.
    Affected if The email service component is enabled and accessible to authenticated users.
  3. Inspect rate limiting configuration for email endpoint
    Examine the application configuration files or settings panel for any rate limiting, throttling, or request frequency control configurations specifically applied to the email sending functionality. Look for settings that limit the number of emails per user within a time window.
    Affected if No rate limiting controls exist, or the rate limiting is not properly enforced on the email service endpoint, allowing excessive email requests from authenticated users.

Your environment is affected if IBM Aspera Orchestrator version 4.0.0 through 4.1.0 is installed AND the email service component is enabled AND rate limiting controls are missing or not enforced on the email endpoint.

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 4.1.1 or later
Fixed in 4.1.1
Interim mitigation

Implement rate limiting and request throttling on the email service endpoint to restrict the number of emails an authenticated user can send within a given time window.

Recommended fix High confidence

IBM Aspera Orchestrator 4.1.1

  1. Back up the current IBM Aspera Orchestrator installation and configuration
  2. Download IBM Aspera Orchestrator version 4.1.1 or later from IBM Fix Central or the IBM Aspera support portal
  3. Follow the official IBM upgrade documentation for Aspera Orchestrator to install the new version
  4. After upgrade, verify the email service is functioning correctly
  5. Confirm the upgrade was successful by checking the version in the administration interface
Caveat Review IBM release notes for 4.1.1 to check for any breaking changes or required migration steps

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

Fix this in Aspera Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13211 — 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-13211 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