Urgent.News

What's breaking now, across hundreds of outlets.

Tech

The MCP Inspector proxy trusted a redirect and inherited command execution

The MCP Inspector proxy trusted a redirect and inherited command execution Local developer tools sit in a useful but dangerous position. They run on a developer workstation, can often launch processes, and connect to servers supplied by the same user. MCP Inspector was built to test those servers, so a hostile server was always part of its threat model. The advisory GHSA-g9hg-qhmf-q45m describes…

The MCP Inspector proxy was found to trust a redirect and inherit command execution in a vulnerability described by CVE-2025-58444. This issue, classified as high severity under CVSS v4, allows a malicious redirect URI from an untrusted remote MCP server to inject script into the Inspector interface. The proxy then provides a pathway for this script execution to execute arbitrary commands on the developer's machine.

This is due to the Inspector rendering the redirect URI in a context where it could become executable script, a classification that falls under CWE-84, improper neutralization of encoded URI schemes in a web page. The impact is high, as the resulting process could potentially gain access to sensitive developer resources such as repository access, cloud tokens, SSH keys, package registry credentials, and shell history.

The vulnerability is addressed in version 0.16.6 of @modelcontextprotocol/inspector. To mitigate the risk, developers are advised to upgrade to this version and review how the Inspector is launched, ensuring it is configured to listen only on loopback interfaces and requiring authentication for remote boundaries.

Brief written by urgent.news; may contain errors — check the original.

Source: dev.to

Read the original at dev.to →

Report a problem with this story

More in Tech

Fix: Codex CLI zstd Compression 400 Error

Originally published on DebugRadar . Fix: Codex CLI zstd Compression 400 Error Quick Fix Summary Problem: Codex CLI requests fail with a bare 400 {"detail":"Bad Request"} on…

Progressive Web Apps: When a PWA Beats a Native App

Progressive web app development is the option most UK buyers dismiss in the first ten minutes of a project and rediscover eighteen months later, once the second native codebase has quietly eaten the…

  • PWAs provide a native app-like experience across multiple platforms using a single codebase.
  • Service workers enable offline capabilities and push notifications for PWAs.

Fix: iOS Codex Shows 'No Tasks Yet' Bug

Originally published on DebugRadar . Quick Fix Summary Problem: Codex on the ChatGPT iOS app shows "No tasks yet" / "Start a task to see it here" while the host still shows connected (green).

  • iOS Codex app shows "No tasks yet" bug while sessions are connected
  • Issue reported November 11, 2026, persists as of November 15, 2026
  • Resolved by using search function or notification links in app

Building Sentinel: Uptime Monitoring with Signed Reports and Quorum

The problem with a single uptime checker Most uptime monitors are one process making one HTTP request from one location. That is enough to catch most outages, but it has two blind spots: the checker…

  • Sentinel uses multiple independent validator nodes in different regions to monitor uptime.
  • Each validator signs its report with a signature to prove its identity.
  • Quorum consensus determines the final verdict based on majority agreement.

More from Sunday 22 November →