# CVE-2026-33591: Authentication bypass on WaptServer

> Remote unauthenticated attackers can bypass security restrictions to retrieve valid session tokens, leading to account takeover in WAPT Server.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-jj6f-hxj9-r997

## What is CVE-2026-33591?

CVE-2026-33591 is a critical authentication bypass vulnerability in Tranquil IT Systems WAPT Server, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in Wapt Server before version 2.6.1.17813 allows a  remote unauthenticated attacker to bypass
security restriction using a specially crafted packet and retrieve a valid
session token for the targeted account.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2026-33591?


## How do I fix CVE-2026-33591?

No fix has been published for CVE-2026-33591 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-33591 being exploited?

There is no known exploitation of CVE-2026-33591 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33591 and fix it if it is affected.

What it is: CVE-2026-33591 is a critical authentication bypass vulnerability in Tranquil IT Systems WAPT Server, published on 3 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33591 in the wild and no public exploit code.

Affected product: Tranquil IT Systems WAPT Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33591/ (Markdown: https://insights.sbomify.com/CVE-2026-33591/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33591
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33591
- OSV: https://osv.dev/vulnerability/CVE-2026-33591

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33591/
Summaries are generated and may contain mistakes; the official description above is the record.