Cyber Resilience

CVE-2025-36371

Ibm I 7.2 … 7.6

Published
19 November 2025
Modified
24 November 2025
Patch / advisory
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0027 18th percentile
Risk Priority 49 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2025-36371 is a medium-severity Use of HTTP Request With Sensitive Query String (CWE-598) vulnerability in Ibm I. Its CVSS base score is 6.5 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Network Sniffing (T1040); ranked at the 18th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-8 (Transmission Confidentiality and Integrity) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

IBM i 7.2, 7.3, 7.4, 7.5, and 7.6 are impacted by obtaining an information vulnerability in the database plan cache implementation.  A user with access to the database plan cache could see information they do not have authority to view.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1040 Network Sniffing Credential Access
Adversaries may passively sniff network traffic to capture information about an environment, including authentication material passed over the network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-17075Same product: Ibm I
CVE-2026-16867Same product: Ibm I
CVE-2026-17101Same product: Ibm I
CVE-2026-17197Same product: Ibm I
CVE-2026-17099Same product: Ibm I
CVE-2026-17045Same product: Ibm I
CVE-2024-27275Same product: Ibm I
CVE-2026-17445Same product: Ibm I
CVE-2026-4942Same product: Ibm I
CVE-2024-27264Same product: Ibm I

Affected Assets

ibm
i
7.2, 7.3, 7.4, 7.5, 7.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.4.5
  • V14.2.1

Mitigating Controls (NIST 800-53 r5) AI

Requiring confidentiality and integrity protection for transmitted data reduces exposure of sensitive query parameters even though the control does not forbid placing secrets in URLs.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly prevent embedding sensitive data in query strings as part of input-handling and data-flow design.

PR.DS-02 partial match
prevents

HTTPS encryption protects query strings in transit but does not address the root design flaw of placing sensitive data in URLs.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing can detect sensitive data leakage via query strings.

mitigates

DLP solutions can detect and block sensitive data in URLs.

degrades

Network security controls can enforce HTTPS and block sensitive data in URLs.

prevents

Application security requirements should mandate avoiding sensitive data in query strings.

prevents

Secure architecture principles discourage exposing sensitive data in URLs.

prevents

Secure coding standards directly prohibit placing secrets in query parameters.

References