NPM · SEPTEMBER 2026 · EARLY WARNING

@zereight/mcp-gitlab npm Package Vulnerability: Early Warning

Q: Am I affected?

You are potentially affected if you are using @zereight/mcp-gitlab npm package in versions less than 2.1.30.

Q: What should I do right now?

Avoid setting the ENABLE_DYNAMIC_API_URL environment variable to true and monitor the primary sources for updates on the vulnerability and any available patches.

Q: Is there a patched version available?

No official fix has been published yet. Monitor the sources for updates.

Q: What is the severity of this vulnerability?

The CVSS score for this vulnerability is 8.5, indicating a high severity level.

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
CVSS: 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N)
Affected component: @zereight/mcp-gitlab (npm)
Affected versions: < 2.1.30 or < 2.1.30
Patched version: Not yet available

GHSA-2H44-8472-FRJJ

An early warning has been issued for a high-severity vulnerability in the @zereight/mcp-gitlab npm package. This vulnerability, tracked as GHSA-2H44-8472-FRJJ, could allow Server-Side Request Forgery (SSRF) via the X-GitLab-API-URL header, potentially leading to credential theft.

What happened

The @zereight/mcp-gitlab npm package is reportedly vulnerable to Server-Side Request Forgery (SSRF) through the X-GitLab-API-URL header. This vulnerability, identified as GHSA-2H44-8472-FRJJ, allows an attacker to potentially steal credentials. The issue affects all versions of the package up to commit 74a8c83. Additionally, there are reports of other vulnerabilities in the same package, including unauthenticated arbitrary file read and DNS rebinding attacks, which could lead to further security risks.

The vulnerability was first flagged on September 15, 2026. It is currently under investigation, and no exploitation in the wild has been confirmed. The CVSS score for this vulnerability is 8.5, indicating a high severity level.

What to do about it

Avoid setting the ENABLE_DYNAMIC_API_URL environment variable to true.
Upgrade to a patched version of @zereight/mcp-gitlab when it becomes available.
Monitor the primary sources for updates on the vulnerability and any available patches.
Review your use of the X-GitLab-API-URL header and consider alternative secure methods.
Ensure that your environment is configured to minimize the risk of SSRF attacks.

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 potentially affected if you are using @zereight/mcp-gitlab npm package in versions less than 2.1.30.

What should I do right now?

Avoid setting the ENABLE_DYNAMIC_API_URL environment variable to true and monitor the primary sources for updates on the vulnerability and any available patches.

Is there a patched version available?

No official fix has been published yet. Monitor the sources for updates.

What is the severity of this vulnerability?

The CVSS score for this vulnerability is 8.5, indicating a high severity level.

Sources

Join the 0Day waitlist →

← Back to all threats