{"answers":{"affected":"1 open source package ship an affected version, including safeurl.","exploited":"There is no known exploitation of CVE-2026-77866 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-77866 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-77866 is a critical server-side request forgery vulnerability in Slab safeurl, published on 15 Sep 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-77866 and fix it if it is affected.\n\nWhat it is: CVE-2026-77866 is a critical server-side request forgery vulnerability in Slab safeurl, published on 15 Sep 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-77866 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- safeurl (Hex): affected from 0.1.0; no fix listed\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-77866/ (Markdown: https://insights.sbomify.com/CVE-2026-77866/index.md)","id":"CVE-2026-77866","markdown":"https://insights.sbomify.com/CVE-2026-77866/index.md","name":"CVE-2026-77866","record":{"aliases":["EEF-CVE-2026-77866","GHSA-97fv-h8pq-9grg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir SSRF protection library","requires_auth":"none","summary":"Attackers can bypass SSRF protections in the safeurl library by using IPv6 addresses or unresolvable hosts to reach blocked internal network destinations.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"EEF","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:H/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-636","name":"Not Failing Securely"}],"description":"Server-Side Request Forgery (SSRF) vulnerability in Slab safeurl allows an attacker who controls a validated URL to reach internal network destinations the library is configured to block.\n\nOnly IPv4 addresses are matched against the reserved ranges and the blocklist. Every other address is treated as matching nothing, so a destination that is rejected in its IPv4 form is accepted when written as an IPv6 address, IPv6 entries in the blocklist never match, and a host that resolves to no IPv4 address is accepted regardless of where it points. Deployments that rely on the allowlist instead are unaffected, because there an unmatched address is rejected.\n\nThis issue affects safeurl: from 0.1.0 onward.","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":false,"headline":"SSRF protection bypass in safeurl via IPv6 addresses and unresolvable hosts","id":"CVE-2026-77866","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":1,"n_references":3,"next":{"headline":"Post Snippets \u003c= 4.2.4 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes","id":"CVE-2026-77871"},"packages":[{"ecosystem":"Hex","fixed":[],"introduced":["0.1.0"],"last_affected":[],"package":"safeurl","purl":"pkg:hex/safeurl","source":"EEF-CVE-2026-77866"}],"prev":{"headline":"'serve-expired' can bypass Unbound 'wait-limit'","id":"CVE-2026-77860"},"products":["safeurl"],"published":"2026-09-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Erlang Ecosystem Foundation","prefix":"EEF"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["Slab"]},"summary":"Attackers can bypass SSRF protections in the safeurl library by using IPv6 addresses or unresolvable hosts to reach blocked internal network destinations.","url":"https://insights.sbomify.com/CVE-2026-77866/"}