Response playbooks, investigation guides, and Atomic Red Team tests are Pro-only. Upgrade to unlock the full detection package for CVE-2026-54735.

Unlock with Pro - from £29/user/mo
CVE-2026-54735 Splunk · SPL

Detect Prebid Server SSRF via Request Forgery (CVE-2026-54735) in Splunk

Detects exploitation of CVE-2026-54735, a critical (CVSS 10.0) server-side request forgery (SSRF) vulnerability in prebid/prebid-server affecting versions < 4.4.0, <= 3.30.0, <= 2.32.0, and <= 0.275.0. The flaw (CWE-918) allows an attacker to craft bid request or adapter/URL parameters that cause the prebid-server host to issue outbound requests to attacker-controlled or internal/cloud-metadata endpoints, potentially exfiltrating host environment data (cloud metadata credentials, internal service responses). Detection focuses on anomalous outbound HTTP requests originating from prebid-server processes/containers to internal RFC1918 ranges, loopback, link-local cloud metadata IPs (169.254.169.254), or unexpected external hosts triggered by bid/adapter request handling.

MITRE ATT&CK

Tactic
Initial Access Collection Command and Control

SPL Detection Query

Splunk (SPL)
spl
index=prebid_server sourcetype=prebid:access
| eval is_metadata=if(dest_ip="169.254.169.254",1,0)
| eval is_internal=if(match(dest_ip, "^(10\.|172\.(1[6-9]|2[0-9]|3[01])\.|192\.168\.|127\.)"),1,0)
| where (is_metadata=1 OR is_internal=1) AND (uri_path="/openrtb2/auction" OR uri_path="/openrtb2/amp" OR uri_path="/setuid" OR uri_path="/cookie_sync")
| stats count values(uri_path) as paths values(dest_ip) as destinations by src_ip, _time span=5m
| where count>1
critical severity medium confidence

Detects Splunk-ingested prebid-server access logs showing outbound requests originating from auction/amp/setuid/cookie_sync handlers directed at metadata service or internal IP ranges, consistent with SSRF exploitation.

Data Sources

Prebid-server access logsNetwork proxy/firewall logs

Required Sourcetypes

prebid:accessstream:http

False Positives & Tuning

  • Legitimate internal bidder adapter integrations
  • Internal health-check probes
  • Service mesh proxy hops through internal IP space
  • Dev/test environments with mock internal adapter endpoints

Other platforms for CVE-2026-54735


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1Simulate SSRF request to cloud metadata endpoint via crafted auction request

    Expected signal: Outbound HTTP connection from prebid-server process to 169.254.169.254 logged in network flow/access logs with source path /openrtb2/auction

  2. Test 2Simulate SSRF probe to internal RFC1918 service via cookie_sync endpoint

    Expected signal: Outbound HTTP connection from prebid-server process to internal IP 10.0.0.5 logged with request path /cookie_sync

  3. Test 3Version fingerprint check against vulnerable prebid-server release

    Expected signal: HTTP GET request to /status or /version endpoint logged in prebid-server access logs

  4. Test 4Simulate repeated metadata-scanning pattern via openrtb2/amp endpoint

    Expected signal: Multiple outbound HTTP connections from prebid-server process to distinct internal/metadata IPs within a short time window, logged with request path /openrtb2/amp

Unlock playbooks & atomic tests with Pro

Get the full detection package for CVE-2026-54735 — response playbook and atomic red team tests, plus investigation guidance and hunting queries.

df00tech Pro — £29/user/month

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections