{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-34207 exists.","fix":"No fix has been published for CVE-2026-34207 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34207 is a high-severity server-side request forgery vulnerability in baptisteArno typebot.io, published on 22 May 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-34207 and fix it if it is affected.\n\nWhat it is: CVE-2026-34207 is a high-severity server-side request forgery vulnerability in baptisteArno typebot.io, published on 22 May 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-34207 exists.\n\nAffected product: baptisteArno typebot.io. 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-34207/ (Markdown: https://insights.sbomify.com/CVE-2026-34207/index.md)","id":"CVE-2026-34207","markdown":"https://insights.sbomify.com/CVE-2026-34207/index.md","name":"CVE-2026-34207","record":{"aliases":["GHSA-grcc-6x37-wwgp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Chatbot builder tool","requires_auth":"low_privilege","summary":"Attackers can bypass SSRF protections in TypeBot by using hostnames that resolve to internal IPs, allowing access to cloud metadata and private networks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"TypeBot is a chatbot builder tool. In versions prior to 3.16.0, SSRF protection for Webhook / HTTP Request blocks validates only the URL string, blocked hostname literals, and literal IP formats. It does not resolve DNS before allowing the request. As a result, a hostname such as ssrf-repro.example that resolves to 127.0.0.1, 169.254.169.254, or RFC1918/private space passes validation and is later fetched by the backend HTTP client. This enables server-side request forgery to loopback, cloud metadata, and private network targets. This issue has been resolved in version 3.16.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-06-26","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-06-26T12:45:41Z","kind":"github_poc","ref":"https://github.com/0xmrma/CVE-2026-34207","stars":0,"title":"The SSRF filter checked hostname text, but the actual destination was decided later by DNS. That gap let attacker-controlled Webhook URLs reach loopback, metadata, and private network targets."}],"tier":"weaponised"},"has_fix":false,"headline":"TypeBot: SSRF Protection Bypass via DNS-Resolved Hostnames in Webhook / HTTP Request Validation","id":"CVE-2026-34207","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"SandboxJS: Sandbox integrity escape","id":"CVE-2026-34208"},"packages":[],"prev":{"headline":"Captcha Protect: Reflected XSS in challenge page via unsanitized destination rendered with text/template","id":"CVE-2026-34206"},"products":["typebot.io"],"published":"2026-05-22","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-22","vendors":["baptisteArno"]},"summary":"Attackers can bypass SSRF protections in TypeBot by using hostnames that resolve to internal IPs, allowing access to cloud metadata and private networks.","url":"https://insights.sbomify.com/CVE-2026-34207/"}