{"answers":{"affected":"4 open source packages ship an affected version, including ex_webrtc.","exploited":"There is no known exploitation of CVE-2026-44700 in the wild and no public exploit code.","fix":"Upgrade ex_webrtc to a fixed version for your release line: 0.15.1 or 0.16.1.","what":"CVE-2026-44700 is a high-severity vulnerability in elixir-webrtc ex_webrtc, published on 14 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-2026-44700 and fix it if it is affected.\n\nWhat it is: CVE-2026-44700 is a high-severity vulnerability in elixir-webrtc ex_webrtc, published on 14 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-2026-44700 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ex_webrtc (Hex): affected all versions; fixed in 0.15.1\n- ex_webrtc (Hex): affected all versions; fixed in 0.15.1\n- ex_webrtc (Hex): affected from 0.16.0; fixed in 0.16.1\n- ex_webrtc (Hex): affected from 0.16.0; fixed in 0.16.1\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-44700/ (Markdown: https://insights.sbomify.com/CVE-2026-44700/index.md)","id":"CVE-2026-44700","markdown":"https://insights.sbomify.com/CVE-2026-44700/index.md","name":"CVE-2026-44700","record":{"aliases":["GHSA-qwfw-ggxw-577c"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir WebRTC library","requires_auth":"none","summary":"Missing DTLS fingerprint validation in the Elixir WebRTC library allows man-in-the-middle attacks when combined with insecure signaling.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"Elixir WebRTC is an Elixir implementation of the W3C WebRTC API. Prior to 0.15.1 and 0.16.1, missing DTLS peer certificate fingerprint validation in the DTLS client (active) role removes one side of WebRTC's mutual authentication. The bug is not independently exploitable for media interception in standard deployments, but enables a full man-in-the-middle attack when chained with insecure signalling or a peer with similar validation gaps. This vulnerability is fixed in 0.15.1 and 0.16.1.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Elixir WebRTC: Missing DTLS peer fingerprint validation in ex_webrtc client-role handshake","id":"CVE-2026-44700","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":5,"next":{"headline":"tmp: Path Traversal via unsanitized prefix/postfix enables directory escape","id":"CVE-2026-44705"},"packages":[{"ecosystem":"Hex","fixed":["0.15.1"],"introduced":["0"],"last_affected":[],"package":"ex_webrtc","purl":null,"source":"GHSA-qwfw-ggxw-577c"},{"ecosystem":"Hex","fixed":["0.15.1"],"introduced":["0"],"last_affected":[],"package":"ex_webrtc","purl":"pkg:hex/ex_webrtc","source":"GHSA-qwfw-ggxw-577c"},{"ecosystem":"Hex","fixed":["0.16.1"],"introduced":["0.16.0"],"last_affected":[],"package":"ex_webrtc","purl":null,"source":"GHSA-qwfw-ggxw-577c"},{"ecosystem":"Hex","fixed":["0.16.1"],"introduced":["0.16.0"],"last_affected":[],"package":"ex_webrtc","purl":"pkg:hex/ex_webrtc","source":"GHSA-qwfw-ggxw-577c"}],"prev":{"headline":"LibJWT: Algorithm confusion allows JWT forgery with RSA JWK as empty-key HMAC","id":"CVE-2026-44699"},"products":["ex_webrtc"],"published":"2026-05-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-15","vendors":["elixir-webrtc"]},"summary":"Missing DTLS fingerprint validation in the Elixir WebRTC library allows man-in-the-middle attacks when combined with insecure signaling.","url":"https://insights.sbomify.com/CVE-2026-44700/"}