VulnerabilityPublished 17 Mar 2026

CVE-2026-27895: LDAPAccountManager lam · Incorrect Regular Expression

Affects LDAPAccountManager lamSource CVE Database V5

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 9.5 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 9.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 17 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade lam and ldapaccountmanager/lam to 9.5.

Affected software

Product	Affected	Fixed in
LDAPAccountManagerlam	Affected <9.5	Fixed in 9.5
GitHubldapaccountmanager/lam`pkg:github/ldapaccountmanager/lam`Other threats	Affected <9.5	Fixed in 9.5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade LDAP Account Manager to version 9.5 or later, where the file extension validation issue is fixed.
As an immediate workaround, change the permissions of /var/lib/ldap-account-manager/config to be read-only for the web server user to prevent unauthorized file uploads.
Implement strict access controls and monitoring on the LAM server, including limiting user accounts that can upload files.
Employ web application firewalls (WAFs) to detect and block suspicious file upload attempts targeting the PDF export functionality.
Regularly audit uploaded files and server directories for unauthorized or unexpected files.
Monitor logs for unusual activity related to file uploads and execution attempts.
Consider isolating the LAM server in a segmented network zone to limit potential lateral movement if compromised.

Description

CVE-2026-27895 is a medium severity vulnerability in LDAP Account Manager (LAM) versions prior to 9.5, where the PDF export component improperly validates uploaded file extensions. This flaw allows attackers with limited privileges to upload arbitrary file types, including executable PHP files, potentially leading to remote code execution as the web server user. The vulnerability arises from an incorrect regular expression validation (CWE-185) that fails to restrict file uploads properly. Although no known exploits are currently in the wild, successful exploitation could compromise the integrity of affected systems. The issue is fixed in LAM version 9.5, and a recommended workaround is to make the configuration directory read-only for the web server user. Organizations using LAM for LDAP management should prioritize upgrading or applying mitigations to prevent exploitation.

Impact

If exploited, this vulnerability allows an authenticated attacker to upload arbitrary files, including executable scripts, to the LAM server. This can lead to remote code execution with the privileges of the web server user, potentially allowing attackers to manipulate LDAP data, escalate privileges, or pivot within the network. While the confidentiality impact is minimal since the vulnerability does not directly expose data, the integrity of LDAP entries and the availability of the service could be compromised through malicious code execution. Organizations using LAM in critical infrastructure or identity management roles could face significant operational disruptions and security breaches. The medium CVSS score reflects the need for authentication and the limited scope of impact, but the risk remains notable due to the potential for lateral movement and further exploitation post-compromise.

CWE-185Incorrect Regular Expression (opens in a new tab)
Base weakness
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
Implementation · Refactoring
Regular expressions can become error prone when defining a complex language even for those experienced in writing grammars. Determine if several smaller regular expressions simplify one large regular expression.
Attack patterns
Command Delimiters (opens in a new tab)
Argument Injection (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 25 Mar 2026, 01:02 UTC

WeaknessesCWE-185

Technical details

References

Community reviews

Related threats