# CVE-2026-94181: Address Bar Spoof Risk; Missing Fullscreen Notification via Select Element

> Attackers can spoof the browser address bar using a select element to hide fullscreen notifications, misleading users about the current site.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/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:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-g53h-c489-2f5m

## What is CVE-2026-94181?

CVE-2026-94181 is a high-severity vulnerability in The Browser Company of New York Arc, published on 23 Sep 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

An address bar spoofing issue in affected versions of Arc could allow an attacker to spoof the browser address bar via a <select> element that triggers requestFullscreen without displaying the fullscreen notification.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information)

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


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

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

## Is CVE-2026-94181 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94181 is a high-severity vulnerability in The Browser Company of New York Arc, published on 23 Sep 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-94181 in the wild and no public exploit code.

Affected product: The Browser Company of New York Arc. 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-94181/ (Markdown: https://insights.sbomify.com/CVE-2026-94181/index.md)
```

## Sources

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

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