Vulnerability from bitnami_vulndb
Published
2026-01-16 08:42
Modified
2026-01-16 09:10
Summary
Allocation of Resources Without Limits or Throttling in Kibana Leading to Excessive Allocation
Details
Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana Fleet can lead to Excessive Allocation (CAPEC-130) via a specially crafted request. This causes the application to perform redundant processing operations that continuously consume system resources until service degradation or complete unavailability occurs.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "kibana",
"purl": "pkg:bitnami/kibana"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "8.19.10"
},
{
"introduced": "9.0.0"
},
{
"fixed": "9.1.10"
},
{
"introduced": "9.2.0"
},
{
"fixed": "9.2.4"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
]
}
],
"aliases": [
"CVE-2026-0530"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:elasticsearch:kibana:*:*:*:*:*:node.js:*:*"
],
"severity": "Medium"
},
"details": "Allocation of Resources Without Limits or Throttling (CWE-770) in Kibana Fleet can lead to Excessive Allocation (CAPEC-130) via a specially crafted request. This causes the application to perform redundant processing operations that continuously consume system resources until service degradation or complete unavailability occurs.",
"id": "BIT-kibana-2026-0530",
"modified": "2026-01-16T09:10:29.256Z",
"published": "2026-01-16T08:42:13.351Z",
"references": [
{
"type": "WEB",
"url": "https://discuss.elastic.co/t/kibana-8-19-10-9-1-10-9-2-4-security-update-esa-2026-03/384521"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0530"
}
],
"schema_version": "1.6.2",
"summary": "Allocation of Resources Without Limits or Throttling in Kibana Leading to Excessive Allocation"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…