How to Fix CVE-2026-27632: Csrf in Talishar

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-27632 is a CSRF in Talishar Talishar. The fix is to apply the vendor patch noted below.

What is CVE-2026-27632?

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. The CVSS base score is 2.6 (Low). The official advisory is at https://github.com/Talishar/Talishar/security/advisories/GHSA-73mm-323r-cm3g.

Am I affected?

Check the version of Talishar you are running and compare it against the Affected row above (Talishar < 6be3871a14c192d1fb8146cdbc76f29f27c1cf48). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:

# Linux package check
dpkg -s talishar 2>/dev/null | grep -i ^Version
rpm -q talishar 2>/dev/null
command -v talishar >/dev/null && talishar --version 2>/dev/null

# Windows (PowerShell)
Get-Package -Name "*Talishar*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "Talishar" 2>$null

How to fix CVE-2026-27632

Upgrade Talishar to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian

sudo apt-get update
sudo apt-get install --only-upgrade talishar
dpkg -s talishar | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux

sudo dnf upgrade --refresh talishar -y
# or for older releases:
sudo yum update talishar -y
rpm -q talishar

SUSE / openSUSE

sudo zypper refresh
sudo zypper update talishar
rpm -q talishar

PHP / Composer

composer update talishar/talishar 2>/dev/null || composer update
composer show | head -20

Complete PowerShell remediation script (Windows)

# Fix script for CVE-2026-27632 affecting Talishar
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-27632-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*Talishar*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\talishar-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\Talishar" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "Talishar" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "Talishar"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)

#!/usr/bin/env bash
# Fix script for CVE-2026-27632 affecting Talishar
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-27632-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s talishar 2>/dev/null | grep -i ^Version || echo "talishar not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q talishar || echo "talishar not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-27632-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/talishar /etc/talishar.d /etc/talishar.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y talishar
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y talishar
elif command -v yum >/dev/null; then
    yum update -y talishar
elif command -v zypper >/dev/null; then
    zypper --non-interactive update talishar
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s talishar 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q talishar
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)

# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)

New-NetFirewallRule -DisplayName "Block-CVE-2026-27632" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-27632"

Disable the affected service (Linux)

sudo systemctl stop talishar 2>/dev/null || true
sudo systemctl disable talishar 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.

# Linux
dpkg -s talishar 2>/dev/null | grep -i ^Version
rpm -q talishar 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true

# Windows
Get-Package -Name "*Talishar*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Related fixes

Other vulnerabilities in the same area that are worth patching alongside this one:

• How to Fix CVE-2026-40885: Information disclosure in goshs — Information disclosure in goshs
• How to Fix CVE-2026-22514: Critical Vulnerability in Unica — Critical Vulnerability in Unica
• How to Fix CVE-2026-1320: Critical Vulnerability in Secure Copy Content Protection and Content Locking , Critical Vulnerability in Secure Copy Content Protection and Content Locking
• How to Fix CVE-2026-42307: Improper Neutralization of Special Elements used in an OS Command ('OS Command I , Improper Neutralization of Special Elements used in an OS Command ('OS Command I
• How to Fix CVE-2026-39339: CRM (Bundle Sibling) , CRM (Bundle Sibling)

Is CVE-2026-27632 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-27632?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-27632?

2.6 (Low). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N.

Where is the official advisory for CVE-2026-27632?

The vendor advisory is at https://github.com/Talishar/Talishar/security/advisories/GHSA-73mm-323r-cm3g. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-27632.

References

• Official vendor advisory: https://github.com/Talishar/Talishar/security/advisories/GHSA-73mm-323r-cm3g
• NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27632
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*