Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.3amended

ArchiveBox Vulnerable to RCE via unvalidated per-crawl config overrides in AddView

CVE-2026-42601GHSA-3h23-7824-pj8r

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

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.

Add to your agent

Affected packages

  • PyPI archivebox

    Affected
    <= 0.8.6rc0
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-42601: 0.40% estimated exploitation activity in the next 30 days; percentile 34.65 (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.

The /add/ endpoint (AddView in core/views.py) accepts a config JSON field that gets merged into the crawl config without validation. This config is exported as environment variables when archive plugins run, allowing injection of arbitrary tool arguments to achieve RCE. When PUBLICADDVIEW=True (common for bookmarklet usage), this is exploitable without authentication. The endpoint is also @csrfexempt. Affected code: core/views.py:887 - user config extracted with no validation: customconfig = form.cleaneddata.get("config") or {} core/views.py:918 - merged into crawl config: config.update(customconfig) config/configset.py:255-256 - crawl config applied with high priority: if crawl and hasattr(crawl, "config") and crawl.config: config.update(crawl.config) hooks.py:398-411 - config exported as env vars: for key, value in config.items(): if key in SKIPKEYS: continue env[key] = str(value) plugins/ytdlp/onSnapshot02ytdlp.bg.py:122-123 - env var args passed to yt-dlp: ytdlpargsextra =…

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

    Amended from ghsa record GHSA-3h23-7824-pj8r

  2. Revision 3 · amended ·

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

  3. Revision 2 · amended ·

    Amended from osv record GHSA-3h23-7824-pj8r

  4. Revision 1 · created ·

    Published from ghsa record GHSA-3h23-7824-pj8r

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-42601

Advisory: ArchiveBox Vulnerable to RCE via unvalidated per-crawl config overrides in AddView
IDs: CVE-2026-42601, GHSA-3h23-7824-pj8r
Record: https://patchnext.com/advisories/cve-2026-42601 (revision 4, source checked 26 Oct 2026, 13:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI archivebox: affected <= 0.8.6rc0

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on archivebox.
- 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://github.com/advisories/GHSA-3h23-7824-pj8r (GitHub-reviewed advisory GHSA-3h23-7824-pj8r lists affected ranges: PyPI archivebox >=0 <=0.8.6rc0)
- Verified: https://osv.dev/vulnerability/GHSA-3h23-7824-pj8r (OSV record GHSA-3h23-7824-pj8r lists affected ranges: PyPI archivebox >=0 <=0.8.6rc0)

Commands are suggestions: review each one before running it.

Loading voting…