{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-10470 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-10470 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10470 is a high-severity denial of service vulnerability in Wso2 Identity Server, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10470 and fix it if it is affected.\n\nWhat it is: CVE-2025-10470 is a high-severity denial of service vulnerability in Wso2 Identity Server, published on 11 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-10470 in the wild and no public exploit code.\n\nAffected product: Wso2 Identity Server. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-10470/ (Markdown: https://insights.sbomify.com/CVE-2025-10470/index.md)","id":"CVE-2025-10470","markdown":"https://insights.sbomify.com/CVE-2025-10470/index.md","name":"CVE-2025-10470","record":{"aliases":["GHSA-3xrw-97cx-wwgf"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"Identity Server","requires_auth":"none","summary":"Attackers can cause service unavailability in WSO2 Identity Server by exploiting uncontrolled memory usage in the Magic Link authentication flow.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WSO2","cpe":[{"product":"identity_server","vendor":"wso2"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"The Magic Link authentication flow accepts multiple invalid authentication requests without adequate rate limiting or resource control, leading to uncontrolled memory usage growth.\n\nThis 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial-of-Service via Magic Link Authentication in WSO2 Identity Server Allows Service Unavailability","id":"CVE-2025-10470","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wso2:identity_server","products":["wso2:identity_server"],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"ZKEACMS MediaController.cs Proxy server-side request forgery","id":"CVE-2025-10471"},"packages":[],"prev":{"headline":"Path Traversal in Beyaz Computer's CityPLus","id":"CVE-2025-10468"},"products":["WSO2 Carbon MagicLink Authenticator Module","WSO2 Identity Server"],"published":"2026-05-11","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2016-4311","kev_date_added":null,"published":"2017-02-16"},{"cvss_score":8.4,"headline":"Server-Side Template Injection via Velocity Template Engine in Multiple WSO2 Products Allows Remote Code Execution","id":"CVE-2025-12107","kev_date_added":null,"published":"2026-02-19"},{"cvss_score":7.5,"headline":"XML external entity in n/a","id":"CVE-2016-4312","kev_date_added":null,"published":"2017-02-16"},{"cvss_score":7.3,"headline":"Account Lock Bypass via Magic Link or Pass Key Authentication in WSO2 Identity Server Allows Unauthorized Access","id":"CVE-2025-10908","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":6.8,"headline":"Auth bypass in WSO2 Identity Server","id":"CVE-2025-0663","kev_date_added":null,"published":"2025-09-23"},{"cvss_score":6.5,"headline":"Unauthenticated Server-Side Request Forgery (SSRF) in Multiple WSO2 Products via SOAP Admin Services","id":"CVE-2024-7073","kev_date_added":null,"published":"2025-06-02"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["WSO2"]},"summary":"Attackers can cause service unavailability in WSO2 Identity Server by exploiting uncontrolled memory usage in the Magic Link authentication flow.","url":"https://insights.sbomify.com/CVE-2025-10470/"}