VulnerabilityPublished 3 Mar 2026Updated 4 Mar 2026

CVE-2025-36363: IBM DevOps Plan · Improper Restriction of Excessive Authentication Attempts

Affects IBM DevOps PlanSource CVE Database V5

Compare

Not known to be exploited · CVSS 5.9 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score

5.9Medium

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

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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

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

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).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
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.
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.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 29 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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
IBMDevOps Plan	Affected >=3.0.0 <=3.0.5	Fixed in–

CPE configurations (2)

cpe:2.3:a:ibm:devops_plan:3.0.0:*:*:*:*:*:*:*
cpe:2.3:a:ibm:devops_plan:3.0.5:*:*:*:*:*:*:*

AI-suggested

To mitigate CVE-2025-36363, organizations should implement the following specific measures: 1) Apply any available patches or updates from IBM promptly once released to address the account lockout weakness. 2) Configure or enforce stricter account lockout policies that limit the number of failed login attempts and introduce progressive delays or temporary account suspension to hinder brute force attempts. 3) Deploy multi-factor authentication (MFA) for all user accounts accessing IBM DevOps Plan to add an additional layer of security beyond passwords. 4) Monitor authentication logs closely for unusual patterns indicative of brute force attacks, such as repeated failed login attempts from the same IP addresses or accounts. 5) Employ network-level protections such as rate limiting, IP blacklisting, or web application firewalls (WAFs) to reduce attack surface exposure. 6) Educate users on strong password practices and consider integrating password complexity requirements. 7) Isolate IBM DevOps Plan instances within secure network segments to limit exposure. These steps go beyond generic advice by focusing on compensating controls and proactive monitoring tailored to this vulnerability's characteristics.

Description

IBM DevOps Plan 3.0.0 through 3.0.5 uses an inadequate account lockout setting that could allow a remote attacker to brute force account credentials.

Impact

The primary impact of CVE-2025-36363 is the potential compromise of user accounts through brute force attacks, leading to unauthorized access to sensitive project and operational data within IBM DevOps Plan environments. Confidentiality is significantly affected as attackers may gain access to credentials or proprietary information. Integrity and availability are not directly impacted by this vulnerability. Organizations using affected versions risk data breaches, intellectual property theft, and potential lateral movement within their networks if attackers leverage compromised accounts. The medium severity score reflects that exploitation requires high attack complexity but no privileges or user interaction, making it moderately accessible to skilled attackers. The widespread use of IBM DevOps Plan in enterprise environments means that a successful attack could disrupt development workflows and expose critical business information, especially in sectors with high reliance on secure DevOps processes.

CWE-307Improper Restriction of Excessive Authentication Attempts (opens in a new tab)
Base weaknessOWASP Top 10 A07:2025: Authentication Failures (opens in a new tab)
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
Architecture and Design
Common protection mechanisms include: Disconnecting the user after a small number of failed attempts; Implementing a timeout; Locking out a targeted account; Requiring a computational task on the user's part.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authentication (opens in a new tab)
Transport Layer Protection (opens in a new tab)
TLS Cipher String (opens in a new tab)
OWASP ASVS 4.0.3
V2.2.1 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Dictionary-based Password Attack (opens in a new tab)
Password Brute Forcing (opens in a new tab)
Password Spraying (opens in a new tab)
Credential Stuffing (opens in a new tab)
Use of Known Kerberos Credentials (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

ibm.com/support/pages/node/7261934 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

CPE configurations (2)

Description

AI analysisMachine-generated, updated 11 Mar 2026, 20:12 UTC

WeaknessesCWE-307

Technical details

References

Community reviews

Related threats