CVE-2026-4800 - Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for th

CVE-2026-4800 + Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for th + High + 2026-03-31

One-sentence business risk

The vulnerable component sits in a commonly deployed application path and can create a material breach, outage, or compliance risk.

Research notes

  • Root cause: Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for the variable option in _.template but did not apply the same validation to options.imports key names.
  • Affected versions: Affected versions named by the upstream advisory and dependency metadata.
  • Fixed / safe versions: upgrade to version 4.18.0…
  • Public exploit / PoC signal: the consulted NVD/GHSA/vendor sources describe the trigger class; treat it as reproducible until patched.
  • CVSS: 8.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.

Exact vulnerable code pattern

setPath(target, key.split("."), value)  # no segment denylist

Fixed / mitigated code pattern

reject segments in {"__proto__", "constructor", "prototype"} before walking the object

Dependency or runtime update:

rg -n "affected component|CVE-2026-4800" .
# update affected runtime/product to upgrade to version 4.18.0.

Step-by-step integration guide

  1. Inventory affected component across source, lockfiles, SBOMs, container images, CI images, and deployment manifests.
  2. Upgrade to upgrade to version 4.18.0. or apply the exact vendor patch referenced below.
  3. Replace the vulnerable prototype-pollution pattern with the fixed pattern and fail closed on malformed input.
  4. Add a regression test that exercises the advisory trigger and proves the request is rejected, bounded, or authorized.
  5. Deploy through canary, monitor security logs and resource metrics, then remove temporary edge blocks only after all runtimes are fixed.

Alternative mitigations

  • Disable the vulnerable feature path while the package/runtime update rolls out.
  • Add WAF or reverse-proxy rules for traversal tokens, prototype-polluting keys, oversized frames, shell metacharacters, or unauthenticated tool calls matching the trigger class.
  • Restrict internal egress, rotate exposed secrets, and revoke affected tokens/keys if the vulnerability can disclose config, logs, JWT secrets, proxy credentials, or PKI material.
  • For admin/API authorization issues, temporarily require elevated roles and explicit ownership checks at the gateway.

Detection signature

id: cve-2026-4800-impact-the-fix-for-cve-2021-23337-https-github-c
source: NVD
dependency_or_product: "affected component"
affected: "Affected versions named by the upstream advisory and dependency metadata"
fixed: "upgrade to version 4.18.0."
signals:
  - "prototype-pollution"
  - "../"
  - "__proto__"
  - "tools/call"
  - "wp_ajax_nopriv"
  - "pickle.loads"
  - "shell command construction"
action: "upgrade, add regression test, and verify deploy artifact"

Copy-paste skill

You are remediating CVE-2026-4800 (Impact: The fix for CVE-2021-23337 (https://github.com/advisories/GHSA-35jh-r3h4-6jhm) added validation for th) in this repository.

Find every affected dependency, runtime, image, service configuration, and reachable code path. Upgrade or patch to upgrade to version 4.18.0.. Replace the vulnerable prototype-pollution pattern with a fail-closed implementation, add a regression test for the trigger shape, and update deployment/SBOM artifacts. If this repository does not control the affected runtime, create TRIAGE.md naming the owner, affected version, fixed version, and blocking decision.

Keywords, affected tech stack, and revenue tags

  • Keywords: CVE-2026-4800, prototype-pollution, affected component, NVD.
  • Affected tech stack: general.
  • Revenue tags: sellable_to_fintech, enterprise_blocker, high_priority_sla.

References