{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68554 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-68554 is a low-severity vulnerability in coturn, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-68554 and fix it if it is affected.\n\nWhat it is: CVE-2026-68554 is a low-severity vulnerability in coturn, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-68554 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-68554/ (Markdown: https://insights.sbomify.com/CVE-2026-68554/index.md)","id":"CVE-2026-68554","markdown":"https://insights.sbomify.com/CVE-2026-68554/index.md","name":"CVE-2026-68554","record":{"aliases":["DEBIAN-CVE-2026-68554","GHSA-5538-7cxj-5jcc","UBUNTU-CVE-2026-68554"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TURN/STUN server","requires_auth":"none","summary":"On-path attackers can modify authenticated TURN requests by appending attributes after MESSAGE-INTEGRITY, bypassing integrity checks and altering server behavior.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-924","name":"Improper Enforcement of Message Integrity During Transmission in a Communication Channel"},{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Coturn is a free open source implementation of TURN and STUN Server. Prior to 4.15.0, an on-path attacker can append attributes after MESSAGE-INTEGRITY to an authenticated STUN request on plain UDP or TCP, adjust the STUN header length, and recompute the unkeyed FINGERPRINT while the original HMAC remains valid because it covers only the message prefix. Server-side parsing in src/server/ns_turn_server.c continues past MESSAGE-INTEGRITY through handle_turn_allocate(), handle_turn_create_permission(), handle_turn_refresh(), and handle_turn_command(), allowing trailing LIFETIME, XOR-PEER-ADDRESS, or ORIGIN attributes to override allocation lifetime, inject a permission, or bypass the origin check. TLS and DTLS deployments prevent this in-transit modification. This issue is fixed in version 4.15.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":"Security feature bypass in coturn","id":"CVE-2026-68554","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"coturn: Chained mobility resumes allow authenticated remote memory exhaustion","id":"CVE-2026-68555"},"packages":[],"prev":{"headline":"Coturn: Format String Injection via TURN USERNAME/REALM into hiredis Redis Command","id":"CVE-2026-68553"},"products":["coturn"],"published":"2026-08-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-08-20","vendors":["coturn"]},"summary":"On-path attackers can modify authenticated TURN requests by appending attributes after MESSAGE-INTEGRITY, bypassing integrity checks and altering server behavior.","url":"https://insights.sbomify.com/CVE-2026-68554/"}