Security Digest: November 16, 2026 - 9 Critical Vulnerabilities

Today’s highest-risk issues span AI sandbox escape, OpenCTI authentication and authorization bypasses, Git remote code execution, MCP credential exposure, and storage firmware compromise. Several flaws allow attackers to move from a single authenticated account to full platform control, while others can expose secrets or execute code from an untrusted repository.

· 10 min read

Urgent Security Alert: 9 Critical Vulnerabilities Demand Immediate Action

Executive Summary

Today’s highest-risk issues span AI sandbox escape, OpenCTI authentication and authorization bypasses, Git remote code execution, MCP credential exposure, and storage firmware compromise. Several flaws allow attackers to move from a single authenticated account to full platform control, while others can expose secrets or execute code from an untrusted repository.

Act now: patch exposed systems immediately, restrict access to vulnerable services, and review logs for suspicious authentication attempts, privilege changes, and unusual repository activity.

Critical Vulnerabilities

CVE-2026-120699: CubeSandbox host-path mount escape

  • Impact: Authenticated tenants can mount arbitrary host paths into their sandbox, leading to host file access, code execution, container-runtime compromise, and cross-tenant impact.
  • Affected Systems: CubeSandbox prior to 0.5.1.
  • Immediate Action: Upgrade to 0.5.1 immediately. Temporarily restrict who can create sandboxes and disable host-mount features if possible.
  • Mitigation: Enforce allowlisted mount paths and review existing sandboxes for unexpected host mounts.

CVE-2026-104840: OpenCTI primary login brute-force exposure

  • Impact: Unauthenticated attackers can guess passwords at high speed and take over user accounts.
  • Affected Systems: OpenCTI prior to 7.260428.0.
  • Immediate Action: Upgrade to 7.260428.0 now. Add external rate limiting at the reverse proxy or WAF until patched.
  • Mitigation: Enforce MFA, monitor failed logins, and lock or reset any account showing suspicious login attempts.

CVE-2026-63477: OpenCTI organization admin privilege escalation

  • Impact: A tenant-scoped organization admin can escalate to global administrator and gain access across organizations, users, settings, connectors, and ingestion.
  • Affected Systems: OpenCTI prior to 7.260624.0.
  • Immediate Action: Patch to 7.260624.0 immediately. Review all organization admin memberships and grant scopes.
  • Mitigation: Remove unnecessary organization-admin privileges and audit for unexpected changes to grantable groups.

CVE-2026-76823: OpenCTI connector API leaks Elasticsearch credentials

  • Impact: Any holder of a connector API token can retrieve Elasticsearch credentials and potentially read, modify, or delete indices and audit data.
  • Affected Systems: OpenCTI prior to 7.260706.0.
  • Immediate Action: Upgrade to 7.260706.0. Rotate Elasticsearch credentials and connector API tokens after patching.
  • Mitigation: Limit connector token scope, restrict network reachability to Elasticsearch, and review access logs for unusual credential queries.

CVE-2026-57150: GLPI authorization bypass in massive actions

  • Impact: Authenticated users can perform state-changing actions outside their rights, including plugin activation, deactivation, and uninstallation.
  • Affected Systems: GLPI prior to 10.0.28, 11.0.10, and 12.0.1.
  • Immediate Action: Upgrade to the fixed release for your branch now. Review any recent plugin state changes.
  • Mitigation: Restrict privileged maintenance functions and monitor for unexpected plugin lifecycle changes.

CVE-2026-124017: Phison E12/E18 SSD Secure Boot bypass

  • Impact: A privileged local attacker can install persistent controller-level firmware implants that survive reinstallation and operate below the OS.
  • Affected Systems: Systems using Phison E12 and E18 PCIe SSD controllers.
  • Immediate Action: Prioritize physical and privileged-access controls; inventory affected hardware and follow vendor firmware guidance immediately.
  • Mitigation: Treat affected endpoints as high risk, limit local admin access, and validate firmware provenance after remediation.

CVE-2026-121708: OpenCTI draft workspace cross-user access

  • Impact: Any authenticated user can read or modify another user’s draft workspace content.
  • Affected Systems: OpenCTI prior to 7.260513.0.
  • Immediate Action: Upgrade to 7.260513.0 immediately. Assume unpublished intelligence may have been exposed.
  • Mitigation: Review draft workspace access patterns and rotate sensitive content if disclosure is suspected.

CVE-2026-111760: Git recursive submodule clone can execute attacker code

  • Impact: Cloning a malicious repository with --recurse-submodules can trigger code execution on the victim system.
  • Affected Systems: Git prior to 2.50.2, 2.51.3, 2.52.1, 2.53.1, 2.54.1, 2.55.1, and 2.56.1.
  • Immediate Action: Upgrade Git immediately. Stop cloning untrusted repositories with recursive submodules.
  • Mitigation: Use trusted forges only, disable recursive submodule cloning where possible, and inspect repositories before checkout.

CVE-2026-115563: MCP Python SDK OAuth credential disclosure

  • Impact: Untrusted MCP servers can cause clients to send OAuth secrets, authorization codes, PKCE verifiers, or signed client assertions to the wrong authorization server.
  • Affected Systems: MCP Python SDK versions 1.9.1 through 1.30.0 and 2.2.0 for affected OAuth client providers.
  • Immediate Action: Upgrade to 1.30.0 or 2.2.0 and configure issuer= for unattended providers. Clear or re-register stored OAuth client records.
  • Mitigation: Do not trust server-advertised authorization endpoints; verify issuer binding and re-authenticate impacted clients.

What to Do Now

  1. Patch exposed systems first: OpenCTI, GLPI, CubeSandbox, Git, and MCP SDK deployments should be at the top of the queue.
  2. Rotate secrets where credential exposure is possible: Elasticsearch credentials, connector tokens, OAuth client secrets, and any accounts used during suspicious login activity.
  3. Restrict access immediately: Limit sandbox creation, connector API use, privileged GLPI actions, and local admin access on affected endpoints.
  4. Review logs and alerts: Look for repeated login failures, unusual GraphQL queries, privilege changes, plugin lifecycle events, and unexpected repository clones.
  5. Validate remediation: Confirm version numbers after upgrades and verify that vulnerable paths, tokens, and mounts are no longer accepted.

Verification steps:

  • Confirm installed versions against the fixed releases listed above.
  • Check for any sandbox or workspace objects created or modified during the exposure window.
  • Audit administrative group membership, connector token usage, and Elasticsearch access.
  • Review endpoint and CI/CD activity for suspicious Git clone behavior.

Monitoring recommendations:

  • Alert on repeated authentication failures and rapid password-guessing patterns.
  • Watch for new admin grants, plugin changes, unexpected mounts, and draft workspace access from unusual users.
  • Track outbound connections from developer machines and build systems to unknown authorization servers.
  • Monitor for firmware anomalies and unauthorized local admin activity on machines with Phison controllers.

Related Resources

  • Internal: Refer to your internal incident response notes and patch-tracking dashboard; publish a dedicated internal blog post for each affected platform.
  • Official vendor advisories: CubeSandbox 0.5.1 release notes; OpenCTI advisories for 7.260428.0, 7.260513.0, 7.260624.0, and 7.260706.0; GLPI security advisories for 10.0.28, 11.0.10, and 12.0.1; Git security release notes; MCP Python SDK release notes for 1.30.0 and 2.2.0; Phison firmware/security guidance.

Keep reading