此页面尚未翻译为您的语言。我们正在努力翻译，目前显示英文内容。
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2026-1184: Insecure Deserialization in GitLab
平台
gitlab
组件
gitlab
修复版本
18.11.3
CVE-2026-1184 addresses an Insecure Deserialization vulnerability discovered in GitLab EE. This flaw allows an unauthenticated user to induce a denial of service (DoS) by uploading a specially crafted file. The vulnerability impacts GitLab EE versions ranging from 11.9.0 through 18.11.3, and is resolved in version 18.11.3.
影响与攻击场景翻译中…
Successful exploitation of CVE-2026-1184 allows an attacker to disrupt GitLab services, rendering them unavailable to legitimate users. The attacker does not require authentication, significantly broadening the potential attack surface. The denial of service can manifest as system instability, performance degradation, or complete service outage. While the vulnerability doesn't directly lead to data exfiltration or code execution, the disruption of GitLab services can severely impact development workflows and project timelines. The impact is amplified in environments where GitLab is a critical component of the software development lifecycle.
利用背景翻译中…
CVE-2026-1184 was published on 2026-05-14. Its severity is currently assessed as Medium (CVSS 6.5). No public proof-of-concept (POC) code has been publicly released as of this writing. There are no indications of active exploitation campaigns targeting this vulnerability. The vulnerability is not currently listed on CISA Known Exploited Vulnerabilities (KEV) catalog.
威胁情报
漏洞利用状态
CVSS 向量
这些指标意味着什么？
- Attack Vector
- 网络 — 可通过互联网远程利用，无需物理或本地访问。攻击面最大。
- Attack Complexity
- 低 — 无需特殊条件，可以稳定地利用漏洞。
- Privileges Required
- 低 — 任何有效用户账户均可。
- User Interaction
- 无 — 攻击自动且无声，受害者无需任何操作。
- Scope
- 未改变 — 影响仅限于脆弱组件本身。
- Confidentiality
- 无 — 无机密性影响。
- Integrity
- 无 — 无完整性影响。
- Availability
- 高 — 完全崩溃或资源耗尽，完全拒绝服务。
受影响的软件
弱点分类 (CWE)
时间线
- 已保留
- 发布日期
缓解措施和替代方案翻译中…
The primary mitigation for CVE-2026-1184 is to upgrade GitLab EE to version 18.11.3 or later. If immediate upgrade is not feasible, consider implementing temporary workarounds such as restricting file uploads from unauthenticated users or implementing stricter file validation rules. Review GitLab's file upload policies and ensure they are enforced. Monitor GitLab logs for suspicious file upload activity. After upgrading, verify the fix by attempting a file upload with a known malicious payload (in a controlled environment) to confirm the vulnerability is no longer exploitable.
修复方法翻译中…
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 de deserialización de datos no confiables. Esta actualización corrige la validación incorrecta de archivos cargados, previniendo posibles ataques de denegación de servicio.
常见问题翻译中…
What is CVE-2026-1184 — Insecure Deserialization in GitLab?
CVE-2026-1184 is a Medium severity vulnerability in GitLab EE allowing unauthenticated users to trigger a denial of service by uploading a crafted file due to improper validation. It affects versions 11.9.0–18.11.3.
Am I affected by CVE-2026-1184 in GitLab?
You are affected if you are running GitLab EE versions 11.9.0 through 18.11.3. Versions prior to 18.11.3 are vulnerable to denial of service attacks.
How do I fix CVE-2026-1184 in GitLab?
Upgrade GitLab EE to version 18.11.3 or later to resolve the vulnerability. Consider temporary workarounds like restricting unauthenticated file uploads if immediate upgrade is not possible.
Is CVE-2026-1184 being actively exploited?
As of the current assessment, there are no indications of active exploitation campaigns targeting CVE-2026-1184.
Where can I find the official GitLab advisory for CVE-2026-1184?
Refer to the official GitLab security advisory for CVE-2026-1184 on the GitLab website: [https://gitlab.com/security/advisories/](https://gitlab.com/security/advisories/)
立即试用 — 无需账户
上传任何清单文件 (composer.lock, package-lock.json, WordPress 插件列表…) 或粘贴您的组件列表。您立即获得一份漏洞报告。上传文件只是开始：拥有账户后，您将获得持续监控、Slack/电子邮件警报、多项目和白标报告。
拖放您的依赖文件
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...