VulnerabilityPublished 21 Sep 2022Updated 28 May 2025

CVE-2022-40616: IBM Maximo Asset Management · Bypass Security

Affects IBM Maximo Asset ManagementSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.0/AC:L/AV:N/PR:N/UI:N/A:N/S:U/I:L/C:L/E:U/RC:C/RL:O

Base metrics

Attack Complexity: Low
Attack Vector: Network
Privileges Required: None
User Interaction: None
Availability: None
Scope: Unchanged
Integrity: Low
Confidentiality: Low

Temporal metrics

Exploit Code Maturity: Unproven
Report Confidence: Confirmed
Remediation Level: Official Fix

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Availability: None: There is no impact to availability within the impacted component.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 21 Sep 2022
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
IBM Maximo Asset Management	Affected =7.6.1.1 =7.6.1.2 =7.6.1.3	Fixed in–

AI-suggested

Organizations should immediately verify their IBM Maximo Asset Management versions and prioritize upgrading to patched versions once IBM releases them. In the absence of official patches, implement network-level controls such as restricting access to Maximo interfaces to trusted internal networks or VPNs. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious authentication bypass attempts. Conduct thorough access audits and monitor logs for unusual authentication patterns or unauthorized access attempts. Enforce strong segmentation between asset management systems and other corporate networks to limit lateral movement. Additionally, implement multi-factor authentication (MFA) where possible to add an extra layer of security, even though the vulnerability bypasses authentication, MFA may help mitigate other attack vectors. Regularly update and test incident response plans to quickly address potential exploitation. Finally, engage with IBM support channels to obtain official guidance and patches as they become available.

Description

IBM Maximo Asset Management 7.6.1.1, 7.6.1.2, and 7.6.1.3 could allow a user to bypass authentication and obtain sensitive information or perform tasks they should not have access to. IBM X-Force ID: 236311.

Impact

For European organizations, the impact of CVE-2022-40616 can be significant, especially for those relying on IBM Maximo Asset Management to oversee critical infrastructure and industrial operations. Unauthorized access could lead to exposure of sensitive operational data, intellectual property, and maintenance schedules, potentially enabling industrial espionage or sabotage. Integrity violations could result in unauthorized changes to asset configurations or maintenance records, leading to operational inefficiencies or safety risks. Given the role of Maximo in sectors like energy, transportation, and manufacturing, exploitation could disrupt supply chains or critical services. Additionally, regulatory compliance risks arise from unauthorized data access, potentially violating GDPR requirements for data protection. The absence of availability impact reduces the risk of direct service outages but does not eliminate the threat of indirect operational disruptions due to compromised data integrity or confidentiality.

CWE-287Improper Authentication (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Libraries or Frameworks
Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
OWASP Cheat Sheets
OWASP Authentication (opens in a new tab)
OWASP ASVS 4.0.3
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
V9.2.3 (opens in a new tab)
Attack patterns
Fake the Source of Data (opens in a new tab)
Utilizing REST's Trust in the System Resource to Obtain Sensitive Data (opens in a new tab)
Session Hijacking (opens in a new tab)
Token Impersonation (opens in a new tab)
Upload a Web Shell to a Web Server (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 7 Jul 2025, 09:11 UTC

WeaknessesCWE-287

Technical details

References

Community reviews

Related threats