Answer in brief
CVE-2026-89309 records a Critical severity (CVSS 10.0) vulnerability in Missing Authentication Vulnerability in JTL-WMS. The current sources do not mark it as known exploited. The current feed maps JTL SW GmbH/JTL-WMS (generic), tbc/tbc (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 10.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps JTL SW GmbH/JTL-WMS (generic), tbc/tbc (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| JTL SW GmbH/JTL-WMSgeneric | >=0 <2.0.7 || >=0 <2.1.2 || >=0 <2.2.1 || 1.7.* 1.8.* 1.9.* 1.10.* 1.11.* | 2.0.7, 2.1.2, 2.2.1 |
| tbc/tbcgeneric | >=0 <1 | 1 |
Published upstream
Oct 13, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 13, 2026
The authorization middleware of the WMS MobileServer fails to require authentication in two distinct cases. First, it only requires an Authorization header for GET and HEAD requests; requests using any other HTTP method are processed without an authentication check. Second, for any HTTP method including GET and HEAD, a request carrying a malformed or non-bearer Authorization header is passed through without a valid token being required. The middleware does validate a token whenever a well-formed one is present, but in these two cases it does not require one. A remote attacker with network access to the service can therefore invoke API functionality without valid credentials.
Quoted source text, attributed separately from HOL analysis.