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

Back
New CVE Detected

CVE-2026-86119 – Unauthenticated SSRF – Webstudio (self-hosted) through 0.296.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-86119 is an unauthenticated server-side request forgery (SSRF) vulnerability in Webstudio, an open-source website builder, affecting all versions through 0.296.0. The flaw resides in the /cgi/image, /cgi/video, and /cgi/asset proxy routes, which fetch arbitrary attacker-supplied URLs server-side when the RESIZE_ORIGIN environment variable is not configured. The issue is rated CRITICAL, allowing unauthenticated attackers to pivot the affected server into internal networks and cloud metadata services.

Technical details

  • Root cause: the /cgi/image, /cgi/video, and /cgi/asset proxy routes (implemented in cgi.image.$.ts, cgi.video.$.ts, and cgi.asset.$.ts) contain an absolute-URL fetch branch that will retrieve any URL supplied by the requester.
  • Trigger condition: the vulnerability is exploitable only when the RESIZE_ORIGIN environment variable is left unset on the deployment, removing the intended restriction on which origins the proxy is allowed to fetch from.
  • Attack vector: network, unauthenticated, no user interaction required — an attacker simply submits a crafted absolute URL as a parameter to one of the vulnerable proxy routes.
  • Impact: server-side requests can be forced to internal-only services and cloud instance metadata endpoints (e.g., 169.254.169.254), enabling credential theft, internal network reconnaissance, and further lateral movement.

Affected software

  • Webstudio (webstudio-is/webstudio) — all versions through 0.296.0, when the RESIZE_ORIGIN environment variable is unset.

Severity

  • CVSS v4.0: 9.2 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
  • CVSS v3.1: 8.6 (High) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

Mitigation and recommended actions

  • Immediate: no fixed release version is documented in the public CVE record at time of publication; administrators should track the upstream Webstudio repository for a patched release addressing GitHub issue #5816.
  • Workaround: explicitly configure the RESIZE_ORIGIN environment variable on all Webstudio deployments to restrict the proxy routes to trusted origins only.
  • Network mitigations: block or restrict outbound access from the Webstudio host to cloud metadata endpoints and internal-only network ranges; monitor logs on the /cgi/image, /cgi/video, and /cgi/asset routes for requests containing absolute URLs, loopback, link-local, or private-IP destinations.

How IONIX identifies potentially affected assets

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

  • Page title: Webstudio login
  • Raw response body: a canonical link tag with href https://apps.webstudio.is/login/, and a description meta tag with content Log in to Webstudio to start creating websites.

References

Are you exposed?

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge