Loading story…
Prebid Server patched a critical server-side request forgery (SSRF) flaw, tracked as CVE-2026-54735 and later referenced as GHSA-4p3g-4hcj-wpvx, affecting bidder adapters that built outbound bid request URLs from untrusted values in imp[].ext.<bidder>. The issue stemmed from unsafe use of bidder-supplied fields such as host, subdomain, account, zone, endpoint, and pbsHost, allowing attackers to inject characters like /, ?, #, or @ and alter the destination host or path of generated requests. The vulnerability was rated CVSS 3.1 AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H, indicating potentially severe impact to confidentiality, integrity, and availability.
The fix was merged through pull request #4802 and shipped in Prebid Server v4.4.0, adding urlutil.IsSafeHost validation and stricter checks across multiple adapters before endpoint URL construction. Unsafe inputs now trigger BadInput errors such as "Invalid Host" or "Invalid account", and new tests and fixtures verify rejection of malformed values containing schemes, paths, queries, fragments, userinfo, or invalid ports. Release notes said the hardening may affect unusual host configurations because certain hostname characters are now blocked, but the change is intended to prevent hostname forgery and SSRF through dynamic bidder parameters.
See affected versions and whether adversaries are exploiting it.
5 events from the most recent confirmed update back to the earliest known activity.
A CVE report disclosed CVE-2026-54735, describing an SSRF vulnerability in Prebid Server bidder adapters caused by unsafe handling of dynamic bidder-specific parameters in OpenRTB imp[].ext.<bidder>. The report documented how unvalidated values such as host, account, zone, endpoint, or pbsHost could alter outbound request destinations and included mitigation details.
Prebid Server released version 4.4.0 including the security update from PR #4802 to validate dynamic bidder hostnames and reduce hostname forgery risk. The release notes warned that some unusual host configurations might be affected because certain hostname characters are now blocked.
Prebid merged changes that added safe host and subdomain validation across multiple bidder adapters, rejecting unsafe bidder-supplied values before endpoint URL construction. The commit introduced urlutil.IsSafeHost checks, BadInput errors, and tests covering malicious-looking inputs.
A pull request was opened in the prebid/prebid-server repository to address SSRF-related URL injection in bidder parameters, later retitled to focus on validating bidder-supplied host and subdomain values.
The pull request timeline notes that GoVulnBot later referenced the Prebid Server issue on July 29, 2026 as a potential Go vulnerability with advisory identifier GHSA-4p3g-4hcj-wpvx.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
4 references tracked. Mallory keeps watching after this page renders.
cvereports.com
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Multiple vulnerabilities in **PraisonAI** and **praisonaiagents** exposed deployments to unauthorized access and server-side request forgery. **CVE-2026-55528** stems from `AgentServer` declaring an `auth_token` but not enforcing it on any route, allowing remote unauthenticated users to subscribe, publish, and invoke other actions even when authentication was configured. The issue affects PraisonAI versions earlier than **4.6.58** and praisonaiagents versions earlier than **1.6.58**, and was rated high severity with impact to integrity. Two SSRF flaws also affected the platform’s network-facing features. **CVE-2026-55526** allowed crafted hostnames such as `127.0.0.1.nip.io` to bypass hostname blocking because `spider_tools._host_is_blocked()` did not resolve hostnames before requests were made, enabling access to loopback and other internal resources. Separately, **CVE-2026-55537** exposed webhook handling to a DNS race and fail-open validation bug: an authenticated attacker with job submission rights and control of authoritative DNS could register a webhook that initially failed resolution, then repoint it before delivery so the background executor sent `HTTP POST` requests to internal targets including `127.0.0.1` and `169.254.169.254`. A hardening commit added authentication enforcement, DNS-based SSRF checks, and broader fail-closed validation, while fixes were released in updated PraisonAI and praisonaiagents versions.
Aug 25, 2026
Budibase disclosed two high-severity vulnerabilities affecting its low-code platform, including an unrestricted server-side request forgery tracked as `CVE-2026-33226` and a stored cross-site scripting flaw tracked as `CVE-2026-35218`. The SSRF issue affects version `3.30.6` and earlier in the REST datasource query preview endpoint, `POST /api/queries/preview`, where an authenticated admin can supply an arbitrary URL in `fields.path` and force the server to make unvalidated HTTP requests. That behavior can expose internal-only resources such as cloud metadata endpoints, internal databases, Kubernetes APIs, and other internal network services, with reported risk of OAuth2 token theft and potentially full Google Cloud access in some GCP deployments. The second flaw affects versions prior to `3.32.5` and stems from unsanitized entity names rendered with Svelte's `{@html}` directive in the Builder Command Palette. An authenticated user with Builder access can inject malicious HTML into names for tables, views, queries, or automations, and the payload executes when another Builder-role user opens the palette with `Ctrl+K`, enabling session cookie theft and possible full account takeover. Budibase patched the stored XSS issue in version `3.32.5`, while no public patch was available for the SSRF issue at the time of publication.
Jun 29, 2026
OpenSIPS disclosed **CVE-2026-46334**, a remotely triggerable denial-of-service flaw in SDP bandwidth-line parsing that affects versions prior to **3.6.6** and **4.0.0-rc1**. A malformed session-level `b=` SDP line missing the required `:` delimiter can corrupt parsed bandwidth metadata, and if that corrupted SDP state is later cloned during dialog handling or QoS processing, an OpenSIPS worker process can crash. The issue is exploitable by an unauthenticated attacker in deployments that parse attacker-controlled SDP and use affected routing or module logic. The fix was introduced through OpenSIPS commits that harden `parser/sdp/sdp_helpr_funcs.c` by rejecting malformed bandwidth lines, adding boundary checks, and preventing unsafe access when `b=` appears at the start of the buffer or lacks a separator. The patched code logs an error and returns failure for invalid SDP bandwidth encoding, closing the crash path in both the **3.6** and **4.0.0** code lines. The vulnerability is mapped to **CWE-20** and **CWE-476** and carries high availability impact.
Aug 5, 2026