{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23846 exists.","fix":"No fix has been published for CVE-2026-23846 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-23846 is a high-severity vulnerability in Quenary tugtainer, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-23846 and fix it if it is affected.\n\nWhat it is: CVE-2026-23846 is a high-severity vulnerability in Quenary tugtainer, published on 19 Jan 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-23846 exists.\n\nAffected product: Quenary tugtainer. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-23846/ (Markdown: https://insights.sbomify.com/CVE-2026-23846/index.md)","id":"CVE-2026-23846","markdown":"https://insights.sbomify.com/CVE-2026-23846/index.md","name":"CVE-2026-23846","record":{"aliases":["GHSA-f2qf-f544-xm4p"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Docker container updater","requires_auth":"none","summary":"Attackers can recover passwords from logs or browser history because Tugtainer sends credentials in URL query parameters.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"tugtainer","vendor":"quenary"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-598","name":"Use of HTTP Request With Sensitive Query String"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Tugtainer vulnerable to Password Exposure via URL Query Parameter","id":"CVE-2026-23846","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"SiYuan Vulnerable to Reflected Cross-Site Scripting (XSS) via /api/icon/getDynamicIcon","id":"CVE-2026-23847"},"packages":[],"prev":{"headline":"Mailpit Vulnerable to Server-Side Request Forgery (SSRF) via HTML Check API","id":"CVE-2026-23845"},"products":["tugtainer"],"published":"2026-01-19","related":[{"cvss_score":8.1,"headline":"Tugtainer has RCE in Agent Command Execution Api","id":"CVE-2025-69201","kev_date_added":null,"published":"2025-12-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-20","vendors":["Quenary"]},"summary":"Attackers can recover passwords from logs or browser history because Tugtainer sends credentials in URL query parameters.","url":"https://insights.sbomify.com/CVE-2026-23846/"}