Quenary tugtainer up to 1.16.0 get request method with sensitive query strings
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Quenary tugtainer up to 1.16.0. The affected element is an unknown function. This manipulation causes use of get request method with sensitive query strings. This vulnerability is registered as CVE-2026-23846. Remote exploitation of the attack is possible. No exploit is available. You should upgrade the affected component.
Details
A vulnerability classified as critical was found in Quenary tugtainer up to 1.16.0. Affected by this vulnerability is some unknown functionality. The manipulation with an unknown input leads to a use of get request method with sensitive query strings vulnerability. The CWE definition for the vulnerability is CWE-598. The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Tugtainer is a self-hosted app for automating updates of Docker containers. In versions prior to 1.16.1, the password authentication mechanism transmits passwords via URL query parameters instead of the HTTP request body. This causes passwords to be logged in server access logs and potentially exposed through browser history, Referer headers, and proxy logs. Version 1.16.1 patches the issue.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-23846 since 01/16/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.16.1 eliminates this vulnerability. Applying the patch 9d23bf40ac1d39005582abfcf0a84753a4e29d52 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-3294). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔒
CNA Base Score: 8.1
CNA Vector (GitHub_M): 🔒
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: Use of get request method with sensitive query stringsCWE: CWE-598
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: tugtainer 1.16.1
Patch: 9d23bf40ac1d39005582abfcf0a84753a4e29d52
Timeline
01/16/2026 CVE reserved01/19/2026 VulDB entry created
01/20/2026 Advisory disclosed
02/05/2026 VulDB entry last update
Sources
Product: github.comAdvisory: GHSA-f2qf-f544-xm4p
Status: Confirmed
CVE: CVE-2026-23846 (🔒)
GCVE (CVE): GCVE-0-2026-23846
GCVE (VulDB): GCVE-100-341875
EUVD: 🔒
Entry
Created: 01/20/2026 00:11Updated: 02/05/2026 21:09
Changes: 01/20/2026 00:11 (65), 01/20/2026 03:34 (1), 02/05/2026 21:09 (11)
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.