Skip to main content

_connect.BRAIN EUVDEUVD-2026-45903

| CVE-2026-16247 HIGH
Incorrect Default Permissions (CWE-276)
2026-07-20 0beee27a-7d8c-424f-8e46-ac453fa147e6 GHSA-gxr5-ww5q-wmqx
7.3
CVSS 3.1 · Vendor: 0beee27a-7d8c-424f-8e46-ac453fa147e6
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Gain local access as low-privileged user
  2. Delivery
    Enumerate world-writable %ProgramData% files
  3. Exploit
    Plant or overwrite binary/DLL/config
  4. Execution
    Await execution by SYSTEM process
  5. Persist
    Execute code as SYSTEM
  6. Impact
    Escalate to full host control

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V13 - Configuration Default permission hardening
MITRE ATT&CK

1 technique across 1 tactic: Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a vulnerable install of Bizerba _connect.BRAIN prior to 5.06 where the setup executed LogPathConfig.exe, leaving %ProgramData% with an ACL granting the built-in Everyone group Full Control. The attacker must already have local interactive or authenticated access to the host as any low-privileged user (matching CVSS PR:L, AV:L). Actual escalation additionally depends on the presence of a higher-privileged process (service, scheduled task, or installer running as SYSTEM/admin) that reads or executes a file located under the world-writable %ProgramData% path - this is the concrete condition that turns the weak ACL into code execution. Limiting factors: exploitation is local-only (not remotely reachable), is neutralized on systems patched to 5.06, and requires that the flawed installer actually ran on the host; hosts where the ACL has since been reset are not exploitable.

Impact

The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L, base 7.3) describes a locally-exploitable, low-complexity flaw requiring an existing low-privileged foothold, with high confidentiality/integrity impact and low availability impact - consistent with a privilege-escalation primitive rather than remote compromise. No EPSS score, KEV entry, POC, or SSVC decision data was supplied, so exploitation-probability and automatability signals are effectively unknown; absence of these is not evidence of low risk, but also nothing here indicates active or widespread exploitation. Because the flaw grants Everyone full control over the shared %ProgramData% root, the practical blast radius is broader than the single product: it lowers the bar for local escalation on any host where the vulnerable installer ran. Realistic priority is moderate - genuinely dangerous where the software is deployed and untrusted local users exist, but gated behind requiring local access, so it is not an internet-facing emergency.

Exploit ScenarioDerived

A standard (non-administrative) user logged into a system running _connect.BRAIN below 5.06 discovers that Everyone has full control over %ProgramData%, then plants or overwrites a DLL, executable, or configuration file that a service or scheduled task running as SYSTEM later loads. When the privileged process executes the attacker-controlled file, the attacker gains SYSTEM-level code execution. No public exploit code is identified, but the technique is a well-understood local privilege-escalation pattern requiring only local access.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 20, 2026

Local privilege escalation in Bizerba _connect.BRAIN before version 5.06 stems from its setup routine invoking LogPathConfig.exe, which strips the existing ACL on %ProgramData% and grants the built-in Everyone group full control instead of scoping permissions to the Bizerba subfolders. Any local low-privileged user can then modify files under %ProgramData% that privileged components read or execute, enabling escalation to higher privileges. There is no public exploit identified at time of analysis and it is not listed in CISA KEV; the issue is resolved in 5.06, which no longer runs the tool.

RemediationAI

Vendor-released patch: 5.06 - upgrade Bizerba _connect.BRAIN to 5.06 or later, which no longer runs LogPathConfig.exe and therefore does not weaken %ProgramData% permissions. Critically, upgrading alone may not repair an already-corrupted ACL on hosts where the vulnerable installer previously ran, so on those systems administrators should manually reset permissions on %ProgramData% to the Windows default (remove the Everyone Full Control grant and restore inherited administrator/SYSTEM-only write access, scoping any needed application write access to %ProgramData%\Bizerba\_connect.BRAIN and %ProgramData%\Bizerba\BCT only) - for example via icacls to reset inheritance and re-apply the standard ProgramData ACL. The trade-off is that overly aggressive tightening could break the application's ability to write logs, so validate that the two Bizerba subfolders retain the required write access after remediation. Consult the vendor advisory for authoritative guidance: https://www.bizerba.com/downloads/global/information-security/2026/bizerba-sa-2026-0003.pdf.

Affected VersionsENISA

_connect.BRAIN >5.06

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-276 (Incorrect Default Permissions). On Windows, %ProgramData% (typically C:\ProgramData) is a shared machine-wide location that should be writable only by administrators/SYSTEM while allowing standard users read/execute. The affected product ships a helper, LogPathConfig.exe, run during installation to configure log paths; instead of tightening ACLs to %ProgramData%\Bizerba\_connect.BRAIN and %ProgramData%\Bizerba\BCT, it replaces the inherited ACL on the whole %ProgramData% root with a Full Control grant to Everyone. This weakens the security boundary for every application storing data there, not just Bizerba's, because any local principal can create, overwrite, or delete files - the classic pre-condition for DLL/binary planting or config tampering against services running as SYSTEM. The affected product is Bizerba _connect.BRAIN, a component in Bizerba's retail/industrial weighing and labeling ecosystem (BCT); no CPE strings were provided in the input.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (0beee27a-7d8c-424f-8e46-ac453fa147e6) PRIMARY 7.3 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
vuln.today AI 7.3 HIGH

Local low-privileged user (AV:L, PR:L) exploits a trivially discoverable world-writable ACL (AC:L) to tamper with privileged files, yielding high confidentiality/integrity and limited availability impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
4.0 AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (0beee27a-7d8c-424f-8e46-ac453fa147e6).

CVSS VectorVendor: 0beee27a-7d8c-424f-8e46-ac453fa147e6

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

DescriptionCVE.org

In _connect.BRAIN versions prior to 5.06, the application LogPathConfig.exe is executed during setup. During this process, existing permissions on %ProgramData% are deleted and replaced, granting the Windows group Everyone full control instead of restricting access to %ProgramData%\Bizerba\_connect.BRAIN or %ProgramData%\Bizerba\BCT.

Starting with _connect.BRAIN 5.06, the setup no longer executes this tool.

Executive ViewAI

Why It Matters

Bizerba _connect.BRAIN versions prior to 5.06 contain a local privilege escalation flaw that allows any low-privileged user on an affected system to gain administrative control by modifying files in the %ProgramData% directory. Organizations running vulnerable versions face risk of internal privilege escalation attacks and compromise of systems relying on this software for operations.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.1%
Top 99% exploitable
Prevalence
Low
niche industrial/retail weighing and labeling software, limited enterprise IT footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy