CVE-2026-33458 json
Server-Side Request Forgery (SSRF) in Kibana One Workflow Leading to Information Disclosure
published 7mo ago modified 2mo ago also BIT-elk-2026-33458 , BIT-kibana-2026-33458 , EUVD-2026-20519
- cvss
- 6.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 14%
- public exploits
- 0
- none known
Summary
Server-Side Request Forgery (CWE-918) in Kibana One Workflow can lead to information disclosure. An authenticated user with workflow creation and execution privileges can bypass host allowlist restrictions in the Workflows Execution Engine, potentially exposing sensitive internal endpoints and data.
Patch / fix
- bitnami elk 9.3.3
- bitnami kibana 9.3.3
- elastic kibana 9.3.3
- elasticsearch kibana 9.3.3
Is CVE-2026-33458 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.24% chance of exploitation in the next 30 days, higher than 14% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.8 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVD | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| OSV | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | elk | >=9.3.0, <9.3.3 |
9.3.3 |
| bitnami | kibana | >=9.3.0, <9.3.3 |
9.3.3 |
Affected products
- Elastic Kibana
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
discuss.elastic.co
/t/kibana-9-3-3-security-update-esa-2026-28/385815
vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-33458
web
Sources
- CVE List CVE-2026-33458
- NVD CVE-2026-33458
- OSV BIT-elk-2026-33458
- OSV BIT-kibana-2026-33458
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.