{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-2053 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-2053 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-2053 is a high-severity server-side request forgery vulnerability in Wso2 Api Manager, published on 26 Jun 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-2026-2053 and fix it if it is affected.\n\nWhat it is: CVE-2026-2053 is a high-severity server-side request forgery vulnerability in Wso2 Api Manager, published on 26 Jun 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-2026-2053 in the wild and no public exploit code.\n\nAffected product: Wso2 Api Manager. 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-2026-2053/ (Markdown: https://insights.sbomify.com/CVE-2026-2053/index.md)","id":"CVE-2026-2053","markdown":"https://insights.sbomify.com/CVE-2026-2053/index.md","name":"CVE-2026-2053","record":{"aliases":["GHSA-r865-x64g-f9mm"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"API Management Platform","requires_auth":"none","summary":"Unauthenticated attackers can exploit WS-Addressing header validation flaws to force the server to make requests to arbitrary internal or external destinations.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"WSO2","cpe":[{"product":"api_manager","vendor":"wso2"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"The WSO2 API Manager's message flow component, when processing WS-Addressing headers, does not sufficiently validate or restrict user-controlled input within these headers. This omission allows an attacker to manipulate WS-Addressing headers to specify arbitrary destinations for server-initiated requests.\n\nSuccessful exploitation allows an unauthenticated attacker to control the destination of server-initiated requests originating from the WSO2 API Manager. This direct control can enable unauthorized access to internal network resources or services that would typically be inaccessible from external networks.","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":"Unauthenticated Server-Side Request Forgery via WS-Addressing in WSO2 API Manager","id":"CVE-2026-2053","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"wso2:api_manager","products":["wso2:api_manager"],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"D-Link DIR-605L/DIR-619L Wifi Setting information disclosure","id":"CVE-2026-2054"},"packages":[],"prev":{"headline":"Widget Options \u003c= 4.2.2 - Authenticated (Contributor+) Remote Code Execution via Display Logic","id":"CVE-2026-2052"},"products":["WSO2 API Manager"],"published":"2026-06-26","related":[{"cvss_score":9.8,"headline":"WSO2 Multiple Products Unrestrictive Upload of File","id":"CVE-2022-29464","kev_date_added":"2022-04-25","published":"2022-04-18"},{"cvss_score":9.8,"headline":"Incorrect Authorization in Multiple WSO2 Products via Account Recovery SOAP Admin Service Leading to Account Takeover","id":"CVE-2024-6914","kev_date_added":null,"published":"2025-05-22"},{"cvss_score":9.8,"headline":"WSO2 API Manager vulnerable to SSRF","id":"CVE-2020-13226","kev_date_added":null,"published":"2020-05-20"},{"cvss_score":9.1,"headline":"An XML External Entity (XXE) vulnerability in Multiple WSO2 Products","id":"CVE-2025-2905","kev_date_added":null,"published":"2025-05-05"},{"cvss_score":9.1,"headline":"XML external entity in n/a","id":"CVE-2021-42646","kev_date_added":null,"published":"2022-05-11"},{"cvss_score":9.1,"headline":"XML external entity in n/a","id":"CVE-2020-24589","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":9.1,"headline":"XML external entity in n/a","id":"CVE-2020-24590","kev_date_added":null,"published":"2020-08-21"}],"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-06-26","vendors":["WSO2"]},"summary":"Unauthenticated attackers can exploit WS-Addressing header validation flaws to force the server to make requests to arbitrary internal or external destinations.","url":"https://insights.sbomify.com/CVE-2026-2053/"}