Skip to main content
Menu
CVEs

Phoenix LiveView authorization bypass skips live_session on_mount hooks

CVE-2026-126334Published , updated

6.0MediumCNA
Exploited
No known exploitation
Fix
Fixed in 1.0.20, 1.1.34, 1.2.14
Who is exposed
Not reported

Summary

An attacker with a low-privilege login can remotely skip the `live_session` `on_mount` hooks on a router-mounted LiveView in phoenix_live_view by sending a join message with neither a "url" nor a "redirect" key. This bypasses the checks those hooks perform, including event checks attached with `attach_hook/4`.

Written by a model

Original description

Incorrect Authorization vulnerability in phoenixframework phoenix_live_view allows an authenticated user to mount a router-mounted LiveView without the on_mount hooks of its live_session via a phx_join message that carries neither a "url" nor a "redirect" key.

The catch-all clause of the private Phoenix.LiveView.Channel.authorize_session/3 in lib/phoenix_live_view/channel.ex accepts a join without a URL for any session, including a root LiveView mounted at the router. The channel then mounts the LiveView with no route, and only a route adds the live_session hooks to the mount lifecycle. Checks that those hooks perform on the connected mount do not run, and event checks that they attach through attach_hook/4 are never attached. The attacker needs a valid session token for the LiveView, which only the HTTP render issues, after the hooks pass there. on_mount hooks declared in the LiveView module still run.

This issue affects phoenix_live_view: from 0.16.0 before 1.0.20, from 1.1.0-rc.0 before 1.1.34, and from 1.2.0-rc.0 before 1.2.14.

What to do

Upgrade to a fixed version: 1.0.20, 1.1.34, 1.2.14.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126334 (Joining a LiveView without `"url"` skips its `live_session` `on_mount` hooks), 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-126334 (entry last updated 2026-11-20):
Affected:
- Hex package phoenix_live_view: from 0.16.0, fixed in 1.0.20; from 1.1.0-rc.0, fixed in 1.1.34; from 1.2.0-rc.0, fixed in 1.2.14
- phoenixframework phoenix_live_view: version range not reported
Fixed versions: 1.0.20, 1.1.34, 1.2.14.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126334 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126334 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Hex): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/phoenixframework/phoenix_live_view/security/advisories/GHSA-v4p7-3pm2-wq6c
- https://github.com/phoenixframework/phoenix_live_view/commit/049b2b10bb051467639c8cf6f3f7ee13df401a74
- https://github.com/phoenixframework/phoenix_live_view/commit/5dc8459da3d5f7f1ba11d2fe351ea97e7a46c99f
- https://github.com/phoenixframework/phoenix_live_view/commit/71b114d75e1ed615bbe8db7474a215536163eabb
- https://github.com/phoenixframework/phoenix_live_view/commit/ec47eaac9e440ca7e8664ef64c8377cd2579c40c
- https://cna.erlef.org/cves/CVE-2026-126334.html
- https://osv.dev/vulnerability/EEF-CVE-2026-126334
- https://github.com/phoenixframework/phoenix_live_view/commit/3d1eb6752399060eebdaa7112f959ee81e7d630d
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-126334
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-126334"}.

Affected versions

cve.now Index

19Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects Hex packages
  • Severity6/10CVSS 6.0
  • No patch0/5No signal

What would change the score

  • Would score about 74 if added to CISA KEV
  • Would score about 69 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Evidence 10

Questions about CVE-2026-126334

Is CVE-2026-126334 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: cve.now feed data

Which versions are affected by CVE-2026-126334?

phoenix_live_view (Hex): from 0.16.0 before 1.0.20; from 1.1.0-rc.0 before 1.1.34; from 1.2.0-rc.0 before 1.2.14.

Source: cve.now feed data

How do I fix CVE-2026-126334?

Upgrade to a fixed version: 1.0.20, 1.1.34, 1.2.14.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.