CVE-2025-36419
Ibm Applinx 11.1.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-36419 is a medium-severity Server-generated Error Message Containing Sensitive Information (CWE-550) vulnerability in Ibm Applinx. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique System Information Discovery (T1082); ranked at the 12th 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 SI-11 (Error Handling) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-3379
Vulnerability Data
IBM ApplinX 11.1 could disclose sensitive information about server architecture that could aid in further attacks against the system.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V14.2.1
Mitigating Controls (NIST 800-53 r5) AI
SI-11 directly requires error messages to avoid revealing exploitable information, structurally preventing the exact leakage described by CWE-550.
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.
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.
Security testing can detect and require remediation of verbose error messages.
Logging policy can require suppression of sensitive data in error responses.
Secure SDLC mandates handling of error messages to avoid information disclosure.
Application security requirements can specify safe error handling and generic messages.
Secure architecture principles include proper exception handling to prevent leakage.
Secure coding standards prohibit embedding sensitive data in server error messages.