{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-27632 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-27632 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-27632 is a low-severity vulnerability in Talishar, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-27632 and fix it if it is affected.\n\nWhat it is: CVE-2026-27632 is a low-severity vulnerability in Talishar, published on 25 Feb 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-27632 in the wild and no public exploit code.\n\nAffected product: Talishar. 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-27632/ (Markdown: https://insights.sbomify.com/CVE-2026-27632/index.md)","id":"CVE-2026-27632","markdown":"https://insights.sbomify.com/CVE-2026-27632/index.md","name":"CVE-2026-27632","record":{"aliases":["GHSA-73mm-323r-cm3g"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Fan-made game platform","requires_auth":"low_privilege","summary":"Attackers can forge requests to perform unauthorized actions in active game sessions if users visit malicious sites while playing.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"talishar","vendor":"talishar"}],"cvss":{"score":2.6,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Talishar is a fan-made Flesh and Blood project. Prior to commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48, the Talishar application lacks Cross-Site Request Forgery (CSRF) protections on critical state-changing endpoints, specifically within `SubmitChat.php` and other game interaction handlers. By failing to require unique, unpredictable session tokens, the application allows third-party malicious websites to forge requests on behalf of authenticated users, leading to unauthorized actions within active game sessions. The attacker would need to know both the proper gameName and playerID for the player. The player would also need to be browsing and interact with the infected website while playing a game. The vulnerability is fixed in commit 6be3871a14c192d1fb8146cdbc76f29f27c1cf48.","ecosystems":[],"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":"Talishar Vulnerable to Cross-Site Request Forgery (CSRF)","id":"CVE-2026-27632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"TinyWeb has Unbounded Content-Length Memory Exhaustion (DoS)","id":"CVE-2026-27633"},"packages":[],"prev":{"headline":"Exiv2: Uncaught exception - cannot create std::vector larger than max_size()","id":"CVE-2026-27631"},"products":["Talishar"],"published":"2026-02-25","related":[{"cvss_score":7.5,"headline":"Talishar: Critical Path Traversal in gameName Parameter","id":"CVE-2026-28429","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":5.3,"headline":"Talishar: Authentication Bypass via Empty authKey Parameter Allows Unauthenticated Game Actions","id":"CVE-2026-28428","kev_date_added":null,"published":"2026-03-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02-26","vendors":["Talishar"]},"summary":"Attackers can forge requests to perform unauthorized actions in active game sessions if users visit malicious sites while playing.","url":"https://insights.sbomify.com/CVE-2026-27632/"}