{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28428 exists.","fix":"No fix has been published for CVE-2026-28428 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-28428 is a medium-severity authentication bypass vulnerability in Talishar, published on 6 Mar 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-28428 and fix it if it is affected.\n\nWhat it is: CVE-2026-28428 is a medium-severity authentication bypass vulnerability in Talishar, published on 6 Mar 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-28428 exists.\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-28428/ (Markdown: https://insights.sbomify.com/CVE-2026-28428/index.md)","id":"CVE-2026-28428","markdown":"https://insights.sbomify.com/CVE-2026-28428/index.md","name":"CVE-2026-28428","record":{"aliases":["GHSA-2659-p579-wv83"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Fan-made game project","requires_auth":"none","summary":"Unauthenticated attackers can bypass authentication and perform game actions by supplying an empty authKey parameter due to loose comparison logic.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"talishar","vendor":"talishar"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Talishar is a fan-made Flesh and Blood project. Prior to commit a9c218e, an authentication bypass vulnerability in Talishar's game endpoint validation logic allows any unauthenticated attacker to perform authenticated game actions — including sending chat messages and submitting game inputs — by supplying an empty authKey parameter (authKey=). The server-side validation uses a loose comparison that accepts an empty string as a valid credential, while correctly rejecting non-empty but incorrect keys. This asymmetry means the authentication mechanism can be completely bypassed without knowing any valid token. This issue has been patched in commit a9c218e.","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":"Talishar: Authentication Bypass via Empty authKey Parameter Allows Unauthenticated Game Actions","id":"CVE-2026-28428","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Talishar: Critical Path Traversal in gameName Parameter","id":"CVE-2026-28429"},"packages":[],"prev":{"headline":"OpenDeck affected by path traversal allows arbitrary file read","id":"CVE-2026-28427"},"products":["Talishar"],"published":"2026-03-06","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":2.6,"headline":"Talishar Vulnerable to Cross-Site Request Forgery (CSRF)","id":"CVE-2026-27632","kev_date_added":null,"published":"2026-02-25"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-09","vendors":["Talishar"]},"summary":"Unauthenticated attackers can bypass authentication and perform game actions by supplying an empty authKey parameter due to loose comparison logic.","url":"https://insights.sbomify.com/CVE-2026-28428/"}