Skip to content
Fencer Intel
high 8.1

CVE-2025-8855 json

2FA Expiry Bypass in Optimus Software's Brokerage Automation

published 11mo ago modified last mo. also EUVD-2025-197605

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits
0
none known

Summary

Authorization Bypass Through User-Controlled Key, Weak Password Recovery Mechanism for Forgotten Password, Authentication Bypass by Assumed-Immutable Data vulnerability in Optimus Software Brokerage Automation allows Exploiting Trust in Client, Authentication Bypass, Manipulate Registry Information.

This issue affects Brokerage Automation: before 1.1.71.

Patch / fix

  • Optimus Software Brokerage Automation 1.1.71

Is CVE-2025-8855 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
11mo ago

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

  • Optimus Software Brokerage Automation

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key
  • CWE-640 Weak Password Recovery Mechanism for Forgotten Password
  • CWE-302 Authentication Bypass by Assumed-Immutable Data

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.