CVE-2026-27895
Ldap-Account-Manager Ldap Account Manager 8.5 – 9.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2026-27895 is a medium-severity Incorrect Regular Expression (CWE-185) vulnerability in Ldap-Account-Manager Ldap Account Manager. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked at the 35th 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 SA-15 (Development Process, Standards, and Tools) — 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-27895 affects LDAP Account Manager (LAM), a web-based frontend for managing LDAP directory entries such as users, groups, and DHCP settings. In versions prior to 9.5, the PDF export component fails to properly validate uploaded file extensions, enabling the upload of arbitrary file types, including PHP files. This vulnerability, classified under CWE-185 (Incorrect Regular Expression) with a CVSS v3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N), stems from inadequate input validation in the file upload process.
An attacker with low-privileged access (PR:L), such as an authenticated LAM user, can exploit this over the network with low complexity and no user interaction required. By uploading malicious files disguised through the PDF export feature, they can achieve file upload integrity violations. When combined with GHSA-w7xq-vjr3-p9cf, this leads to remote code execution as the web server user.
LAM version 9.5 resolves the issue, and upgrading is the recommended mitigation. As a workaround, administrators can make the /var/lib/ldap-account-manager/config directory read-only for the web server user. Relevant advisories and the patch release are detailed in GitHub security advisories GHSA-88hf-2cjm-m9g8, GHSA-w7xq-vjr3-p9cf, and the LAM 9.5 release notes.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-12682
Vulnerability Data
LDAP Account Manager (LAM) is a webfrontend for managing entries (e.g. users, groups, DHCP settings) stored in an LDAP directory. Prior to version 9.5, the PDF export component does not correctly validate uploaded file extensions. This way any file type…
more
(including .php files) can be uploaded. With GHSA-w7xq-vjr3-p9cf, an attacker can achieve remote code execution as the web server user. Version 9.5 fixes the issue. Although upgrading is recommended, a workaround would be to make /var/lib/ldap-account-manager/config read-only for the web-server user.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover regex that fails to match or compare data as intended.
Requiring documented development standards and tools reduces the chance that incorrect regular expressions are written into validation or filtering logic.
An SDLC that incorporates security can embed reviews or tooling that catch malformed regular expressions before deployment.
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 correct regex design, testing, and review to avoid improper matching.
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 can detect regex-related flaws before release.
Secure development lifecycle includes validation of input-handling constructs such as regex.
Application security requirements can mandate correct regex design and testing.
Secure coding standards directly address proper construction and review of regular expressions.