Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-85612 – Unauthenticated SSRF – OpenPanel before 2.3.0

Be the first to know when new zero-days emerge:

Summary

CVE-2026-85612 is an unauthenticated Server-Side Request Forgery (SSRF) vulnerability in OpenPanel, an open-source analytics platform. The flaw resides in the /misc/favicon and /misc/og endpoints, which accept an attacker-supplied URL parameter and fetch it server-side with insufficient validation. It carries a HIGH severity rating and requires no authentication or user interaction to exploit remotely.

Technical details

  • Root cause: the /misc/favicon and /misc/og endpoints accept a client-controlled URL parameter and issue an outbound HTTP request to it without adequate validation or blocklisting.
  • Trigger condition: an unauthenticated attacker submits a request to either endpoint with a URL pointing at an internal host or a cloud instance metadata endpoint.
  • Attack vector: network, no privileges or user interaction required (CWE-918, Server-Side Request Forgery).
  • Impact: the server-side response is returned verbatim to the attacker, enabling disclosure of internal service data, cloud metadata (e.g., instance credentials), and enumeration of internal network hosts/services.

Affected software

  • OpenPanel (Openpanel-dev) — all releases prior to version 2.3.0

Severity

  • CVSS v4.0 Base Score: 8.7 (HIGH) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
  • CVSS v3.1 Base Score: 7.5 (HIGH) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: upgrade OpenPanel to version 2.3.0 or later, which addresses this SSRF issue.
  • If patching is not immediately possible: restrict or disable outbound network access from the OpenPanel host to internal/private IP ranges and cloud metadata addresses (e.g., 169.254.169.254), and place a network-level egress filter or proxy in front of the /misc/favicon and /misc/og endpoints until the upgrade can be applied.

How IONIX identifies potentially affected assets

IONIX matches the following signal against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Raw response body: "Successfully running OpenPanel.dev API"

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge