Elastic has released a security advisory addressing an origin validation error in Kibana that could expose systems to Server-Side Request Forgery (SSRF) attacks.
The vulnerability, tracked as CVE-2025-37734, affects multiple versions of the popular data visualization and exploration platform and has prompted immediate patching across all affected deployments.
| CVE ID | Vulnerability | Affected Versions | CVSS Score | Fixed Versions |
|---|---|---|---|---|
| CVE-2025-37734 | Origin Validation Error (SSRF) | Kibana 8.12.0–8.19.6, 9.1.0–9.1.6, 9.2.0 | 4.3 (Medium) | 8.19.7, 9.1.7, 9.2.1 |
The security flaw stems from improper origin validation in Kibana’s Observability AI Assistant component.
Attackers can exploit this weakness by crafting forged Origin HTTP headers to bypass security checks, enabling them to perform unauthorized server-side requests.
The vulnerability allows threat actors to access internal systems and services that should be protected from external access.
This type of attack is particularly concerning because it can lead to data exfiltration, unauthorized access to internal resources, and potential lateral movement within compromised networks.
The Observability AI Assistant processes these headers without sufficient validation, creating a window of opportunity for exploitation.
The vulnerability affects a wide range of Kibana deployments across multiple versions. Organizations running Kibana 8.12.0 through 8.19.6, 9.1.0 through 9.1.6, and version 9.2.0 are at immediate risk.
However, the impact is limited to deployments specifically using the Observability AI Assistant feature.
According to Elastic’s official security announcement, the vulnerability has a CVSS score of 4.3, which is Medium severity. The attack requires low privileges and no user interaction, making it relatively accessible to potential threat actors with basic network access.
Elastic has released security updates addressing this vulnerability in three major releases. Organizations should immediately upgrade to version 8.19.7, 9.1.7, or 9.2.1, depending on their current deployment version.
Notably, Elastic Cloud Serverless users are already protected. Due to Elastic’s continuous deployment model, the vulnerability was patched before public disclosure, eliminating the exposure window for serverless customers.
Security teams should prioritize upgrading affected Kibana instances to patched versions.
For organizations unable to upgrade immediately, Elastic recommends temporarily disabling the Observability AI Assistant as a mitigation until patches can be applied.
Administrators should also audit access logs and monitor for suspicious origin headers or unusual server-side requests that might indicate exploitation attempts.
This proactive approach helps identify potential breaches before significant damage occurs.
Follow us on Google News, LinkedIn, and X to Get Instant Updates and set GBH as a Preferred Source in Google.
Attackers abused compromised ConnectWise Cloud Backup credentials to access Microsoft 365 customer environments, prompting ConnectWise…
Anthropic says an internal Claude research model reconstructed how the National Security Agency generated seeds…
Two WordPress Core vulnerabilities can be chained to execute remote code without authentication, according to…
A newly disclosed OpenBSD kernel exploitation chain combines a shared memory accounting flaw with a…
GhostAction attackers have expanded their GitHub credential theft campaign with a second stage that disguises…
Indian authorities have warned that SideCopy hackers are targeting Indian organizations, including academic institutions, with…