Security Digest: October 21, 2026 - 10 Critical Vulnerabilities

Ten critical vulnerabilities published today affect widely used npm, Maven, and Go components. The most urgent issues can let attackers read other users’ task data, crash Node.js services with a single request, leak credentials across redirects, or exhaust disk and memory.

· 9 min read

Urgent Security Alert: Patch and isolate now

Today’s risk is concentrated in agent/server frameworks, Markdown rendering, and file upload paths. Several of the issues below allow cross-user data exposure, denial of service, or credential leakage with little or no attacker effort. If you run any affected package, treat this as a same-day patch window and verify your deployment patterns immediately.

Executive Summary

Ten critical vulnerabilities published today affect widely used npm, Maven, and Go components. The most urgent issues can let attackers read other users’ task data, crash Node.js services with a single request, leak credentials across redirects, or exhaust disk and memory. Upgrade first, then confirm your code changes are compatible with the fixed releases.

Critical Vulnerabilities

CVE-2026-111767: MCP task session mix-up

  • Impact: Attackers can list, read, and cancel tasks created by other sessions.
  • Affected Systems: @modelcontextprotocol/sdk 1.24.0 through 1.31.0.
  • Immediate Action: Upgrade to @modelcontextprotocol/sdk 1.32.0 or later. Stop using experimental tasks if possible.
  • Mitigation: Remove taskStore, or isolate one InMemoryTaskStore per session.

CVE-2026-111770: MCP HTTP response mix-up

  • Impact: One client may receive another client’s responses and notifications over HTTP.
  • Affected Systems: @modelcontextprotocol/server 2.0.0 through 2.2.0.
  • Immediate Action: Upgrade to @modelcontextprotocol/server 2.3.0 or later.
  • Mitigation: Change code so each request or session gets a fresh server/transport instance; do not share a single server across clients.

CVE-2026-111758: markdown-it quadratic parsing DoS

  • Impact: A crafted Markdown document can freeze the Node.js event loop for seconds to over a minute.
  • Affected Systems: markdown-it 15.0.2 and related affected versions in the 14.x/15.x line.
  • Immediate Action: Upgrade to a fixed release and block oversized Markdown uploads until patched.
  • Mitigation: Disable the reference rule as a temporary workaround only if you can tolerate feature loss.

CVE-2026-113658: Apostrophe rejected upload leaves temp files behind

  • Impact: Repeated rejected uploads can fill temporary storage and disrupt the host.
  • Affected Systems: apostrophe rich-text CSV upload route.
  • Immediate Action: Restrict access to the endpoint now and monitor temp disk growth.
  • Mitigation: Patch the upload cleanup path; until then, remove or tightly gate the route.

CVE-2026-63209: klauspost/compress S2 dictionary overflow

  • Impact: A malformed S2 dictionary can crash the process with a segmentation fault.
  • Affected Systems: github.com/klauspost/compress/s2 up to v1.18.6.
  • Immediate Action: Upgrade to a fixed release as soon as it is available and reject untrusted dictionaries.
  • Mitigation: Never accept user-supplied S2 dictionary data without validation.

CVE-2026-111768: MCP tool input memory exhaustion

  • Impact: One request can consume heap memory and crash the service.
  • Affected Systems: @modelcontextprotocol/sdk 1.3.0 through 1.31.0; @modelcontextprotocol/server 2.0.0 through 2.2.0.
  • Immediate Action: Upgrade to @modelcontextprotocol/sdk 1.32.0+ or @modelcontextprotocol/server 2.3.0+.
  • Mitigation: Set maxToolInputElements and lower request body limits immediately.

CVE-2026-111759: markdown-it smartquotes quadratic DoS

  • Impact: Crafted text can drive high CPU usage when typography is enabled.
  • Affected Systems: markdown-it with typographer: true.
  • Immediate Action: Upgrade to 15.0.2 or 14.3.2.
  • Mitigation: Disable typographer or the smartquotes rule if you cannot patch immediately.

CVE-2026-111765: Android A2A client redirect credential leak

  • Impact: Redirects can forward API keys or tokens to a different authority.
  • Affected Systems: org.a2aproject.sdk:a2a-java-sdk-http-client-android versions affected by the surviving redirect override.
  • Immediate Action: Patch the client and verify redirects are disabled by default.
  • Mitigation: Force followRedirects(false) until the fix is shipped.

CVE-2026-111764: A2A server task store authorization bypass

  • Impact: One caller can read another caller’s tasks and task data.
  • Affected Systems: org.a2aproject.sdk:a2a-java-sdk-server-common <= 1.2.0.Final and 1.2.1.Final-SNAPSHOT before the fix.
  • Immediate Action: Add authorization checks now and upgrade to the fixed release when available.
  • Mitigation: Use a TaskAuthorizationProvider and ensure requests pass through the authorization decorator.

CVE-2026-113666: Apostrophe db-connect prototype deletion DoS

  • Impact: An authenticated user can delete shared prototype methods and break the whole Node process.
  • Affected Systems: @apostrophecms/db-connect 1.0.0 through 1.0.2; related apostrophe deployments using SQLite, PostgreSQL, or multipostgres adapters.
  • Immediate Action: Restrict authenticated API access and move off affected adapters where possible.
  • Mitigation: Patch the nested-field helpers to reject prototype-traversal paths immediately.

What to Do Now

  1. Patch the MCP stack first. Upgrade @modelcontextprotocol/sdk to 1.32.0+ and @modelcontextprotocol/server to 2.3.0+.
  2. Fix your code, not just your package lock. Several MCP issues require request/session-level refactoring after upgrade.
  3. Cap request size and tool complexity. Set body limits and maxToolInputElements before exposing MCP endpoints to untrusted clients.
  4. Block or patch Markdown rendering paths. If your app renders user Markdown, upgrade immediately and rate-limit large submissions.
  5. Audit file upload endpoints. Check for temp-file cleanup failures and watch disk usage on shared hosts.
  6. Review redirect behavior in mobile clients. Ensure credentials cannot cross authorities during redirects.

Verification steps:

  • Search your repos for taskStore, shared MCP server instances, typographer: true, and large-body parsers.
  • Confirm deployed versions against the ranges above.
  • Test that rejected uploads are deleted and that temp directories do not grow after failed requests.
  • Validate that redirects are disabled by default in Android HTTP clients.

Monitoring recommendations:

  • Alert on repeated 400 responses from upload endpoints paired with rising temp disk usage.
  • Watch for Node.js heap exhaustion, high CPU in Markdown rendering, and unexpected process restarts.
  • Log and alert on cross-session task access attempts and unusual MCP request patterns.
  • Track outbound redirects and credential-bearing requests to unexpected authorities.

Related Resources

  • Internal blog posts: Security team follow-up analysis and remediation notes will be published separately.
  • Official vendor advisories: GitHub Security Advisories for the CVEs listed above; npm, Maven, and project release notes for fixed versions.

Keep reading