# CVE-2025-14812: Address bar spoofing risk in Arc Search on iOS

> Attackers can spoof the address bar in Arc Search for iOS via iframe navigation, misleading users about the current site.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2025
- **Updated:** 19 Dec 2025
- **Also known as:** GHSA-xjv2-8h6h-m75g

## What is CVE-2025-14812?

CVE-2025-14812 is a high-severity vulnerability in The Browser Company of New York ArcSearch, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ArcSearch for iOS versions prior to 1.45.2 could display a different domain in the address bar than the content being shown after an iframe-triggered URI-scheme navigation, increasing spoofing risk.

Weakness: CWE-1021 (Improper Restriction of Rendered UI Layers or Frames)

## Which versions are affected by CVE-2025-14812?


## How do I fix CVE-2025-14812?

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

## Is CVE-2025-14812 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-14812 and fix it if it is affected.

What it is: CVE-2025-14812 is a high-severity vulnerability in The Browser Company of New York ArcSearch, published on 19 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14812 in the wild and no public exploit code.

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

## Sources

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

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