User impersonation via unsigned embedded JWTs
Published Mar 3, 2026 · Updated Mar 3, 2026
Authentication bypass in DataEase SQLBot 1.5.0 through 1.5.1 allows remote attackers to impersonate users with forged embedded JWTs. validateEmbedded in backend/apps/system/middleware/auth.py decodes the token with signature and expiration checks disabled, then trusts its account claim for user lookup. An attacker needs a valid embedded assistant ID, but no account credentials or signing key, and gains the selected user's protected access.
Summary
What happened
Authentication bypass in DataEase SQLBot 1.5.0 through 1.5.1 allows remote attackers to impersonate users with forged embedded JWTs. validateEmbedded in backend/apps/system/middleware/auth.py decodes the token with signature and expiration checks disabled, then trusts its account claim for user lookup. An attacker needs a valid embedded assistant ID, but no account credentials or signing key, and gains the selected user's protected access.
The record
- CVE
- CVE-2025-15598
- Published
- Mar 3, 2026
- Updated
- Mar 3, 2026
- Vendor
- KubeOperator
- Product
- SQLBot
- Classifications
- CWE-345, CWE-347, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 3, 2026CVE publishedPublication date reported by the CVE source.
- Mar 3, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.5.0
- Affected versionversion=1.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- JWT Signature Verification Bypass in Embedded Authenticationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo