/

CVE-2026-85612

Severity:

HIGH RISK

(7.5)

SSRF (CWE-918) in OpenPanel Favicon and OG Endpoints

CVE-2026-85612

Deferred

Vulnerability type

Category:

Server-Side Request Forgery

CWE:

CWE-918

Impact:

Internal Service Access and Credential Disclosure

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

OpenPanel contains an unauthenticated server-side request forgery vulnerability in the /misc/favicon and /misc/og endpoints, where attacker-controlled URLs are fetched with insufficient validation. An attacker may use these endpoints to reach internal services or cloud metadata endpoints, and small responses returned by the API could expose credentials or service information.

Affected context

The vulnerability occurs in OpenPanel deployments where the /misc/favicon or /misc/og endpoints accept a user-supplied url parameter and perform outbound server-side requests. Risk is greater when the hosting environment can reach private network services, cloud metadata endpoints, or other sensitive administrative interfaces, and when fetched response content is returned to the requester.

Exploit preconditions

  • Attack surface: Unauthenticated HTTP access to the affected OpenPanel endpoints
  • Required access: Ability to submit an attacker-controlled url parameter
  • Trigger point: Server-side retrieval of the requested favicon or Open Graph resource
  • Why exploitation is possible: URL validation does not sufficiently restrict internal destinations, allowing the server to act as a network proxy and return limited response content

Why this happens

The underlying issue is insufficient validation and authorization of server-side outbound requests. The application accepts externally controlled destination data without reliably enforcing an allowlist, blocking private or link-local address ranges, handling redirects safely, and validating resolved network destinations. This behavior maps to CWE-918: Server-Side Request Forgery, where an attacker influences a server to connect to unintended internal or protected resources.

Potential impact

  • An attacker may enumerate internal services and network topology
  • Cloud instance metadata or temporary credentials could be disclosed
  • Internal administrative endpoints could be queried
  • Sensitive response data could be exposed through the affected API
  • Compromised credentials could enable further access within the environment

General mitigation guidance

Mitigation generally focuses on reducing trust in user-controlled URLs and limiting the destinations reachable by server-side request functionality.

Common defensive patterns include:

  • Restricting requests to an explicit allowlist of permitted schemes, hosts, and ports
  • Blocking loopback, private, link-local, multicast, and cloud metadata address ranges
  • Revalidating destinations after DNS resolution and across redirects
  • Returning only the minimum required resource data rather than upstream response content
  • Applying strict connection, response-size, and timeout limits
  • Running the service with network segmentation and least-privilege identity permissions
  • Using cloud controls that restrict application access to instance metadata services

How teams detect issues like this

Organizations can identify SSRF risks through:

  • Static analysis rules for outbound HTTP clients that consume request parameters
  • Code review checks for URL allowlisting, redirect handling, DNS rebinding defenses, and private-address filtering
  • Dynamic testing that verifies blocked access to loopback, private, link-local, and metadata destinations
  • Egress network policies that alert on unexpected connections from application workloads
  • Monitoring for unusual requests to internal address ranges or metadata service IPs
  • Automated security review tools that flag user-controlled URL fetch operations

Sources

SourceLink
github.comgithub.com/Openpanel-dev/openpanel/security/advisories/GHSA-2hff-m67f-2w2w
vulncheck.comvulncheck.com/advisories/openpanel-before-2.3.0-ssrf-via-favicon-and-og-endpoints

Frequently asked

questions

Yes. The affected endpoints are reachable without authentication, so an attacker may submit crafted URL parameters over the network when the endpoints are exposed.

The attacker generally needs only network access to the OpenPanel API. They do not need valid application credentials if unauthenticated access to the endpoints remains available.

Restrict server-side fetching to an explicit allowlist, block internal and metadata destinations, validate resolved addresses and redirects, and minimize returned response content.

Treat all user-provided URLs as untrusted, enforce outbound network policy at both the application and infrastructure layers, and continuously test SSRF defenses against private, link-local, and cloud metadata targets.

Find out what's already
exploitable in your codebase.