{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101049 exists.","fix":"No fix has been published for CVE-2026-101049 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-101049 is a high-severity authentication bypass vulnerability in heymrun heym, published on 27 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-101049 and fix it if it is affected.\n\nWhat it is: CVE-2026-101049 is a high-severity authentication bypass vulnerability in heymrun heym, published on 27 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-101049 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-101049/ (Markdown: https://insights.sbomify.com/CVE-2026-101049/index.md)","id":"CVE-2026-101049","markdown":"https://insights.sbomify.com/CVE-2026-101049/index.md","name":"CVE-2026-101049","record":{"aliases":["GHSA-2m9j-ffq7-cjqc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Heym automation platform","requires_auth":"none","summary":"Remote attackers can bypass Slack signature verification to trigger workflows with owner credentials when signing secrets are missing or empty.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Heym before 0.0.53 fails to verify Slack request signatures when trigger nodes lack credential IDs or have empty signing secrets. Remote unauthenticated attackers can send forged Slack events to known webhook URLs to trigger workflows with the owner's credentials.","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.53 Slack Webhook Signature Verification Bypass","id":"CVE-2026-101049","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Heym before 0.0.53 Authentication Bypass via Telegram Webhook","id":"CVE-2026-101050"},"packages":[],"prev":{"headline":"Cloudreve before 4.17.0 SSRF via Admin.Read OAuth scope","id":"CVE-2026-101048"},"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":"partial"},"state":"PUBLISHED","updated":"2026-09-28","vendors":["heymrun"]},"summary":"Remote attackers can bypass Slack signature verification to trigger workflows with owner credentials when signing secrets are missing or empty.","url":"https://insights.sbomify.com/CVE-2026-101049/"}