CVE-2026-42601

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-04. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

ArchiveBox is an open source self-hosted web archiving system. In versions 0.8.6rc0 and prior, 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. At time of publication, there are no publicly available patches.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Attend)
EG Risk 75/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS
33.0%
KEV
Not listed

Published

May 9, 2026

Last Modified

May 14, 2026

Advisory Details (1)

Auto-updated Jun 21, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Anonymous users can set potentially dangerous config values via /add/ when PUBLIC_ADD_VIEW=True on <=0.8.6rc0 · Advisory · ArchiveBox/ArchiveBox · GitHub

https://github.com/ArchiveBox/ArchiveBox/security/advisories/GHSA-3h23-7824-pj8r

Vendor Advisories for CVE-2026-42601(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
piparchivebox—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
archivebox0.4.11 ... 0.8.5rc9 (76 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 41× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 184 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:11 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-16 09:53 UTCOSV refresh
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 15:15 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 16:27 UTCEPSS rescore
  22. 2026-07-06 02:23 UTCEPSS rescore
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-05 02:30 UTCEPSS rescore
  25. 2026-07-04 06:31 UTCEPSS rescore
Show 75 more
  1. 2026-07-01 15:06 UTCEPSS rescore
  2. 2026-06-30 23:22 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 08:54 UTCGHSA enrichment
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 03:38 UTCGHSA enrichment
  8. 2026-06-27 14:21 UTCGHSA enrichment
  9. 2026-06-27 10:29 UTCGHSA enrichment
  10. 2026-06-27 03:08 UTCEPSS rescore
  11. 2026-06-26 21:10 UTCGHSA enrichment
  12. 2026-06-26 05:45 UTCGHSA enrichment
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-24 14:05 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-22 14:25 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-21 14:56 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 01:59 UTCEPSS rescore
  22. 2026-06-19 19:25 UTCEPSS rescore
  23. 2026-06-18 17:52 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-17 17:53 UTCEPSS rescore
  26. 2026-06-17 05:39 UTCGHSA enrichment
  27. 2026-06-17 01:12 UTCGHSA enrichment
  28. 2026-06-16 17:52 UTCEPSS rescore
  29. 2026-06-16 07:49 UTCGHSA enrichment
  30. 2026-06-15 17:49 UTCEPSS rescore
  31. 2026-06-15 06:06 UTCGHSA enrichment
  32. 2026-06-15 02:14 UTCGHSA enrichment
  33. 2026-06-14 22:22 UTCGHSA enrichment
  34. 2026-06-14 18:30 UTCGHSA enrichment
  35. 2026-06-14 14:39 UTCGHSA enrichment
  36. 2026-06-14 10:36 UTCGHSA enrichment
  37. 2026-06-14 06:43 UTCGHSA enrichment
  38. 2026-06-14 02:21 UTCGHSA enrichment
  39. 2026-06-13 23:00 UTCEPSS rescore
  40. 2026-06-13 09:10 UTCGHSA enrichment
  41. 2026-06-12 23:12 UTCEPSS rescore
  42. 2026-06-12 23:12 UTCEPSS rescore
  43. 2026-06-12 22:43 UTCGHSA enrichment
  44. 2026-06-12 18:32 UTCGHSA enrichment
  45. 2026-06-12 14:15 UTCGHSA enrichment
  46. 2026-06-12 09:49 UTCGHSA enrichment
  47. 2026-06-12 05:58 UTCGHSA enrichment
  48. 2026-06-12 02:06 UTCGHSA enrichment
  49. 2026-06-11 22:15 UTCGHSA enrichment
  50. 2026-06-11 18:23 UTCGHSA enrichment
  51. 2026-06-11 14:15 UTCGHSA enrichment
  52. 2026-06-11 14:00 UTCEPSS rescore
  53. 2026-06-11 10:22 UTCGHSA enrichment
  54. 2026-06-11 06:30 UTCGHSA enrichment
  55. 2026-06-11 02:38 UTCGHSA enrichment
  56. 2026-06-10 22:46 UTCGHSA enrichment
  57. 2026-06-10 22:18 UTCEPSS rescore
  58. 2026-06-10 18:55 UTCGHSA enrichment
  59. 2026-06-10 15:03 UTCGHSA enrichment
  60. 2026-06-10 13:22 UTCEPSS rescore
  61. 2026-06-10 13:22 UTCEPSS rescore
  62. 2026-06-10 11:12 UTCGHSA enrichment
  63. 2026-06-10 07:20 UTCGHSA enrichment
  64. 2026-06-10 03:27 UTCGHSA enrichment
  65. 2026-06-09 23:34 UTCGHSA enrichment
  66. 2026-06-09 19:43 UTCGHSA enrichment
  67. 2026-06-09 15:51 UTCGHSA enrichment
  68. 2026-06-09 11:59 UTCGHSA enrichment
  69. 2026-06-09 08:08 UTCGHSA enrichment
  70. 2026-06-09 04:16 UTCGHSA enrichment
  71. 2026-06-09 00:24 UTCGHSA enrichment
  72. 2026-06-08 20:32 UTCGHSA enrichment
  73. 2026-06-08 14:17 UTCEPSS rescore
  74. 2026-06-08 14:17 UTCEPSS rescore
  75. 2026-06-08 13:33 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-42601?
CVE-2026-42601 is a critical vulnerability published on May 9, 2026. ArchiveBox is an open source self-hosted web archiving system. In versions 0.8.6rc0 and prior, 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…
When was CVE-2026-42601 disclosed?
CVE-2026-42601 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42601 actively exploited?
CVE-2026-42601 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-42601?
CVE-2026-42601 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-42601?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42601, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-42601

Explore →

Is Your Infrastructure Affected by CVE-2026-42601?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs