CVE-2026-54734

10.0

Prebid · prebid-server-java

Prebid Server Java is vulnerable to Server-Side Request Forgery due to improper validation of user-supplied parameters in bidder adapters, allowing unauthenticated attackers to reach internal services.

Executive summary

A critical Server-Side Request Forgery vulnerability in Prebid Server Java allows unauthenticated remote attackers to perform unauthorized requests to internal network services.

Vulnerability

The application fails to properly validate bid-request parameters before interpolating them into outbound request URLs. This flaw allows an unauthenticated attacker to manipulate the server into making arbitrary HTTP requests to internal metadata endpoints or sensitive network services.

Business impact

This vulnerability carries a CVSS score of 10.0, reflecting its potential for complete system compromise. Successful exploitation could allow an attacker to bypass perimeter security, access internal-only management interfaces, or exfiltrate sensitive environment metadata, leading to significant data breaches and unauthorized control over the server infrastructure.

Remediation

Immediate Action: Upgrade prebid-server-java to version 3.43.0 or later to ensure proper URL validation using HttpUtil.

Proactive Monitoring: Review web access and application logs for unusual outbound request patterns or suspicious parameter inputs targeting internal IP addresses.

Compensating Controls: Deploy a strict egress filtering policy at the network level to restrict the server from accessing internal network segments or unauthorized external domains.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the critical severity and the potential for full unauthorized access to internal resources, organizations should prioritize patching this vulnerability immediately. Upgrading to version 3.43.0 is the only reliable way to remediate the underlying logic flaw that enables these SSRF attacks.

More Prebid CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief critical section

Sources