# CVE-2026-12703: Bypass of 2FA for Connections via Unattended Access in TeamViewer for macOS

> An authenticated attacker can bypass 2FA to establish remote connections on TeamViewer for macOS hosts.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jul 2026
- **Updated:** 29 Jul 2026
- **Also known as:** GHSA-r926-cxpx-jff4

## What is CVE-2026-12703?

CVE-2026-12703 is a high-severity authentication bypass vulnerability in TeamViewer ONE, published on 29 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

TeamViewer Full Client and Host for macOS before version 15.80 contain a business logic error that can allow an authenticated attacker to bypass a configured 2FA for Connections approval flow via Unattended Access and establish a remote connection to an affected macOS host.

Weakness: CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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


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

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

## Is CVE-2026-12703 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-12703 is a high-severity authentication bypass vulnerability in TeamViewer ONE, published on 29 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-12703 in the wild and no public exploit code.

Affected product: TeamViewer ONE. 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-12703/ (Markdown: https://insights.sbomify.com/CVE-2026-12703/index.md)
```

## Sources

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

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