tbphp GPT-Load up to 1.4.11 Gin Logger middleware /data/logs/app.log extractAuthKey key missing encryption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.9 | $0-$5k | 0.40+ |
Summary
A vulnerability was found in tbphp GPT-Load up to 1.4.11. It has been classified as problematic. Affected by this issue is the function extractAuthKey of the file /data/logs/app.log of the component Gin Logger middleware. This manipulation of the argument key causes missing encryption.
The identification of this vulnerability is CVE-2026-108754. The attack can only be executed locally. There is no exploit available.
Details
A vulnerability has been found in tbphp GPT-Load up to 1.4.11 and classified as problematic. Affected by this vulnerability is the function extractAuthKey of the file /data/logs/app.log of the component Gin Logger middleware. The manipulation of the argument key with an unknown input leads to a missing encryption vulnerability. The CWE definition for the vulnerability is CWE-311. The product does not encrypt sensitive or critical information before storage or transmission. As an impact it is known to affect confidentiality. The summary by CVE is:
GPT-Load through 1.4.11 contains a cleartext logging vulnerability that exposes client proxy keys because the Gin Logger middleware records the raw query string before extractAuthKey strips the key parameter. Attackers with read access to console logs or ./data/logs/app.log can recover proxy keys from Gemini-style requests and use them against the corresponding group.
It is possible to read the advisory at hackmd.io. This vulnerability is known as CVE-2026-108754 since 10/11/2026. The exploitation appears to be difficult. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK.
By approaching the search of inurl:data/logs/app.log it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.9VulDB Meta Temp Score: 2.9
VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 3.3
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Missing encryptionCWE: CWE-311 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Google Hack: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/11/2026 Advisory disclosed10/11/2026 CVE reserved
10/11/2026 VulDB entry created
10/11/2026 VulDB entry last update
Sources
Advisory: hackmd.ioStatus: Not defined
CVE: CVE-2026-108754 (🔒)
GCVE (CVE): GCVE-0-2026-108754
GCVE (VulDB): GCVE-100-416659
Entry
Created: 10/11/2026 15:21Changes: 10/11/2026 15:21 (77)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.