Skip to main content
VulnerabilityPublished

CVE-2025-12508: Bizerba BRAIN2 · Cleartext Transmission

Affects Bizerba BRAIN2Source CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Bizerba BRAIN2Affected
  • =0.0
Fixed in–

AI-suggested

To mitigate CVE-2025-12508, European organizations should immediately assess their use of Bizerba BRAIN2 with domain user integration. Until a patch is released, disable the use of domain users as BRAIN2 users or isolate BRAIN2 communication with Active Directory to secure, segmented network zones. Implement network-level encryption such as VPNs or IPsec tunnels to protect authentication traffic. Monitor network traffic for unencrypted LDAP or similar protocols and deploy intrusion detection systems to identify suspicious activities. Enforce strict access controls and limit the number of users with high privileges to reduce exploitation risk. Conduct regular audits of authentication logs to detect anomalies. Engage with Bizerba for timely updates and patches, and plan for prompt deployment once available. Additionally, educate users about the risks of interacting with suspicious prompts or workflows that could facilitate exploitation. Consider deploying multi-factor authentication (MFA) to add an extra layer of security for domain user accounts involved in BRAIN2 operations.

Description

When using domain users as BRAIN2 users, communication with Active Directory services is unencrypted. This can lead to the interception of authentication data and compromise confidentiality.

References

Community reviews

Loading reviews…