Skip to content
Infrastructure

CVE-2026-5065

8.8
High
EPSS 0.19%Patch availableMay 27, 2026

Hard-coded credentials in IBM Controller allow auth bypass

common questions

Is CVE-2026-5065 being exploited?

Not confirmed. CVE-2026-5065 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.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-5065?

CVE-2026-5065 is rated High with a CVSS score of 8.8. 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-2026-5065?

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

What does CVE-2026-5065 affect?

CVE-2026-5065 affects IBM Controller 11.0.1, IBM Controller 11.1.0, IBM Controller 11.1.1, IBM Controller 11.1.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-5065?

Patch when released; rotate credentials; restrict access

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

executive summary
technical analysis
affected
IBM Controller 11.0.1IBM Controller 11.1.0IBM Controller 11.1.1IBM Controller 11.1.2
impact

Bypass authentication to internal modules via hard-coded credentials, enabling unauthorized access and potential data exposure.

action required

Patch when possible

affected versions
IBM Controller
  • affected>= 11.0.1 and <= 26.0.0.5
  • affected11.1.0
  • affected11.1.1
  • affected11.1.2

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