CVE-2026-67544

Browser automation nodes could execute code on the workflow host

Heym · Heym browser workflow nodes

First documented disclosure · Review checkpoint

Summary

Custom browser-node code ran with backend privileges and without an isolation boundary. Code could run with the service account's permissions.

Severity and exploitation evidence

High · 8.8/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed advisory does not report malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Custom browser-node code ran with backend privileges and without an isolation boundary.

Conditions required

An authenticated user could submit and run a workflow using the affected node.

Potential impact

Code could run with the service account's permissions.

Affected versions and configurations

Before 0.0.71. The maintainer lists the boundary version in both its affected and patched fields. The CNA excludes the patched build.

Fix and mitigation status

0.0.71.

Practical next steps

Upgrade and restrict who may run custom browser automation.

Operating lesson

Apply authorization and isolation to every backend path that can act on behalf of an agent.

Evidence and limits

The public disclosure was on 2026-07-18. The CVE record was published on 2026-11-11.

Sources