CVE-2026-39962
Misp ≤ 2.5.36
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2026-39962 is a high-severity LDAP Injection (CWE-90) vulnerability in Misp Misp. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 27th 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-39962 is an LDAP injection vulnerability in MISP, an open source threat intelligence and sharing platform. It affects versions prior to 2.5.36, specifically in the ApacheAuthenticate.php component, where an unsanitized username value is used in an LDAP query. The issue arises when ApacheAuthenticate.apacheEnv is configured to rely on a user-controlled server variable rather than REMOTE_USER, such as in certain proxy setups, leading to improper neutralization of special elements (CWE-90). The vulnerability has a CVSS v3.1 base score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).
An unauthenticated attacker with network access can exploit this vulnerability if they control the relevant server variable, requiring some user interaction. By injecting malicious content into the username value, they can manipulate the LDAP search filter, potentially bypassing authentication constraints or executing unauthorized LDAP queries against the directory.
Mitigation is available in MISP version 2.5.36, which includes fixes via commits such as 380ee4136a7d9ce2fe63fce06d517839f30aba10 and d7d671ea8f5822e91207dcad2003c35c30092a32. Security practitioners should upgrade to this release and review configurations to ensure ApacheAuthenticate.apacheEnv does not use user-controlled variables. Additional details are provided in the MISP security advisory GHSA-mc53-48w8-9g63 and the v2.5.36 release notes.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-20966
Vulnerability Data
MISP is an open source threat intelligence and sharing platform. Prior to 2.5.36, improper neutralization of special elements in an LDAP query in ApacheAuthenticate.php allows LDAP injection via an unsanitized username value when ApacheAuthenticate.apacheEnv is configured to use a user-controlled…
more
server variable instead of REMOTE_USER (such as in certain proxy setups). An attacker able to control that value can manipulate the LDAP search filter and potentially bypass authentication constraints or cause unauthorized LDAP queries. This vulnerability is fixed in 2.5.36.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover LDAP injection flaws through static analysis or crafted test cases.
Input validation directly stops untrusted data from reaching an LDAP query builder without neutralization of special characters.
Secure engineering principles require safe query construction and escaping that structurally prevents LDAP injection.
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.
Secure SDLC practices directly require input neutralization and query parameterization to prevent LDAP injection.
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 in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.
Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.
Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.
Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.
Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.
Information access restriction limits who can query LDAP but does not address how queries are built.