{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49410 exists.","fix":"No fix has been published for CVE-2026-49410 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49410 is a high-severity vulnerability in tinyhumansai openhuman, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49410 and fix it if it is affected.\n\nWhat it is: CVE-2026-49410 is a high-severity vulnerability in tinyhumansai openhuman, published on 16 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49410 exists.\n\nAffected product: tinyhumansai openhuman. 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-49410/ (Markdown: https://insights.sbomify.com/CVE-2026-49410/index.md)","id":"CVE-2026-49410","markdown":"https://insights.sbomify.com/CVE-2026-49410/index.md","name":"CVE-2026-49410","record":{"aliases":["GHSA-c4m9-hw7m-vv3m"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenHuman agent harness","requires_auth":"none","summary":"An attacker can hijack a local user's session via CSRF, gaining access to agent actions, memory, and Telegram messages.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"OpenHuman is an open-source agent harness available as a desktop application and Rust library. Versions before 0.56.0 allow cross-site request forgery against the unauthenticated GET /auth/telegram loopback callback because telegram_auth_handler consumes an attacker-supplied one-time Telegram login token and passes the returned JWT to credentials::ops::store_session without validating browser fetch metadata or the request origin. An attacker with an OpenHuman account can cause a user with the local core running to visit a malicious page that requests the /auth/telegram endpoint on loopback port 7788, switching the user's active local session to the attacker's backend account and exposing subsequent agent actions, memory writes, and Telegram messages associated with that session to the attacker. This issue is fixed in version 0.56.0.","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":"OpenHuman /auth/telegram CSRF allows attacker-controlled session implantation","id":"CVE-2026-49410","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Deno Node TCPWrap numeric hostname aliases bypass --deny-net resolved-IP deny checks","id":"CVE-2026-49411"},"packages":[],"prev":{"headline":"Deno: BYONM module resolution allows `package.json` main path traversal to bypass `--allow-read` restrictions","id":"CVE-2026-49406"},"products":["openhuman"],"published":"2026-10-16","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-10-19","vendors":["tinyhumansai"]},"summary":"An attacker can hijack a local user's session via CSRF, gaining access to agent actions, memory, and Telegram messages.","url":"https://insights.sbomify.com/CVE-2026-49410/"}