CVE-2026-28428

Talishar: Authentication Bypass via Empty authKey Parameter Allows Unauthenticated Game Actions

Published Mar 6, 2026 CVSS 3.1 · 5.3 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

An authentication bypass flaw in Talishar’s game endpoint validation allows any attacker to carry out actions that normally require authentication, such as sending chat messages or submitting game inputs, simply by providing an empty authKey parameter. The server compares the supplied credential loosely, accepting an empty string as valid while rejecting non‑empty incorrect keys, creating a critical asymmetry in the authentication logic.

Affected Systems

This vulnerability affects the Talishar fan‑made Flesh and Blood project. Any deployment of the game server running a version of the code prior to commit a9c218e is vulnerable; newer versions contain the patch.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity, and the EPSS score of less than 1 % suggests low current exploitation probability. The issue is not listed in the CISA KEV catalog. Because the attack requires only the submission of an empty authKey, it can be executed remotely over the public network without prior knowledge of valid credentials, effectively granting unauthenticated users privileged actions within the game.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Apply the patch that replaces the loose comparison with a strict equality check, addressing the authentication bypass (CWE‑287).
  • Restart the Talishar server to load the corrected authentication logic.
  • If patching is not immediately possible, temporarily configure the server to reject any game requests that lack a valid, non‑empty authKey or that provide an empty authKey, mitigating the authentication bypass.

Generated by OpenCVE AI on April 17, 2026 at 12:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
CPEs cpe:2.3:a:talishar:talishar:*:*:*:*:*:*:*:*
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Talishar
Talishar talishar
Vendors & Products Talishar
Talishar talishar
Type Values Removed Values Added
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.
Title Talishar: Authentication Bypass via Empty authKey Parameter Allows Unauthenticated Game Actions
Weaknesses CWE-287
References
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 9, 2026, 7:54 PM
Reserved
Feb 27, 2026, 3:54 PM
Status
Analyzed
Published
Mar 6, 2026, 5:16 AM
Modified
Jun 17, 2026, 10:28 AM