# CVE-2026-73210: Server-Side Request Forgery via Favicon Retrieval in Lookyloo PlaywrightCapture

> Attacker-controlled pages can bypass network restrictions to access internal services via crafted favicon URLs in Lookyloo PlaywrightCapture.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 12 Aug 2026

## What is CVE-2026-73210?

CVE-2026-73210 is a medium-severity server-side request forgery vulnerability in Lookyloo PlaywrightCapture, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Server-Side Request Forgery (SSRF) vulnerability existed in Lookyloo's PlaywrightCapture when the only_global_lookup option was enabled.

PlaywrightCapture implements this option to prevent captures from accessing local, loopback, or otherwise non-public network resources. However, favicon retrieval was performed separately from the browser request-routing protections. Favicon URLs extracted from rendered HTML were resolved and subsequently fetched directly using an aiohttp.ClientSession.

An attacker able to supply or control a web page processed by PlaywrightCapture could include a crafted favicon reference, for example pointing to a loopback address, private IP address, or another resource reachable only from the PlaywrightCapture host. When the page was processed, the favicon retrieval routine could issue an HTTP request to this destination despite only_global_lookup being enabled.

This bypass could therefore be used to make the PlaywrightCapture host interact with internal network services that should not be reachable through a capture. Depending on the targeted service and its response, this could enable internal service discovery, access to internal resources, or interaction with HTTP endpoints available only from the capture infrastructure.

The patch introduces a common URL validation routine and applies it to favicon retrieval. Direct non-global IP addresses, localhost, .local domains, malformed URLs, and other explicitly non-public destinations are rejected before the favicon request is performed.

This fix is a complementary fix to CVE-2026-44439 - GCVE-0-2026-44439 - GHSA-687H-XW6F-Q2QW

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-73210?


## How do I fix CVE-2026-73210?

No fix has been published for CVE-2026-73210 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-73210 being exploited?

There is no known exploitation of CVE-2026-73210 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-73210 and fix it if it is affected.

What it is: CVE-2026-73210 is a medium-severity server-side request forgery vulnerability in Lookyloo PlaywrightCapture, published on 11 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-73210 in the wild and no public exploit code.

Affected product: Lookyloo PlaywrightCapture. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-73210/ (Markdown: https://insights.sbomify.com/CVE-2026-73210/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-73210
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-73210
- OSV: https://osv.dev/vulnerability/CVE-2026-73210

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-73210/
Summaries are generated and may contain mistakes; the official description above is the record.