{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-34030 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-34030 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-34030 is a medium-severity path traversal vulnerability in Wertheim SafeController Software for VAULT ROOMS (Safe Deposit Locker System), published on 15 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-34030 and fix it if it is affected.\n\nWhat it is: CVE-2026-34030 is a medium-severity path traversal vulnerability in Wertheim SafeController Software for VAULT ROOMS (Safe Deposit Locker System), published on 15 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-34030 in the wild and no public exploit code.\n\nAffected product: Wertheim SafeController Software for VAULT ROOMS (Safe Deposit Locker System). 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-34030/ (Markdown: https://insights.sbomify.com/CVE-2026-34030/index.md)","id":"CVE-2026-34030","markdown":"https://insights.sbomify.com/CVE-2026-34030/index.md","name":"CVE-2026-34030","record":{"aliases":["GHSA-mvvf-7w7v-ww2x"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Safe deposit locker system","requires_auth":"high_privilege","summary":"An authenticated attacker can manipulate branch codes to store files in unintended filesystem locations via path traversal.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"SEC-VLab","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-73","name":"External Control of File Name or Path"}],"description":"The Wertheim SafeController Software, AssemblyVersion 6.15.8328.28014, does not sufficiently validate the branch code when a new branch is created. The branch code is later used in multiple application functions, including filesystem path generation for uploaded files, profile pictures, and settings. An authenticated attacker with the settings_branches_manage privilege can include path traversal sequences in the branch code and influence the final filesystem location used by affected file operations. This can allow files to be stored in unintended locations, subject to service-account write permissions and branch-code length restrictions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Improper branch-code validation in Wertheim SafeController Software allows file path manipulation","id":"CVE-2026-34030","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Apache Answer: The custom avatar was not properly validated","id":"CVE-2026-34031"},"packages":[],"prev":{"headline":"Hard-coded cryptographic key in Wertheim SafeController Software allows decryption of sensitive configuration data","id":"CVE-2026-34029"},"products":["Wertheim SafeController Software for VAULT ROOMS (Safe Deposit Locker System)"],"published":"2026-06-15","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":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-15","vendors":["Wertheim GmbH"]},"summary":"An authenticated attacker can manipulate branch codes to store files in unintended filesystem locations via path traversal.","url":"https://insights.sbomify.com/CVE-2026-34030/"}