CVE-2026-23846
Quenary Tugtainer ≤ 1.16.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:NSummary
CVE-2026-23846 is a high-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability in Quenary Tugtainer. Its CVSS base score is 8.1 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 33th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-23846 affects Tugtainer, a self-hosted application for automating updates of Docker containers, in versions prior to 1.16.1. The vulnerability stems from the password authentication mechanism transmitting credentials via URL query parameters rather than in the HTTP request body. This design flaw results in passwords being logged in server access logs and potentially exposed through browser history, Referer headers, and proxy logs, corresponding to CWE-598 (Information Exposure Through Query Parameters in GET Request). The issue carries a CVSS v3.1 base score of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N).
Attackers can exploit this vulnerability over the network with low complexity and no required privileges, though it necessitates user interaction, such as a legitimate user authenticating via the affected interface. Exploitation enables observation or access to logs, browser data, or network traffic where the password is inadvertently stored or transmitted. Successful compromise yields high confidentiality and integrity impacts, allowing attackers to capture valid credentials for unauthorized access to Tugtainer instances.
The GitHub security advisory (GHSA-f2qf-f544-xm4p) and patching commit (9d23bf40ac1d39005582abfcf0a84753a4e29d52) confirm that upgrading to version 1.16.1 resolves the issue by modifying the authentication to avoid query parameter usage. Security practitioners should prioritize updating affected Tugtainer deployments and review existing logs for exposed credentials.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3294
Vulnerability Data
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…
more
access logs and potentially exposed through browser history, Referer headers, and proxy logs. Version 1.16.1 patches the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V3.4.5V14.2.1
Mitigating Controls (NIST 800-53 r5) AI
Requiring confidentiality and integrity protection for transmitted data reduces exposure of sensitive query parameters even though the control does not forbid placing secrets in URLs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.
HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect sensitive data leakage via query strings.
DLP solutions can detect and block sensitive data in URLs.
Network security controls can enforce HTTPS and block sensitive data in URLs.
Application security requirements should mandate avoiding sensitive data in query strings.
Secure architecture principles discourage exposing sensitive data in URLs.
Secure coding standards directly prohibit placing secrets in query parameters.