Cyber Resilience

CVE-2025-36419

Ibm Applinx 11.1.0

Published
20 January 2026
Modified
26 January 2026
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0021 11th percentile
Risk Priority 35 floored blend · peak EPSS

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, ranked at the 11th 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) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A10:2025 Mishandling of Exceptional Conditions

EU & UK References

Vulnerability Data

IBM ApplinX 11.1 could disclose sensitive information about server architecture that could aid in further attacks against the system.

CWE(s)
CWE-550

Related Threats

CVEs Like This One

CVE-2024-49792Same product: Ibm Applinx
CVE-2024-49794Same product: Ibm Applinx
CVE-2024-49793Same product: Ibm Applinx
CVE-2025-36410Same product: Ibm Applinx
CVE-2024-49791Same product: Ibm Applinx
CVE-2025-36409Same product: Ibm Applinx
CVE-2024-49795Same product: Ibm Applinx
CVE-2024-49797Same product: Ibm Applinx
CVE-2025-36411Same product: Ibm Applinx
CVE-2025-36408Same product: Ibm Applinx

Affected Assets

ibm
applinx
11.1.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-11 Error Handling
  • SC-7 Boundary Protection
  • AC-4 Information Flow Enforcement
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

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

Mitigating Controls (NIST 800-53 r5) AI

SI-11 Error Handling good match
prevent

Directly requires error conditions to be handled without revealing sensitive server architecture details that CWE-550 exposes.

SC-7 Boundary Protection partial match
prevent

Boundary protection mechanisms can filter or suppress architecture-revealing responses before they reach external attackers.

AC-4 Information Flow Enforcement partial match
prevent

Enforces information flow rules that prevent unauthorized disclosure of internal system details to untrusted parties.

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 full match
prevents

Secure SDLC explicitly requires sanitized error handling and information disclosure controls.

PR.PS-01 mostly match
prevents

Hardened baselines and config management directly suppress verbose server error output.

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.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing can detect and require remediation of verbose error messages.

A.8.15 Logging partial match
degrades

Logging policy can require suppression of sensitive data in error responses.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates handling of error messages to avoid information disclosure.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify safe error handling and generic messages.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles include proper exception handling to prevent leakage.

A.8.28 Secure coding partial match
prevents

Secure coding standards prohibit embedding sensitive data in server error messages.

References