{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100858 exists.","fix":"No fix has been published for CVE-2026-100858 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-100858 is a high-severity server-side request forgery vulnerability in heymrun heym, published on 27 Sep 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-100858 and fix it if it is affected.\n\nWhat it is: CVE-2026-100858 is a high-severity server-side request forgery vulnerability in heymrun heym, published on 27 Sep 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-100858 exists.\n\nAffected product: heymrun heym. 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-100858/ (Markdown: https://insights.sbomify.com/CVE-2026-100858/index.md)","id":"CVE-2026-100858","markdown":"https://insights.sbomify.com/CVE-2026-100858/index.md","name":"CVE-2026-100858","record":{"aliases":["GHSA-39j3-6x3x-8rcr","GHSA-68x6-m7x2-mcgw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"heym workflow automation","requires_auth":"low_privilege","summary":"An attacker can exploit SSRF in heym workflow nodes to access internal network resources and cloud metadata by using unvalidated URLs in credentials.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":7.6,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"heym before 0.0.109 contains a server-side request forgery vulnerability in the Slack, Discord, and Crawler workflow nodes. These nodes issue HTTP requests to URLs taken from user-created credentials (webhook_url / flaresolverr_url) using an unguarded HTTP client, bypassing the SSRF egress guard that already protects the HTTP, WebSocket, and MCP nodes; the credential API validates only that the URL is non-empty. Any registered user can create a credential pointing at an internal address and execute a workflow, causing the backend to reach loopback, private, link-local, or cloud-metadata endpoints and return the full response body in the node output (non-blind SSRF).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"heym before 0.0.109 Server-Side Request Forgery via Workflow Nodes","id":"CVE-2026-100858","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Heym before 0.0.106 Credential Exfiltration via URL Override","id":"CVE-2026-100859"},"packages":[],"prev":{"headline":"AzuraCast before 0.23.4 Remote Code Execution via Liquidsoap string interpolation","id":"CVE-2026-100857"},"products":["heym"],"published":"2026-09-27","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":"total"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["heymrun"]},"summary":"An attacker can exploit SSRF in heym workflow nodes to access internal network resources and cloud metadata by using unvalidated URLs in credentials.","url":"https://insights.sbomify.com/CVE-2026-100858/"}