● Medium · CVSS 6.5

How to Fix CVE-2026-28444: Insecure Direct Object Reference in typebot.io

Q: Is CVE-2026-28444 being exploited in the wild?

Public exploitation has not been confirmed by CISA at the time of writing. Treat the patch as time-sensitive anyway; reports often lag actual abuse.

Q: Will a WAF or IDS rule fully mitigate CVE-2026-28444?

No. Network-layer filters can reduce noise and slow opportunistic scanners, but they will not stop a determined attacker. The vendor patch is the only durable fix.

Q: How long should I plan for the upgrade?

Typical vendor-documented upgrade windows for typebot.io run from a few minutes to under an hour depending on cluster size. Test in a staging environment first and follow the vendor's documented HA upgrade order.

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

How to Fix CVE-2026-28099: Cross-site scripting in UberSlider Ultra — Cross-site scripting in UberSlider Ultra
How to Fix CVE-2026-44647: Path Traversal in onedev — Path Traversal in onedev
How to Fix CVE-2026-27370: Insertion of sensitive information into sent data in Chaty , Insertion of sensitive information into sent data in Chaty
How to Fix CVE-2026-6442: Validation of syntactic correctness of input in Cortex Code CLI , Validation of syntactic correctness of input in Cortex Code CLI
How to Fix CVE-2026-4344: Cross-site scripting in Fusion , Cross-site scripting in Fusion

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 6.5 - Medium
Actively exploited?	Not currently listed in CISA KEV
Affected	< 3.16.0
Fixed in	version
Type (CWE)	CWE-639: Authorization Bypass Through User-Controlled Key

What is CVE-2026-28444?

CVE-2026-28444 is an insecure direct object reference (IDOR) in typebot.io. The product uses a user-supplied identifier to fetch or modify a record without checking that the caller is allowed to touch that specific object, exposing or altering other users' data. Vendor description: Typebot is a chatbot builder tool. In versions 3.15.2 and prior, the getResultLogs API endpoint authorizes the caller against the provided typebotId but fetches logs solely by resultId without verifying that the result belongs to the authorized typebot, leading to IDOR.

Why this CVE matters

IDOR flaws bypass the application's intended tenant isolation. In multi-user products this typically means one customer can read or modify another customer's data with nothing more than a sequential identifier.

For deployments of typebot.io that have been exposed to the public internet during the disclosure window, the operating assumption should be that scanning has already happened. Even where exploitation has not been publicly observed, scanning for the vulnerable fingerprint is cheap and routine. Patching closes the door; log review and credential rotation close out the rest of the response.

Am I affected?

You are affected if your installation matches any of these version ranges:

typebot.io: < 3.16.0

Check your installed version against the list above. If you cannot determine the version, treat the system as affected and follow the upgrade path below.

Open typebot.io's About dialog or run the vendor-documented version-check command. Compare the result against the affected ranges in the advisory.

How to fix CVE-2026-28444

Read the vendor advisory in full: https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-c63p-mqx5-75r7
Upgrade typebot.io to the patched build listed in the vendor advisory.
Back up the configuration (and database, where applicable) before upgrading.
Apply the patch in a maintenance window. For HA pairs, upgrade the standby node first, fail over, then upgrade the former primary.
Restart the affected service so the patched binary loads, then verify the new version (see verification section).

The commands below are runnable starting points. Adapt the package name, target version, and host paths to your environment using the vendor advisory linked under References.

npm / Yarn / pnpm


# Vendor advisory: https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-c63p-mqx5-75r7
# Update to the patched release named in the advisory
npm install typebot-io@latest
# or pin to the exact fixed version from the vendor advisory
npm install typebot-io@<patched-version>
npm ls typebot-io

PyPI (pip / Poetry)


# Vendor advisory: https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-c63p-mqx5-75r7
pip install --upgrade typebot-io
pip show typebot-io | grep -i version
# Poetry:
poetry add typebot-io@^<patched-version>

Docker / container


# Vendor advisory: https://github.com/baptisteArno/typebot.io/security/advisories/GHSA-c63p-mqx5-75r7
docker pull <your-registry>/typebot-io:<patched-tag>
docker stop <app> && docker rm <app>
docker run -d --name <app> <your-registry>/typebot-io:<patched-tag>

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2026-28444 remediation runner. Adapt version checks to your environment.
$log = "C:\Logs\CVE-2026-28444-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'typebot.io' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2026-28444-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'typebot.io' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged; check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

Bash detect/upgrade/verify/log (Linux)


#!/usr/bin/env bash
# CVE-2026-28444 remediation runner. Re-runnable, exits non-zero on failure.
set -euo pipefail
log() { printf '%s %s\n' "$(date -Is)" "$*" | tee -a /var/log/cve-2026-28444-fix.log; }

log "Detect: current typebotio version"
if command -v dpkg >/dev/null 2>&1; then
    current=$(dpkg-query -W -f='${Version}' typebotio 2>/dev/null || echo "not-installed")
elif command -v rpm >/dev/null 2>&1; then
    current=$(rpm -q --qf '%{VERSION}-%{RELEASE}' typebotio 2>/dev/null || echo "not-installed")
else
    current="unknown"
fi
log "Current: $current"

log "Backup: snapshotting config"
backup="/var/backups/cve-2026-28444-$(date +%Y%m%d-%H%M)"
mkdir -p "$backup"
[ -d /etc/typebotio ] && cp -a /etc/typebotio "$backup/" || true

log "Upgrade: applying vendor patch"
if command -v apt-get >/dev/null 2>&1; then
    sudo apt-get update -qq
    sudo apt-get install -y --only-upgrade typebotio
elif command -v dnf >/dev/null 2>&1; then
    sudo dnf upgrade -y typebotio
elif command -v yum >/dev/null 2>&1; then
    sudo yum update -y typebotio
fi

log "Verify: re-reading typebotio version"
if command -v dpkg >/dev/null 2>&1; then
    after=$(dpkg-query -W -f='${Version}' typebotio)
else
    after=$(rpm -q --qf '%{VERSION}-%{RELEASE}' typebotio)
fi
log "After: $after"

if [ "$after" != "$current" ]; then
    log "SUCCESS: typebotio upgraded"
else
    log "WARN: version unchanged. Confirm the patched build is in your repository."
    exit 1
fi

If you cannot patch immediately

Front the vulnerable endpoint with an authorization rule at a reverse proxy or API gateway that validates the caller's right to access the requested object. The patch is the only complete fix.

How to verify the fix worked

After applying the patch, verify the running version in the product's admin UI or via the vendor-documented CLI command.
Confirm the patched build matches the version listed in the vendor advisory.
Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2026-28444.
Review logs for the entire pre-patch window for indicators of compromise listed in the vendor or CISA advisory.
Confirm any network-layer mitigations that were applied as a stopgap have been reverted (or left in place intentionally) once the patch is verified.

If your installation was internet-reachable during the disclosure window, treat log review as part of the remediation rather than an optional follow-up. Look for log entries that do not match your normal request patterns, especially repeated requests to the same uncommon endpoint, and any administrative changes you cannot tie back to a known operator.

Frequently asked questions

Is CVE-2026-28444 being exploited in the wild?