NPM · SEPTEMBER 2026 · EARLY WARNING

@zereight/mcp-gitlab DNS Rebinding Vulnerability

Q: Am I affected?

You are affected if you are using @zereight/mcp-gitlab in a version prior to 2.1.30.

Q: What should I do right now?

Upgrade to @zereight/mcp-gitlab version 2.1.30 or later as soon as possible.

Q: Has this vulnerability been exploited in the wild?

There is no confirmed report of this vulnerability being exploited in the wild at this time.

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

Severity: HIGH
Affected component: @zereight/mcp-gitlab (npm)
Affected versions: < 2.1.30 or < 2.1.30
Patched version: Not yet available

GHSA-VMP7-252J-CWP7

An early warning has been issued regarding a DNS rebinding vulnerability in @zereight/mcp-gitlab versions prior to 2.1.30. This vulnerability could potentially allow unauthorized access to local Streamable HTTP MCP transport.

What happened

The @zereight/mcp-gitlab package, when used in versions prior to 2.1.30, reportedly exposes its Streamable HTTP MCP endpoint without an effective Host or Origin allowlist. This configuration allows for DNS rebinding attacks, which could potentially grant unauthorized access to the local Streamable HTTP MCP transport.

This vulnerability, tracked as GHSA-vmp7-252j-cwp7, has a high severity rating. It is not yet confirmed to have been exploited in the wild. Users of @zereight/mcp-gitlab should assess their exposure by checking their current version against the affected range (< 2.1.30).

What to do about it

Upgrade to @zereight/mcp-gitlab version 2.1.30 or later to mitigate the DNS rebinding vulnerability.
Review your application's use of the Streamable HTTP MCP endpoint to ensure it is properly secured against DNS rebinding attacks.
Monitor the primary sources for updates on this vulnerability and any additional patches that may be released.

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If @zereight/mcp-gitlab is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using @zereight/mcp-gitlab in a version prior to 2.1.30.

What should I do right now?

Upgrade to @zereight/mcp-gitlab version 2.1.30 or later as soon as possible.

Has this vulnerability been exploited in the wild?

There is no confirmed report of this vulnerability being exploited in the wild at this time.

Sources

Join the 0Day waitlist →

← Back to all threats