Skip to content
Applications

CVE-2025-14510

9.2
Critical
EPSS 0.44%Patch availableJan 16, 2026

Authentication bypass in ABB Ability OPTIMAX

common questions

Is CVE-2025-14510 being exploited?

Not confirmed. CVE-2025-14510 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.44% probability of exploitation in the next 30 days.

How severe is CVE-2025-14510?

CVE-2025-14510 is rated Critical with a CVSS score of 9.2. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2025-14510?

Yes. A fix has been recorded for CVE-2025-14510. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2025-14510 affect?

CVE-2025-14510 affects ABB Ability OPTIMAX 6.1, ABB Ability OPTIMAX 6.2, ABB Ability OPTIMAX 6.3.0 before 6.3.1-251120, ABB Ability OPTIMAX 6.4.0 before 6.4.1-251120. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-14510?

Upgrade to 6.3.1-251120 or 6.4.1-251120

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
ABB Ability OPTIMAX 6.1ABB Ability OPTIMAX 6.2ABB Ability OPTIMAX 6.3.0 before 6.3.1-251120ABB Ability OPTIMAX 6.4.0 before 6.4.1-251120
impact

Authentication bypass enables unauthorized access to OPTIMAX features and settings.

action required

Immediate action required

affected versions
ABB ABB Ability OPTIMAX
  • affected6.1
  • affected6.2
  • affected>= 6.3.0 and < 6.3.1-251120
  • affected>= 6.4.0 and < 6.4.1-251120

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free