{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53450 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-53450 is a high-severity server-side request forgery vulnerability in coturn, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53450 and fix it if it is affected.\n\nWhat it is: CVE-2026-53450 is a high-severity server-side request forgery vulnerability in coturn, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-53450 exists.\n\nAffected product: coturn. 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-53450/ (Markdown: https://insights.sbomify.com/CVE-2026-53450/index.md)","id":"CVE-2026-53450","markdown":"https://insights.sbomify.com/CVE-2026-53450/index.md","name":"CVE-2026-53450","record":{"aliases":["DEBIAN-CVE-2026-53450","GHSA-w4hf-cr3w-6h79","UBUNTU-CVE-2026-53450"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TURN/STUN server","requires_auth":"low_privilege","summary":"An authenticated attacker can bypass loopback protection to access localhost services via IPv4-mapped IPv6 addresses in TURN relay traffic.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"coturn","vendor":"coturn_project"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.13.0, coturn rejects loopback peers by default unless allow-loopback-peers is enabled, but the default loopback guard can be bypassed by using the IPv4-mapped IPv6 peer address ::ffff:127.0.0.1 in a TURN XOR-PEER-ADDRESS attribute. ioa_addr_is_loopback checks for the literal IPv6 loopback shape before IPv4-mapped IPv6 handling, so good_peer_addr does not apply the default loopback rejection and an authenticated TURN client can expose services bound only to localhost on the coturn host through TURN relay traffic. This issue is fixed in version 4.13.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Coturn: IPv4-mapped 127.0.0.1 bypasses default loopback peer protection","id":"CVE-2026-53450","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in ground-station","id":"CVE-2026-53451"},"packages":[],"prev":{"headline":"Coturn: Arbitrary File Write via CLI psd Command","id":"CVE-2026-53449"},"products":["coturn"],"published":"2026-07-10","related":[{"cvss_score":9.1,"headline":"SQL injection in coTURN","id":"CVE-2018-4056","kev_date_added":null,"published":"2019-02-05"},{"cvss_score":8.1,"headline":"Coturn: Stack buffer overflow in decode_oauth_token_gcm()","id":"CVE-2026-43994","kev_date_added":null,"published":"2026-06-18"},{"cvss_score":7.7,"headline":"Server-side request forgery in coTURN","id":"CVE-2018-4058","kev_date_added":null,"published":"2019-03-21"},{"cvss_score":7.5,"headline":"Coturn: Misaligned Memory Access in coturn STUN Attribute Parser (Remote DoS on ARM64)","id":"CVE-2026-40613","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":7.2,"headline":"Coturn: SQL Injection in HTTPS Admin Panel Delete Operations","id":"CVE-2026-53448","kev_date_added":null,"published":"2026-07-10"},{"cvss_score":7.2,"headline":"Coturn: IPv4-mapped IPv6 (::ffff:0:0/96) bypasses denied-peer-ip ACL","id":"CVE-2026-27624","kev_date_added":null,"published":"2026-02-25"}],"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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-10","vendors":["coturn"]},"summary":"An authenticated attacker can bypass loopback protection to access localhost services via IPv4-mapped IPv6 addresses in TURN relay traffic.","url":"https://insights.sbomify.com/CVE-2026-53450/"}