Skip to main content
Menu
CVEs

Skyvern server-side request forgery in browser egress policy

CVE-2026-134533Published November 21, 2026, updated

5.1MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Specific setups only

Summary

Skyvern-AI Skyvern contains a server-side request forgery flaw in the classify_url function of its browser egress policy code. A remote attacker with low-privilege access, who must get a user to take an action, can use it to make the server send requests to destinations it should not reach.

Written by a model

Original description

A vulnerability was identified in Skyvern-AI Skyvern 1.0.56. Impacted is the function classify_url of the file skyvern/forge/sdk/browser_egress_policy.py. The manipulation leads to server-side request forgery. The attack is possible to be carried out remotely. Upgrading to version 1.0.57 is recommended to address this issue. The identifier of the patch is 10b8d829c2750ebf62f2b70dec0e288297e752dd. Upgrading the affected component is recommended.

Who should check

Teams running Skyvern-AI Skyvern 1.0.56 self-hosted with a remote browser (BROWSER_REMOTE_DEBUGGING_URL) on a network separate from the worker.

“Affected: Skyvern-AI/skyvern at commit 623eb57 ( v1.0.56 )”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    The browser runs on a different network from the worker, so the two resolvers can disagree (split-horizon DNS).
  2. Apply the patch listed under Evidence.

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-134533 (Skyvern-AI Skyvern browser_egress_policy.py classify_url server-side request forgery), 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-134533 (entry last updated 2026-11-21):
Affected:
- Skyvern-AI Skyvern: versions 1.0.56
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- The browser runs on a different network from the worker, so the two resolvers can disagree (split-horizon DNS). (source: https://github.com/Skyvern-AI/skyvern/issues/9010)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-134533 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-134533 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://github.com/Skyvern-AI/skyvern/pull/9013
- https://github.com/Skyvern-AI/skyvern/commit/10b8d829c2750ebf62f2b70dec0e288297e752dd
- https://github.com/Skyvern-AI/skyvern/releases/tag/v1.0.57
- https://github.com/Skyvern-AI/skyvern/issues/9010
- https://vuldb.com/vuln/441678
- https://vuldb.com/vuln/441678/cti
- https://vuldb.com/cve/CVE-2026-134533
- https://github.com/Skyvern-AI/skyvern/
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-134533
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-134533"}.

Affected versions

cve.now Index

13Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure8/25Specific setups only, reachable over the network
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.1/10CVSS 5.1
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 20 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 10

Questions about CVE-2026-134533

Is CVE-2026-134533 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

What does this mean?

The URL check in Skyvern's browser egress policy can be bypassed through DNS, so the agent can be steered to internal HTTP(S) services it should not reach. The agent can read the rendered response, so internal content may be read and sent out through the run's outbound channels.

Source: github.com

Which versions are affected by CVE-2026-134533?

Skyvern: version 1.0.56.

Source: cve.now feed data

Am I affected, and how do I check?

The issue applies to Skyvern setups where the browser runs on a different network from the worker, so the two DNS resolvers can disagree (split-horizon DNS). To check a setup, confirm whether the browser and worker run on separate networks and whether they use different DNS resolvers.

Source: github.com

How do I fix CVE-2026-134533?

No fixed version or vendor patch is listed in the checked facts, so no upgrade target can be given yet. Check the vendor's advisory for updates.

Source: github.com

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