Skip to content

← Actionable
Medium, CVSS 6.6amended

Playwright Capture permits access to local files and internal network resources during page capture

CVE-2026-44439GHSA-687h-xw6f-q2qw

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (playwrightcapture 1.39.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.6 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:U · score source
EPSS
  • CVE-2026-44439: 0.40% estimated exploitation activity in the next 30 days; percentile 33.89 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Playwright Capture did not sufficiently restrict navigations and resource requests initiated by rendered pages. An attacker-controlled page could abuse browser-side redirection mechanisms, such as window.location.href, to make the capture process open file:// URLs or request resources hosted on private, loopback, link-local, or otherwise non-public IP addresses. In deployments where PlaywrightCapture processes untrusted URLs, this could allow a remote attacker to perform server-side request forgery against internal services or attempt to access local files from the capture environment. Depending on what capture artifacts are generated and exposed, responses from those resources could potentially be leaked through screenshots, saved page content, logs, or other capture outputs. The patch mitigates the issue by introducing request routing checks that block secondary requests to local files, non-global IP addresses, and .local domains when onlygloballookup is enabled, while still…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-687h-xw6f-q2qw

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-687h-xw6f-q2qw

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44439

Advisory: Playwright Capture permits access to local files and internal network resources during page capture
IDs: CVE-2026-44439, GHSA-687h-xw6f-q2qw
Record: https://patchnext.com/advisories/cve-2026-44439 (revision 3, source checked 26 Oct 2026, 13:45 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: playwrightcapture 1.39.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI playwrightcapture: affected < 1.39.6; fixed in 1.39.6

## Suggested inspection (read-only)
- `python -m pip show playwrightcapture`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on playwrightcapture.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-687h-xw6f-q2qw (OSV record GHSA-687h-xw6f-q2qw lists affected ranges: PyPI playwrightcapture >=0 <1.39.6 (fixed))
- Verified: https://github.com/advisories/GHSA-687h-xw6f-q2qw (GitHub-reviewed advisory GHSA-687h-xw6f-q2qw lists affected ranges: PyPI playwrightcapture >=0 <1.39.6)

Commands are suggestions: review each one before running it.

Loading voting…