{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-36363 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-36363 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-36363 is a medium-severity vulnerability in IBM DevOps Plan, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-36363 and fix it if it is affected.\n\nWhat it is: CVE-2025-36363 is a medium-severity vulnerability in IBM DevOps Plan, published on 3 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-36363 in the wild and no public exploit code.\n\nAffected product: IBM DevOps Plan. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-36363/ (Markdown: https://insights.sbomify.com/CVE-2025-36363/index.md)","id":"CVE-2025-36363","markdown":"https://insights.sbomify.com/CVE-2025-36363/index.md","name":"CVE-2025-36363","record":{"aliases":["GHSA-9jh8-xh9x-6w7f"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM DevOps Plan","requires_auth":"none","summary":"Remote attackers can brute force credentials due to inadequate account lockout settings in IBM DevOps Plan.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"devops_plan","vendor":"hcltech"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"IBM DevOps Plan is vulnerable to Excessive Authentication Attempts","id":"CVE-2025-36363","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"IBM DevOps Plan REST APIs are vulnerable to exposure of sensitive data through request query parameters.","id":"CVE-2025-36364"},"packages":[],"prev":{"headline":"IBM App Connect Enterprise runtime is vulnerable to a lack of authorization on windows environments using IWA","id":"CVE-2025-36361"},"products":["DevOps Plan"],"published":"2026-03-03","related":[{"cvss_score":6.9,"headline":"An information disclosure vulnerability affects HCL DevOps Plan","id":"CVE-2023-37507","kev_date_added":null,"published":"2026-07-21"},{"cvss_score":6.5,"headline":"Other in DevOps Plan","id":"CVE-2026-4096","kev_date_added":null,"published":"2026-06-11"},{"cvss_score":6.2,"headline":"IBM DevOps Plan REST APIs are vulnerable to exposure of sensitive data through request query parameters.","id":"CVE-2025-36364","kev_date_added":null,"published":"2026-03-03"},{"cvss_score":2.3,"headline":"HCL DevOps Plan is susceptible to a Cross-Site Scripting (XSS) vulnerability","id":"CVE-2023-37508","kev_date_added":null,"published":"2026-07-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-04","vendors":["IBM"]},"summary":"Remote attackers can brute force credentials due to inadequate account lockout settings in IBM DevOps Plan.","url":"https://insights.sbomify.com/CVE-2025-36363/"}