CVE-2025-37734

4.3 MEDIUM

📋 TL;DR

An origin validation error in Kibana's Observability AI Assistant allows attackers to perform Server-Side Request Forgery (SSRF) by forging the Origin HTTP header. This vulnerability affects Kibana instances with the Observability AI Assistant feature enabled, potentially allowing attackers to make unauthorized requests from the Kibana server to internal systems.

💻 Affected Systems

Products:
  • Kibana
Versions: Versions 8.19.0 to 8.19.6, 9.1.0 to 9.1.6, and 9.2.0
Operating Systems: All supported operating systems
Default Config Vulnerable: ✅ No
Notes: Only vulnerable when the Observability AI Assistant feature is enabled and configured.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Attackers could access sensitive internal services, exfiltrate data from internal systems, or pivot to attack other internal infrastructure via the Kibana server.

🟠

Likely Case

Limited SSRF to internal services accessible from the Kibana server, potentially exposing metadata or limited internal resources.

🟢

If Mitigated

No impact if proper network segmentation and access controls prevent the Kibana server from reaching sensitive internal systems.

🌐 Internet-Facing: MEDIUM - Internet-facing Kibana instances are vulnerable if the Observability AI Assistant is enabled, but exploitation requires specific conditions.
🏢 Internal Only: MEDIUM - Internal Kibana instances could be exploited by authenticated users or attackers who gain internal access.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: MEDIUM

Exploitation requires knowledge of the Observability AI Assistant endpoint and ability to forge HTTP headers. Authentication requirements depend on Kibana configuration.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Kibana 8.19.7, 9.1.7, and 9.2.1

Vendor Advisory: https://discuss.elastic.co/t/kibana-8-19-7-9-1-7-and-9-2-1-security-update-esa-2025-24/383381

Restart Required: Yes

Instructions:

1. Download the patched version from Elastic's official repository. 2. Backup your Kibana configuration and data. 3. Stop the Kibana service. 4. Install the patched version. 5. Restart the Kibana service. 6. Verify the version is updated.

🔧 Temporary Workarounds

Disable Observability AI Assistant

all

Temporarily disable the vulnerable feature until patching can be completed

Edit kibana.yml and set: xpack.observability.aiAssistant.enabled: false
Restart Kibana service

Restrict Network Access

all

Implement network controls to limit Kibana server outbound connections

Configure firewall rules to restrict Kibana server egress to only required destinations

🧯 If You Can't Patch

  • Disable the Observability AI Assistant feature completely
  • Implement strict network segmentation to prevent Kibana from accessing sensitive internal systems

🔍 How to Verify

Check if Vulnerable:

Check Kibana version and verify if Observability AI Assistant is enabled in kibana.yml configuration

Check Version:

curl -X GET 'http://localhost:5601/api/status' | grep 'number'

Verify Fix Applied:

Verify Kibana version is 8.19.7, 9.1.7, or 9.2.1 or higher using the version check command

📡 Detection & Monitoring

Log Indicators:

  • Unusual requests to Observability AI Assistant endpoints
  • HTTP requests with forged Origin headers
  • Outbound connections from Kibana to unexpected internal systems

Network Indicators:

  • Unexpected outbound HTTP/HTTPS traffic from Kibana server to internal systems
  • Requests to internal services with Kibana User-Agent

SIEM Query:

source="kibana.log" AND ("ai_assistant" OR "observability") AND (status!=200 OR method=POST)

🔗 References

📤 Share & Export