CVE-2026-34030

MEDIUMPre-NVD 6.96.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 75% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
6.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.9
EG Score
6.9(medium)
EPSS
24.6%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 15, 2026

Advisory Details (2)

Auto-updated Jun 15, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic

Safe Deposit Software: Role-Based Control System

https://wertheim-safes.com/safe-deposit-box-management/
generic🟡 PoC Available

Multiple Critical Vulnerabilities in Wertheim SafeController Software for VAULT ROOMS (Safe Deposit Locker System) - SEC Consult

https://r.sec-consult.com/wertheim

Vendor Advisories for CVE-2026-34030(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 75× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 00:28 UTCEG score recompute
  2. 2026-07-07 00:28 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 19:11 UTCEG score recompute
  8. 2026-07-05 19:11 UTCGHSA enrichment
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 18:59 UTCEG score recompute
  11. 2026-07-04 18:59 UTCGHSA enrichment
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-03 16:51 UTCEG score recompute
  14. 2026-07-03 16:51 UTCGHSA enrichment
  15. 2026-07-02 16:37 UTCEG score recompute
  16. 2026-07-02 16:37 UTCGHSA enrichment
  17. 2026-07-01 16:27 UTCEG score recompute
  18. 2026-07-01 16:27 UTCGHSA enrichment
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-30 16:16 UTCEG score recompute
  22. 2026-06-30 16:16 UTCGHSA enrichment
  23. 2026-06-29 15:56 UTCEG score recompute
  24. 2026-06-29 15:56 UTCGHSA enrichment
  25. 2026-06-29 14:06 UTCEPSS rescore
Show 50 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-28 15:46 UTCEG score recompute
  3. 2026-06-28 15:46 UTCGHSA enrichment
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-27 15:32 UTCEG score recompute
  9. 2026-06-27 15:32 UTCGHSA enrichment
  10. 2026-06-27 03:08 UTCEPSS rescore
  11. 2026-06-26 15:21 UTCEG score recompute
  12. 2026-06-26 15:21 UTCGHSA enrichment
  13. 2026-06-25 15:11 UTCEG score recompute
  14. 2026-06-25 15:11 UTCGHSA enrichment
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-24 15:01 UTCEG score recompute
  18. 2026-06-24 15:01 UTCGHSA enrichment
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-23 21:33 UTCEPSS rescore
  21. 2026-06-23 21:33 UTCEPSS rescore
  22. 2026-06-23 14:49 UTCEG score recompute
  23. 2026-06-23 14:49 UTCGHSA enrichment
  24. 2026-06-22 14:25 UTCEPSS rescore
  25. 2026-06-22 14:25 UTCEPSS rescore
  26. 2026-06-22 14:18 UTCEG score recompute
  27. 2026-06-22 14:18 UTCGHSA enrichment
  28. 2026-06-21 14:56 UTCEPSS rescore
  29. 2026-06-21 14:56 UTCEPSS rescore
  30. 2026-06-21 14:06 UTCEG score recompute
  31. 2026-06-21 14:06 UTCGHSA enrichment
  32. 2026-06-21 01:59 UTCEPSS rescore
  33. 2026-06-20 13:01 UTCEG score recompute
  34. 2026-06-20 13:01 UTCGHSA enrichment
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-19 19:25 UTCEPSS rescore
  37. 2026-06-19 12:51 UTCEG score recompute
  38. 2026-06-19 12:51 UTCGHSA enrichment
  39. 2026-06-18 17:52 UTCEPSS rescore
  40. 2026-06-18 17:52 UTCEPSS rescore
  41. 2026-06-18 12:38 UTCEG score recompute
  42. 2026-06-18 12:37 UTCGHSA enrichment
  43. 2026-06-17 17:53 UTCEPSS rescore
  44. 2026-06-17 12:26 UTCEG score recompute
  45. 2026-06-17 12:25 UTCGHSA enrichment
  46. 2026-06-16 17:52 UTCEPSS rescore
  47. 2026-06-16 12:14 UTCEG score recompute
  48. 2026-06-16 12:14 UTCGHSA enrichment
  49. 2026-06-15 12:03 UTCEG score recompute
  50. 2026-06-15 12:03 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-34030?
CVE-2026-34030 is a medium vulnerability published on June 15, 2026. 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…
When was CVE-2026-34030 disclosed?
CVE-2026-34030 was first published in the National Vulnerability Database on June 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-34030 actively exploited?
CVE-2026-34030 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 24.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-34030?
CVE-2026-34030 has a CVSS v3 base score of 6.9 (NVD).
How do I remediate CVE-2026-34030?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-34030, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-34030

Explore →

Is Your Infrastructure Affected by CVE-2026-34030?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs