Security Digest: October 22, 2026 - 24 Critical Vulnerabilities

Today’s advisory load is heavy: 24 critical and high-severity flaws across widely used developer tools, web frameworks, image processors, and supply-chain components. The most urgent risks are remote code execution, prototype pollution, and multiple denial-of-service issues that can take down shared services or expose internal execution paths.

· 16 min read

Executive Summary

Today’s advisory load is heavy: 24 critical and high-severity flaws across widely used developer tools, web frameworks, image processors, and supply-chain components. The most urgent risks are remote code execution, prototype pollution, and multiple denial-of-service issues that can take down shared services or expose internal execution paths.

Act now: patch exposed developer and server-side packages first, then audit any workflows that parse untrusted files, accept user-controlled request headers, or run in shared network environments. Several of today’s issues have working workarounds, but the safest response is to upgrade immediately and reduce exposure until every affected component is confirmed fixed.

Critical Vulnerabilities

  • CVE-2026-114139: Sentry Next.js tunnel middleware bypass
    • Impact: Requests under the tunnel path can skip middleware and reach application routes that were meant to be protected, if authorization lives only in middleware.
    • Affected Systems: @sentry/nextjs on webpack-based Next.js builds with tunnelRoute enabled.
    • Immediate Action: Upgrade to 9.47.2, 10.75.2, or 11.0.0-rc.1 now.
    • Mitigation: Move authorization checks into route/layout/data-access code; disable or relocate tunnelRoute if needed.
  • CVE-2026-114135: Jupyter Server gateway WebSocket authorization gap
    • Impact: Authenticated users can open kernel channels without the required execute authorization.
    • Affected Systems: jupyter-server 2.0.0 through 2.5.0; manual use of deprecated gateway handlers remains risky in 2.6.0+.
    • Immediate Action: Upgrade to 2.6.0+ and review any custom gateway handler registration.
    • Mitigation: Remove restrictive reliance on middleware-only checks; validate kernel execution permissions server-side.
  • CVE-2026-114140: nbconvert arbitrary file write
    • Impact: Malicious notebooks can write files outside the intended output directory, including sensitive paths.
    • Affected Systems: nbconvert <= 7.17.1.
    • Immediate Action: Upgrade to 7.17.2 immediately.
    • Mitigation: Do not convert untrusted notebooks until patched; isolate conversion jobs.
  • CVE-2026-114142: toml prototype pollution
    • Impact: Crafted TOML can write to Object.prototype, affecting unrelated code across the process.
    • Affected Systems: npm toml 5.0.0 and related releases in the affected code path.
    • Immediate Action: Replace or patch toml before parsing any untrusted TOML.
    • Mitigation: Treat TOML from users, packages, or APIs as hostile; prefer a fixed release or alternate parser.
  • CVE-2026-114134: Black GitHub Action code execution via pyproject
    • Impact: A pull request can steer the action to install and run untrusted code.
    • Affected Systems: PSF Black GitHub Action with use_pyproject: true.
    • Immediate Action: Disable use_pyproject until a fixed workflow is in place.
    • Mitigation: Pin versions in workflow files and restrict PR-triggered execution on untrusted branches.
  • CVE-2026-114143: toml quadratic parse DoS
    • Impact: Long dotted keys can freeze Node.js processes and even trigger OOM crashes.
    • Affected Systems: npm toml 5.0.0 and related releases.
    • Immediate Action: Limit TOML input size and upgrade as soon as a fix is available.
    • Mitigation: Reject oversized or attacker-controlled TOML before parsing.
  • CVE-2026-114126: Storybook dev server token exposure
    • Impact: Any client on the same LAN can obtain the WebSocket token and potentially inject code into story files.
    • Affected Systems: Storybook dev servers on untrusted networks.
    • Immediate Action: Upgrade to 11.0.0-alpha.6, 10.6.2, 9.1.21, or 8.6.19.
    • Mitigation: Bind dev servers to 127.0.0.1 only unless sharing is intentional and controlled.
  • CVE-2026-114141: toml array-of-tables quadratic DoS
    • Impact: Repeated [[name]] headers can consume seconds of CPU in a single parse.
    • Affected Systems: npm toml 5.0.0 and related releases.
    • Immediate Action: Restrict untrusted TOML size and parse frequency now.
    • Mitigation: Upgrade when patched; consider input caps as defense-in-depth.
  • CVE-2026-114604: GraphQL Tools prototype pollution
    • Impact: Malformed incremental GraphQL paths can pollute object prototypes in the consuming process.
    • Affected Systems: @graphql-tools/utils 10.10.1 through 12.0.1.
    • Immediate Action: Upgrade to 12.0.2.
    • Mitigation: Validate path segments before merging incremental results.
  • CVE-2026-96640: Pillow PDF append CPU exhaustion
    • Impact: A compact malformed PDF can force expensive page-tree expansion and stall workers.
    • Affected Systems: Pillow PDF append path, including tested releases 12.3.0 and 13.0.0.dev0.
    • Immediate Action: Avoid appending to attacker-supplied PDFs until patched.
    • Mitigation: Reject duplicate or cyclic page-tree references before processing.
  • CVE-2026-94482: Next.js Server Action CPU exhaustion
    • Impact: Crafted requests can tie up CPU and block other requests in the same process.
    • Affected Systems: Next.js App Router apps with Server Actions.
    • Immediate Action: Upgrade immediately; no workaround exists.
    • Mitigation: Temporarily reduce exposure of public Server Action endpoints.
  • CVE-2026-96889: librsvg use-after-free via nested XInclude
    • Impact: Crafted SVG can trigger a use-after-free and crash or destabilize parsing.
    • Affected Systems: librsvg builds using libxml2.
    • Immediate Action: Apply the fix in commit 8a1b0cd319e9af2d1e9cf878081dd77f227a0504 or vendor a patched build.
    • Mitigation: Treat untrusted SVG as hostile input.
  • CVE-2026-96778: Pillow JPEG heap overflow
    • Impact: Re-saving crafted images as JPEG can crash the process and may be exploitable for code execution.
    • Affected Systems: Pillow JPEG encoder from 9.4.0 onward.
    • Immediate Action: Stop preserving untrusted ICC/comment metadata until patched.
    • Mitigation: Apply the vendor fix and retest image pipelines.
  • CVE-2026-114145: GitPython submodule path planting
    • Impact: An attacker-controlled submodule path can plant executable hook files in .git/hooks.
    • Affected Systems: GitPython 3.1.x through current tip.
    • Immediate Action: Block untrusted submodule paths and inspect repositories for planted hooks.
    • Mitigation: Upgrade and validate before clone/mutation, not after.
  • CVE-2026-114136: DRF JSONParser memory amplification
    • Impact: A tiny request can expand into tens of megabytes inside the parser, exhausting memory.
    • Affected Systems: djangorestframework 3.6.4 and later with default JSON parsing.
    • Immediate Action: Reject non-text codecs in Content-Type now.
    • Mitigation: Upgrade and apply decompressed-body limits.
  • CVE-2026-75508: GraphQL comment-padding memory DoS
    • Impact: Comment-heavy GraphQL documents bypass token limits and consume excessive memory.
    • Affected Systems: graphql-core 3.2.8 and similar affected releases.
    • Immediate Action: Upgrade to 3.2.12 or 3.3.0rc1.
    • Mitigation: Enforce decompressed request-size limits in front of validation.
  • CVE-2026-114138: DRF Accept-header CPU DoS
    • Impact: Large valid Accept headers can pin workers for many seconds.
    • Affected Systems: djangorestframework content negotiation on default deployments.
    • Immediate Action: Cap header size and request rate at the edge.
    • Mitigation: Upgrade and reduce repeated header parsing.
  • CVE-2026-75507: GraphQL overlapping-fields validation DoS
    • Impact: Small compressed queries can burn CPU for minutes during validation.
    • Affected Systems: graphql-core default validation rules.
    • Immediate Action: Upgrade to 3.2.12 or 3.3.0rc1.
    • Mitigation: Enforce query-size and validation budgets.
  • CVE-2026-114144: toml BigInt parsing DoS
    • Impact: A single huge integer literal can block the Node.js event loop for seconds.
    • Affected Systems: npm toml integer parsing path.
    • Immediate Action: Reject oversized numeric literals before parsing.
    • Mitigation: Upgrade and apply input-length limits.
  • CVE-2026-114137: DRF TokenProxy silent revocation failure
    • Impact: Token revocation can appear to succeed while the credential remains valid.
    • Affected Systems: djangorestframework 3.12.0 and later using TokenProxy.
    • Immediate Action: Audit every token-deletion path and confirm rows are actually removed.
    • Mitigation: Revoke concrete Token rows directly until a fix lands.
  • CVE-2026-96644: Pillow Windows metafile over-read
    • Impact: Crafted EMF/WMF files can trigger an out-of-bounds read on Windows builds.
    • Affected Systems: Pillow Windows image handling.
    • Immediate Action: Block untrusted metafiles on Windows endpoints.
    • Mitigation: Patch the native handler and retest file ingestion.
  • CVE-2026-96642: Pillow TarIO infinite loop
    • Impact: A malformed tar header can hang a process at 100% CPU indefinitely.
    • Affected Systems: Pillow TarIO helper usage.
    • Immediate Action: Avoid direct TarIO use on untrusted archives.
    • Mitigation: Add size validation and timeouts.
  • CVE-2026-96643: Pillow EXIF parsing quadratic DoS
    • Impact: Crafted PNG EXIF chunks can consume seconds of CPU on small files.
    • Affected Systems: Pillow EXIF parsing and ImageOps.exif_transpose().
    • Immediate Action: Upgrade and cap untrusted PNG metadata.
    • Mitigation: Reject oversized eXIf chunks before parsing.
  • CVE-2026-96637: Pillow SPIDER bomb-check bypass
    • Impact: Tiny SPIDER stack files can force multi-gigabyte allocations on load.
    • Affected Systems: Pillow SPIDER plugin, including current development builds.
    • Immediate Action: Block untrusted SPIDER files now.
    • Mitigation: Add bomb checks in alternate seek/open paths.

What to Do Now

  1. Patch first: prioritize @sentry/nextjs, jupyter-server, nbconvert, @graphql-tools/utils, graphql-core, djangorestframework, next, Pillow, storybook, GitPython, and black.
  2. Isolate risky workflows: pause or sandbox notebook conversion, image re-encoding, GraphQL incremental merging, TOML parsing, and dev-server sharing on untrusted networks.
  3. Verify exposure: search for tunnelRoute, use_pyproject: true, GatewayClient.url, direct TokenProxy.delete(), and Pillow JPEG/PDF append paths in your codebase.
  4. Harden the edge: enforce request-size, header-size, and decompressed-body limits; add timeouts for parsing and validation paths.
  5. Audit auth assumptions: confirm authorization is enforced in routes and data-access layers, not middleware alone.

Verification Steps

  • Confirm installed versions against the fixed releases listed above.
  • Check CI/CD workflows for untrusted PR execution and dynamic version reads from repository files.
  • Review logs for unusual Accept headers, oversized notebook uploads, repeated TOML parse failures, and unexpected WebSocket activity on dev servers.
  • Test token revocation and ensure the underlying database row disappears, not just the proxy object.

Monitoring Recommendations

  • Alert on sustained CPU spikes in worker processes handling parsing, validation, or image conversion.
  • Watch for unexpected file writes in build and conversion directories.
  • Track dev-server exposure on LANs and any non-local Storybook bindings.
  • Flag repeated 4xx/406 responses with unusually large headers or compressed payloads.

Related Resources

  • Internal blog post: Security Response Playbook for October 22, 2026 (to be published).
  • Internal blog post: Developer Dependency Triage for High-Severity CVEs (to be published).
  • Official vendor advisories: Sentry, Jupyter Server, nbconvert, Black, Storybook, Pillow, Next.js, GraphQL Tools, GraphQL-core, Django REST Framework, GitPython, librsvg, and toml project advisories.

Keep reading