CVE-2026-63041
Apache Apisix 3.11.0 – 3.18.0
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-63041 is a medium-severity Reliance on Untrusted Inputs in a Security Decision (CWE-807) vulnerability in Apache Apisix. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 49% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to AC-24 (Access Control Decisions) 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
- 🇪🇺 ENISA EUVD: EUVD-2026-66409
Vulnerability Data
Reliance on Untrusted Inputs in a Security Decision vulnerability in Apache APISIX. This vulnerability allows an attacker to escalate privilege or perform an authorization bypass by sending certain values that the attach-consumer-label plugin does not sanitise correctly. This issue affects…
more
Apache APISIX: from 3.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
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Explicitly requires that every access decision be based on authoritative, protected decision data rather than caller-supplied inputs.
Input validation can reject malformed or attacker-controlled values before they reach a security decision point.
Access enforcement requires decisions to be made from trusted policy data rather than modifiable client-supplied inputs.
Information-flow enforcement applies rules to validated, internal attributes instead of untrusted external values.
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.
Proper management of identities/credentials reduces the chance that security decisions will be driven by untrusted inputs.
Strong authentication mechanisms directly prevent security decisions from depending on modifiable, untrusted inputs.
Verification and protection of identity assertions stops reliance on attacker-controlled values for authorization decisions.
Policy-driven, least-privilege authorization reduces opportunities to bypass controls via tampered inputs.
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.
Monitoring can detect exploitation but does not stop the underlying weakness.
Application security requirements explicitly call for validation of inputs used in security decisions.
Secure architecture principles mandate treating all external inputs as untrusted.
Secure coding standards directly prohibit using untrusted inputs for security-critical decisions.
Security testing in development catches input-validation flaws before deployment.
Access-control rules can be bypassed if they rely on untrusted inputs.