What is the CVSS score of EUVD-2026-24947?

EUVD-2026-24947 has a CVSS 3.1 base score of 5.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.0%.

Is there a patch available for EUVD-2026-24947?

Yes, a patch is available for EUVD-2026-24947. Update the affected software to the latest version immediately.

PowerDNS Authoritative EUVD-2026-24947

| CVE-2026-33609 MEDIUM

LDAP Injection (CWE-90)

2026-04-22 security@open-xchange.com

GHSA-q8p8-x4x3-fvqm

Information Disclosure LDAP Code Injection Suse

5.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

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

SUSE

MEDIUM

qualitative

Primary rating from NVD.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Lifecycle Timeline

Patch released

Apr 24, 2026 - 18:52 nvd

Patch available

Apr 22, 2026 - 16:33 EUVD

Analysis Generated

Apr 22, 2026 - 15:02 vuln.today

EUVD ID Assigned

Apr 22, 2026 - 14:22 euvd

EUVD-2026-24947

Analysis Generated

Apr 22, 2026 - 14:22 vuln.today

CVE Published

Apr 22, 2026 - 14:16 nvd

MEDIUM 5.3

DescriptionCVE.org

Incomplete escaping of LDAP queries when running with 8bit-dns enabled allows users to perform queries of internal domain subtrees.

AnalysisAI

Incomplete LDAP query escaping in PowerDNS Authoritative with 8bit-dns enabled allows authenticated users to enumerate internal domain subtrees through LDAP injection, leading to information disclosure of sensitive DNS zone data. The vulnerability requires valid authentication, high attack complexity due to LDAP protocol constraints, and has been reported by the vendor security team. No active exploitation data is currently available.

Technical ContextAI

PowerDNS Authoritative Server processes DNS queries and supports backend storage mechanisms including LDAP directories. When the 8bit-dns feature is enabled, the server processes non-ASCII characters in DNS names. The vulnerability stems from improper sanitization of user-controlled input in LDAP query construction, allowing attackers to inject LDAP filter syntax. This is a classic example of CWE-90 (Improper Neutralization of Special Elements used in an LDAP Query) where special LDAP characters such as parentheses, asterisks, and boolean operators are not properly escaped before query execution. The LDAP backend then interprets the injected syntax as structural query logic rather than literal data, enabling unauthorized directory traversal and enumeration.

RemediationAI

Immediately review and apply the vendor-released security patch from PowerDNS advisory powerdns-2026-05 (https://docs.powerdns.com/authoritative/security-advisories/powerdns-advisory-powerdns-2026-05.html) to update your PowerDNS Authoritative installation to a patched version. As an interim control, if LDAP backend usage is not essential, disable LDAP authentication backends in the PowerDNS configuration and switch to alternative storage mechanisms (MySQL, PostgreSQL, or SQLite) until patching is complete. Alternatively, if 8bit-dns feature is not operationally required, disable it in the PowerDNS configuration file (set allow-8bit=no or equivalent) to eliminate the attack vector; this may impact internationalized domain name (IDN) support if your infrastructure depends on it. Restrict LDAP backend access to trusted networks only via firewall rules at the network boundary, limiting the pool of authenticated users who can reach the vulnerable code path.