CVE-2026-62308: Tugtainer: Authenticated SSRF via arbitrary notification URLs in test_notification endpoint
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-04 15:41 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Tugtainer is a self-hosted app for automating updates of Docker containers. Prior to version 1.30.6, Tugtainer allows an authenticated user to make the backend server send outbound HTTP requests to arbitrary user-supplied URLs through the notification test endpoint. The /settings/test_notification endpoint accepts a urls field and passes it directly to Apprise without restricting protocols, hostnames, localhost addresses, private IP ranges, or cloud metadata addresses. This can be abused as an authenticated blind server-side request forgery (SSRF). This issue has been patched in version 1.30.6.
Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-30).
Weakness: CWE-918: Server-Side Request Forgery (SSRF)
How it can be exploited
Exploitable over the network with low attack complexity needing low privileges and no user interaction. Impact: confidentiality high, integrity low, availability low. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:L
CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: no. Technical impact: partial.
Public exploit evidence (Exploit Observer)
Exploit Observer found 4 code repositories naming this CVE.
Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.
See all 6 references on Exploit Observer
Live scores
- EPSS
- 0.003
low predicted chance of attack - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Not listed
- Detection rule
- Suricata
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Quenary tugtainer | version < 1.30.6 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.
How to detect it
Suricata rules (network detection)
1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-62308 Tugtainer - Server-Side Request Forgery via Notification Test. Add them to your Suricata rule set and reload.
Show the rules
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-62308 Tugtainer - Server-Side Request Forgery via Notification Test"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/settings/test_notification"; nocase; fast_pattern; http.request_body; content:"urls"; nocase; pcre:"/\x22?urls\x22?\s*[:=]\s*\x5b?\s*\x22?https?\x3a\/\//i"; classtype:web-application-attack; reference:cve,CVE-2026-62308; reference:url,https://www.exploit.observer/?keyword=CVE-2026-62308&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=tugtainer&match=exact; sid:1096200; rev:1;)
CVE-2026-62308.rules on GitHub
References
Other references
- https://github.com/Quenary/tugtainer/security/advisories/GHSA-c2h5-ppv9-7vrq (x_refsource_CONFIRM)
- https://github.com/Quenary/tugtainer/commit/c0294d0ab64985b135d0c5b566ac30bf8371f9c3 (x_refsource_MISC)
- https://github.com/Quenary/tugtainer/releases/tag/v1.30.6 (x_refsource_MISC)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
