Kibana code execution issue
Key facts
- Attack vector
- Network
- Privileges required
- High
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Code execution
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-94.
Summary
It was discovered that a user with Fleet admin permissions could upload a malicious package. Due to using an older version of the js-yaml library, this package would be loaded in an insecure manner, allowing an attacker to execute commands on the Kibana server.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA Kibana (Elastic) Fixed in 7.14.0
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Elastic Kibana 7.14.0
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2021-05141 Kibana path traversal issuePriority LOW 21
Timeline
- 2026-10-02 Threatist record created from CVE-2021-22150
- 2026-10-03 Alias added: GHSA-534g-6jq4-vq89
References
More Elastic Kibana vulnerabilities
- TI-2019-05363 Code injection in Elastic Kibana KEVCVSS 3.1CRITICAL 10.0
- TI-2018-12328 Kibana versions before 6.4.3 and 5.6.13 contain an arbitrary file inclusion flaw in the… CVSS 3.0CRITICAL 9.8
- TI-2025-18692 Kibana arbitrary code execution via prototype pollution CVSS 3.1CRITICAL 9.8
- TI-2020-05660 Code injection in Elastic Kibana CVSS 3.1HIGH 8.8
- TI-2024-24803 Deserialization of untrusted data in Elastic Kibana CVSS 3.1CRITICAL 9.9
- TI-2024-24800 Kibana arbitrary code execution via YAML deserialization CVSS 3.1CRITICAL 9.1
Sources
- CVE-2021-22150 · CVE Program
- CVE-2021-22150 · NVD
- FIRST EPSS
- GHSA-534g-6jq4-vq89 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences