Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local low-privilege access to host
-
ExploitAuthenticate using default install/manufacturing credentials
-
ImpactBypass authentication for full component compromise
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Default credential prevention
|
| Exploitation Conditions | Exploitation requires that the default passwords provisioned during the installation/manufacturing process were never changed to unique values on the deployed instance; an attacker then uses those known default credentials to bypass authentication. Per IBM's CVSS the attacker must have local access to the host (AV:L) and some low-level existing privilege (PR:L), which materially limits reach compared with a remote unauthenticated flaw - this is the key limiting factor defenders should weigh. The description does not state whether the affected login is network-exposed, so network reachability cannot be confirmed from the available sources. Affected versions span 1.3.2.0, 1.3.3.0, 1.3.5.0-1.3.5.3, 1.3.6.0-1.3.6.1, 1.3.7.0-1.3.7.2, and 1.3.8.0-1.3.8.4 (per EUVD/CPE). |
| Impact | Signals point to a genuinely high technical impact but a low real-world exploitation likelihood, so this reads as a serious-but-not-urgent issue rather than an active threat. The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects total compromise of confidentiality, integrity, and availability once reached, and SSVC agrees on Technical Impact: total. However, SSVC also records Exploitation: none and Automatable: no, EPSS is only 0.02% (5th percentile), there is no CISA KEV listing, and no public exploit or PoC reference is provided - only the IBM vendor advisory. Exploitation status is therefore: no public exploit identified at time of analysis. One conflict to verify with the vendor: the description frames this as an authentication bypass via default credentials, which usually implies a network-reachable login, yet IBM's own vector is AV:L (local) with PR:L (authenticated/low-privilege) - the local vector materially lowers real-world reach, so confirm with IBM whether the affected login/installation interface is network-exposed. The vuln.today priority of 'this_week' aligns with patching in the normal cycle rather than treating it as an emergency. |
| Exploit ScenarioDerived | An attacker who already has local, low-privilege access to a host running IBM Operations Analytics / SmartCloud Analytics - Log Analysis uses a known default password left over from the manufacturing/installation process to bypass authentication and obtain full control of the component. Because the credentials are factory defaults, no exploit development is needed once the attacker reaches the interface, though per IBM's CVSS the attacker needs local access (AV:L) and low existing privileges (PR:L). No public PoC or exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 26, 2026
Authentication can be bypassed on IBM Operations Analytics - Log Analysis deployments that still carry the default passwords created during the manufacturing/installation process, giving an attacker access to the installation instead of being challenged at login. Per IBM's published vector the attacker needs local access to the host and low-level existing privileges (AV:L/PR:L), which materially limits reach; the sources do not confirm whether the affected login interface is network-exposed, and our own assessment scores the reachability as network/unauthenticated in the worst case. Technical impact is total if the default credentials are unrotated, but no public exploit has been identified at time of analysis, EPSS is 0.02% (5th percentile), and SSVC records exploitation as none and automatable as no, so this reads as serious-but-not-urgent and is tracked for remediation this week.
Earlier versions of this analysis (1)
Authentication bypass in IBM Operations Analytics - Log Analysis and IBM SmartCloud Analytics - Log Analysis (Operations Analytics versions 1.3.2.0 through 1.3.8.4) stems from hardcoded default credentials baked in during the manufacturing/installation process. An attacker who can reach the installation can authenticate with these known-default passwords, gaining full control with high confidentiality, integrity, and availability impact. The CVSS 3.1 vector scores this as a local-vector issue (AV:L) rather than remote, no public exploit has been identified, and SSVC reports exploitation status of 'none'.
RemediationAI
The decisive action is to replace the manufacturing-process default passwords with unique, strong values on every deployed instance of IBM Operations Analytics - Log Analysis and IBM SmartCloud Analytics - Log Analysis across the affected releases (1.3.2.0, 1.3.3.0, 1.3.5.x, 1.3.6.x, 1.3.7.x and 1.3.8.x); an installation that has never rotated these credentials remains exploitable regardless of other controls, and rotating them removes the bypass condition entirely. The supplied data does not list an exact fixed release version, so consult IBM's advisory at https://www.ibm.com/support/pages/node/7272268 for the vendor's stated remediation or fix level before planning the upgrade. Because the sources do not confirm whether the affected login interface is reachable over the network, treat credential rotation as the primary fix and verify the exposure of the login endpoint on each instance as part of the same change.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
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-1392, Use of Default Credentials: the product ships with passwords fixed during the manufacturing/installation process rather than generating or forcing a unique secret per deployment, so the credential is predictable and reusable across installations. Exploitation is entirely conditional on operator hygiene - it works only where the shipped default was never changed, meaning the vulnerable state is a deployment that was left at factory settings rather than a code-level memory or injection flaw. IBM's CPE inventory covers Operations Analytics - Log Analysis 1.3.2.0, 1.3.3.0, 1.3.5.0 through 1.3.5.3, 1.3.6.0 and 1.3.6.1, and 1.3.7.0 and 1.3.7.1; ENISA EUVD extends the affected range to 1.3.7.2 and 1.3.8.0 through 1.3.8.4, which are not represented in the supplied CPE list. IBM scored it 7.8 with the trigger requiring local access and low privileges; the description itself does not describe how the login is reached, so network reachability of the default-credential login remains unverified from the available sources.
Know when Operations Analytics Log Analysis gets its next vulnerability
- 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
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Default-credential use to bypass authentication means the attacker needs no legitimate privileges (PR:N); I assess AV:N for a networked analytics login, contrasting IBM's local AV:L - verify exposure with vendor.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionNVD
IBM Operations Analytics - Log Analysis and IBM SmartCloud Analytics - Log Analysis uses default passwords default passwords from the manufacturing process for use during the installation process, which could allow an attacker to bypass authentication.
Executive ViewAI
IBM Operations Analytics - Log Analysis deployments still using default manufacturing passwords are vulnerable to authentication bypass, allowing an attacker with local host access to gain unauthorized access. This poses a significant risk to data confidentiality, integrity, and compliance, particularly if such deployments are present in the environment. Leadership should prioritize identifying and remediating affected systems to prevent potential breaches.
No vendor-released patch identified at time of analysis; interim mitigations include changing default passwords, restricting local host access, and monitoring authentication logs for anomalies.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-32505
GHSA-9mxp-rq8m-qq98
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB