此页面尚未翻译为您的语言。我们正在努力翻译,目前显示英文内容。

💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.

HIGHCVE-2026-1659CVSS 7.5

CVE-2026-1659: DoS in GitLab 9.0 - 18.11.3

平台

gitlab

组件

gitlab

修复版本

18.11.3

正在翻译为您的语言…

CVE-2026-1659 describes a denial-of-service vulnerability discovered in GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw allows an unauthenticated attacker to disrupt GitLab services by sending specially crafted requests, leading to resource exhaustion. The vulnerability impacts versions ranging from 9.0.0 through 18.11.3, and a fix is available in version 18.11.3.

影响与攻击场景翻译中…

Successful exploitation of CVE-2026-1659 can lead to a complete denial of service for GitLab instances. An attacker can overwhelm the server with malicious requests, preventing legitimate users from accessing the platform. This can disrupt critical development workflows, CI/CD pipelines, and collaboration efforts. The lack of authentication required for exploitation significantly broadens the attack surface, as any external user can potentially trigger the DoS. The impact is particularly severe for organizations heavily reliant on GitLab for their software development lifecycle.

利用背景翻译中…

CVE-2026-1659 was published on May 14, 2026. Severity is currently assessed as HIGH with a CVSS score of 7.5. No public proof-of-concept (POC) code has been released at the time of writing. There are no indications of active exploitation campaigns targeting this vulnerability. Monitor CISA advisories and GitLab security bulletins for updates.

威胁情报

漏洞利用状态

概念验证未知
CISA KEVNO
互联网暴露
报告1 份威胁报告

CISA SSVC

利用情况none
可自动化yes
技术影响partial

CVSS 向量

威胁情报· CVSS 3.1CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H7.5HIGHAttack VectorNetwork攻击者如何到达目标Attack ComplexityLow利用漏洞所需的条件Privileges RequiredNone攻击所需的认证级别User InteractionNone是否需要受害者采取行动ScopeUnchanged超出受影响组件的影响范围ConfidentialityNone敏感数据泄露风险IntegrityNone数据未授权篡改风险AvailabilityHigh服务中断风险nextguardhq.com · CVSS v3.1 基础分数
这些指标意味着什么?
Attack Vector
网络 — 可通过互联网远程利用,无需物理或本地访问。攻击面最大。
Attack Complexity
低 — 无需特殊条件,可以稳定地利用漏洞。
Privileges Required
无 — 无需认证,无需凭证即可利用。
User Interaction
无 — 攻击自动且无声,受害者无需任何操作。
Scope
未改变 — 影响仅限于脆弱组件本身。
Confidentiality
无 — 无机密性影响。
Integrity
无 — 无完整性影响。
Availability
高 — 完全崩溃或资源耗尽,完全拒绝服务。

受影响的软件

组件gitlab
供应商GitLab
最低版本9.0.0
最高版本18.11.3
修复版本18.11.3

弱点分类 (CWE)

时间线

  1. 已保留
  2. 发布日期

缓解措施和替代方案翻译中…

The primary mitigation for CVE-2026-1659 is to upgrade GitLab to version 18.11.3 or later. If an immediate upgrade is not feasible, consider implementing rate limiting on incoming requests to the GitLab instance to reduce the impact of potential attacks. Review GitLab's input validation mechanisms and consider implementing stricter controls to prevent malicious data from being processed. Monitor GitLab logs for unusual request patterns that may indicate exploitation attempts. After upgrading, confirm the fix by attempting to trigger the vulnerability with a crafted request; it should now be rejected.

修复方法翻译中…

Actualice GitLab a la versión 18.9.7 o superior, 18.10.6 o superior, o 18.11.3 o superior para mitigar la vulnerabilidad. Esta actualización aborda la falta de validación de entrada que permitía a usuarios no autenticados causar una denegación de servicio.

常见问题翻译中…

What is CVE-2026-1659 — DoS in GitLab 9.0 - 18.11.3?

CVE-2026-1659 is a denial-of-service vulnerability in GitLab CE/EE allowing unauthenticated users to cause service disruption via crafted requests due to insufficient input validation. It affects versions 9.0.0–18.11.3.

Am I affected by CVE-2026-1659 in GitLab 9.0 - 18.11.3?

If you are running GitLab CE or EE versions 9.0.0 through 18.11.3, you are potentially affected by this vulnerability. Check your GitLab version immediately.

How do I fix CVE-2026-1659 in GitLab 9.0 - 18.11.3?

Upgrade GitLab to version 18.11.3 or later to resolve this vulnerability. Consider rate limiting as a temporary mitigation if an immediate upgrade is not possible.

Is CVE-2026-1659 being actively exploited?

There are currently no indications of active exploitation campaigns targeting CVE-2026-1659, but it's crucial to apply the fix promptly.

Where can I find the official GitLab advisory for CVE-2026-1659?

Refer to the official GitLab security advisory for detailed information and updates: [https://gitlab.com/security/security advisories](https://gitlab.com/security/security advisories)

你的项目受影响吗?

上传你的依赖文件,立即了解此CVE和其他CVE是否影响你。

live免费扫描

立即试用 — 无需账户

上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始:拥有账户后,您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。

手动扫描Slack/邮件提醒持续监控白标报告

拖放您的依赖文件

composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...