Cyber Resilience

CVE-2026-75020

Apache Apisix 2.11.0 – 3.18.0

Published
27 August 2026
Modified
31 August 2026
Patch / advisory
CVSS Score v4 7.0
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N/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:X
EPSS Score 0.0054 44th percentile
Risk Priority 42 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-75020 is a high-severity LDAP Injection (CWE-90) vulnerability in Apache Apisix. Its CVSS base score is 7.0 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 44th 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.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache APISIX. A caller who holds valid credentials for one entry in the LDAP directory can authenticate through APISIX as a consumer mapped to a different…

more

entry, one the plugin's configured scope was meant to keep out of reach. This issue affects Apache APISIX: from 2.11.0 through 3.17.0. Users are recommended to upgrade to version 3.18.0, which fixes the issue.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-49871Same product: Apache Apisix
CVE-2024-32638Same product: Apache Apisix
CVE-2026-63041Same product: Apache Apisix
CVE-2025-46647Same product: Apache Apisix
CVE-2026-31908Same product: Apache Apisix
CVE-2026-39998Same product: Apache Apisix
CVE-2026-47339Same product: Apache Apisix
CVE-2026-49872Same product: Apache Apisix
CVE-2026-49230Same product: Apache Apisix
CVE-2026-44930Same vendor: Apache

Affected Assets

apache
apisix
2.11.0 — 3.18.0

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • 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.

PR.PS-06 partial match
prevents

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.

prevents

Secure development lifecycle mandates input validation and query construction practices that directly prevent LDAP injection.

prevents

Application security requirements include explicit rules for safe construction of directory queries, mitigating LDAP injection.

prevents

Secure coding standards require proper neutralization of LDAP special characters, directly eliminating this weakness.

finds

Security testing in development catches LDAP injection via dynamic analysis or fuzzing, but does not prevent it at the source.

mitigates

Secure architecture principles encourage safe query interfaces but do not prescribe the specific coding controls needed for LDAP injection.

References