# CVE-2026-52842: Lightpanda:URL parser misidentifies page origin for URLs containing @ in the path - Same-Origin Policy bypass

> Lightpanda's URL parser incorrectly handles '@' in paths, allowing attackers to bypass Same-Origin Policy restrictions.

- **Severity:** Critical 9.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A: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:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-mq6p-m9cc-q432

## What is CVE-2026-52842?

CVE-2026-52842 is a critical vulnerability in lightpanda-io browser, published on 15 Jul 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

Lightpanda is a headless browser designed for AI and automation. Prior to 0.3.1, Lightpanda searched for @ across the entire URL string instead of only the authority component when computing a page origin, so a URL such as `http://attacker.com/@victim.com/` was fetched from attacker.com but treated as `http://victim.com`, allowing a complete Same-Origin Policy bypass. This issue is fixed in version 0.3.1.

Weakness: CWE-346 (Origin Validation Error)

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


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

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

## Is CVE-2026-52842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-52842 is a critical vulnerability in lightpanda-io browser, published on 15 Jul 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-52842 in the wild and no public exploit code.

Affected product: lightpanda-io browser. 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-52842/ (Markdown: https://insights.sbomify.com/CVE-2026-52842/index.md)
```

## Sources

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

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