Is CVE-2026-50870 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-50870 being exploited in the wild.

How severe is CVE-2026-50870?

Informational severity, published 15 June 2026.

Which products and versions are affected?

Ben Busby Whoogle Search 1.2.3.

Is there a fix for CVE-2026-50870?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-50870 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-50870?

Check whether you run Ben Busby Whoogle Search at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-50870: Ben Busby whoogle-search information disclosure in configuration endpoint

CVE-2026-50870 · Severity: info · Published 2026-06-15

Whoogle Search is a privacy-focused search engine that acts as a proxy for Google results. A security flaw in version 1.2.3 allows any visitor to view the server's private Google API keys and search engine identifiers. An attacker could steal these credentials to use the owner's paid search quota or perform unauthorized searches using the owner's identity.

Technologies: Ben Busby Whoogle Search. Vendors: Ben Busby.

Quick answers

Is CVE-2026-50870 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-50870 being exploited in the wild.
How severe is CVE-2026-50870?: Informational severity, published 15 June 2026.
Which products and versions are affected?: Ben Busby Whoogle Search 1.2.3.
Is there a fix for CVE-2026-50870?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-50870 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-50870?: Check whether you run Ben Busby Whoogle Search at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An information disclosure vulnerability exists in the /config endpoint of Whoogle Search v1.2.3. The application fails to filter sensitive fields when returning the user configuration dictionary (g.user_config.__dict__) via a GET request. Specifically, the 'cse_api_key' and 'cse_id' fields are exposed to unauthenticated remote users. Additionally, these credentials may be rendered into client-visible state within index and header templates or encoded within preference values used by the root and search routes. Even if WHOOGLE_CONFIG_DISABLE is enabled, the fields remain visible in the GET response, allowing attackers to exfiltrate server-side API credentials.

Affected products

Ben Busby whoogle-search 1.2.3

Timeline

2026-06-13: other: Vulnerability details shared via GitHub Gist
2026-06-15: disclosed: CVE published to NVD

References

https://gist.github.com/pyuysig/b15055668de5fa09d08448ce830bba10

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.