dbcve.org
Identity ServerApplication · Wso2

CVE-2025-10470

HIGH · 8.6 CVSS v3.1 Published 2026-05-11
Fix available
A fix is available. Upgrade to 7.0.0.121 or later.
See remediation →
95/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
The Magic Link authentication flow accepts multiple invalid authentication requests without adequate rate limiting or resource control, leading to uncontrolled memory usage growth. This vulnerability can result in a denial-of-service condition, causing service unavailability for deployments that utilize the Magic Link authenticator. The impact is limited to these specific deployments and requires repeated invalid authentication attempts to trigger.

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

The Magic Link authentication endpoint lacks proper rate limiting, allowing attackers to send repeated invalid authentication requests. Each request consumes memory resources without proper cleanup, leading to uncontrolled memory growth and eventual denial of service when system resources are exhausted.

MitigationImplement rate limiting on the Magic Link authentication endpoint with exponential backoff or account lockout after failed attempts. Add memory usage monitoring and request throttling to prevent resource exhaustion from repeated invalid authentication attempts.

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
Identity ServerApplication
Affected:>= 7.0.0, < 7.0.0.121

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 WSO2 Identity Server installation
    Locate the WSO2 Identity Server installation directory. Common paths include /opt/wso2/is, /usr/local/wso2/is, or C:\Program Files\WSO2\Identity Server. Check for the product-is distribution or service wrapper scripts.
    Affected if WSO2 Identity Server is not installed on this system
  2. Determine the installed version
    Check the product version by viewing the <IS_HOME>/repository/components/PRODUCT_VERSION file, or run the version command from the bin directory (wso2server.bat --version on Windows or ./wso2server.sh --version on Linux).
    Affected if The installed version is >= 7.0.0 and < 7.0.0.121
  3. Verify Magic Link authentication is enabled
    Log in to the WSO2 Identity Server management console (default port 9443). Navigate to Login Adapters under Identity Providers > Resident > Inbound Authentication Configuration. Check if Magic Link is listed as an enabled authentication option.
    Affected if Magic Link authentication is enabled in the tenant configuration
  4. Inspect rate limiting configuration for Magic Link endpoint
    Check the <IS_HOME>/repository/conf/deployment.toml file for any rate limiting or throttling configurations related to /api/users/v1/me/magic-link or magiclink authentication. Look for sections containing 'throttle' or 'rate_limit' relevant to this endpoint.
    Affected if No rate limiting or throttling rules are configured for the Magic Link authentication endpoint

The system is affected if WSO2 Identity Server version 7.0.0 through 7.0.0.120 is installed with Magic Link authentication enabled and no rate limiting configured for that 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 7.0.0.121 or later
Fixed in 7.0.0.121
Interim mitigation

Implement rate limiting on the Magic Link authentication endpoint with exponential backoff or account lockout after failed attempts. Add memory usage monitoring and request throttling to prevent resource exhaustion from repeated invalid authentication attempts.

Recommended fix Moderate confidence

7.0.0.121

  1. 1. Back up the current WSO2 Identity Server deployment and configuration
  2. 2. Review the release notes for version 7.0.0.121 to understand changes and any required migration steps
  3. 3. Upgrade WSO2 Identity Server to version 7.0.0.121 or later
  4. 4. After upgrade, verify the Magic Link authenticator functionality
  5. 5. Monitor system memory usage to confirm the rate limiting remediation is effective

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

Fix this in Identity Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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