{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54205 exists.","fix":"No fix has been published for CVE-2026-54205 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-54205 is a medium-severity server-side request forgery vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-54205 and fix it if it is affected.\n\nWhat it is: CVE-2026-54205 is a medium-severity server-side request forgery vulnerability in Tobit Laboratories AG TeamDavid, published on 7 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54205 exists.\n\nAffected product: Tobit Laboratories AG TeamDavid. 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-54205/ (Markdown: https://insights.sbomify.com/CVE-2026-54205/index.md)","id":"CVE-2026-54205","markdown":"https://insights.sbomify.com/CVE-2026-54205/index.md","name":"CVE-2026-54205","record":{"aliases":["GHSA-8rw4-wgvv-9v82"],"analysis":{"component_type":"server_software","fix_type":"configuration_change","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"TeamDavid email server","requires_auth":"low_privilege","summary":"Unauthenticated attackers can trigger SSRF via the pathname parameter to steal NTLM hashes or conduct SMB relay attacks.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Tobit Laboratories AG TeamDavid's Webbox 's link storing functionality (//ServerClient_celink.htm)\n accepts a “pathname” parameter, which can be set to network locations \nusing UNC paths (e.g., “\\\\Server\\Share”). The server processes these \npaths without validation, resulting in outbound connection attempts to \nattacker-controlled SMB servers. This enables authenticated attackers to\n trigger the server to authenticate to arbitrary SMB endpoints, \npotentially exposing NTLM authentication information (such as NTLM \nhashes). If outbound connections to port 445 (SMB) are permitted, \nattackers can use this to conduct SMB relay or credential theft attacks.\n Exploitation of the “pathname” parameter is possible without \nauthentication. This issue affects TeamDavid before Rollout 528.\n\nStarting with Rollout 528 (June 30, 2026), the affected functionality is disabled by default and the vulnerabilities are therefore no longer exposed through this functionality.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"TeamDavid: Server-Side Request Forgery (SSRF) via 'pathname' parameter in link storing functionality","id":"CVE-2026-54205","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"TeamDavid: Server-Side Request Forgery (SSRF) via 'pathname' parameter in sending functionality","id":"CVE-2026-54206"},"packages":[],"prev":{"headline":"TeamDavid: Server-Side Request Forgery (SSRF) via 'pathnameroot' parameter in search functionality","id":"CVE-2026-54204"},"products":["TeamDavid"],"published":"2026-08-07","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-09-07","vendors":["Tobit Laboratories AG"]},"summary":"Unauthenticated attackers can trigger SSRF via the pathname parameter to steal NTLM hashes or conduct SMB relay attacks.","url":"https://insights.sbomify.com/CVE-2026-54205/"}