Deze pagina is nog niet vertaald naar uw taal. We werken eraan — de inhoud wordt voorlopig in het Engels weergegeven.
💡 Keep dependencies up to date — most exploits target known, patchable vulnerabilities.
CVE-2025-14869: DoS in GitLab
Platform
gitlab
Component
gitlab
Opgelost in
18.11.3
CVE-2025-14869 describes a denial-of-service vulnerability discovered in GitLab Community Edition (CE) and Enterprise Edition (EE). This flaw allows an unauthenticated user to trigger a DoS condition by exploiting specific API endpoints with specially crafted payloads. The vulnerability impacts versions 18.5.0 through 18.11.3 and is resolved in version 18.11.3.
Impact en Aanvalsscenarioswordt vertaald…
Successful exploitation of CVE-2025-14869 can lead to a denial-of-service condition, rendering affected GitLab instances unavailable to legitimate users. An attacker could repeatedly send malicious payloads, overwhelming the server's resources and causing it to crash or become unresponsive. The impact extends beyond simple service disruption; prolonged DoS attacks can hinder critical development workflows, impact CI/CD pipelines, and potentially lead to data loss if recovery is delayed. While the vulnerability requires no authentication, the attacker needs to be able to reach the targeted API endpoints, which might be restricted by firewalls or network configurations.
Uitbuitingscontextwordt vertaald…
CVE-2025-14869 was published on 2026-05-14. The vulnerability's impact is considered high due to the potential for widespread service disruption. No public exploits or active campaigns have been reported at the time of writing. The vulnerability is not currently listed on KEV or EPSS, suggesting a low probability of immediate exploitation, but proactive patching is still recommended.
Dreigingsinformatie
Exploit Status
CVSS-vector
Wat betekenen deze metrics?
- Attack Vector
- Netwerk — op afstand uitbuitbaar via internet. Geen fysieke of lokale toegang vereist.
- Attack Complexity
- Laag — geen speciale voorwaarden vereist. Betrouwbaar uitbuitbaar.
- Privileges Required
- Geen — geen authenticatie vereist om te exploiteren.
- User Interaction
- Geen — automatische en stille aanval. Slachtoffer doet niets.
- Scope
- Ongewijzigd — impact beperkt tot het kwetsbare component.
- Confidentiality
- Geen — geen vertrouwelijkheidsimpact.
- Integrity
- Geen — geen integriteitsimpact.
- Availability
- Hoog — volledige crash of uitputting van resources. Totale denial of service.
Getroffen Software
Zwakheidsclassificatie (CWE)
Tijdlijn
- Gereserveerd
- Gepubliceerd
Mitigatie en Workaroundswordt vertaald…
The primary mitigation for CVE-2025-14869 is to upgrade GitLab to version 18.11.3 or later. If immediate upgrading is not feasible, consider implementing rate limiting on the affected API endpoints to restrict the number of requests from a single source within a given timeframe. Web Application Firewalls (WAFs) configured to detect and block malicious payloads targeting API endpoints can also provide a temporary layer of protection. Review GitLab's network configuration to ensure only authorized traffic can access the API endpoints.
Hoe te verhelpenwordt vertaald…
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 corrige una falla de validación de cantidad en ciertos puntos finales de la API que podría permitir a un usuario no autenticado causar una denegación de servicio.
Veelgestelde vragenwordt vertaald…
What is CVE-2025-14869 — DoS in GitLab?
CVE-2025-14869 is a denial-of-service vulnerability in GitLab CE/EE allowing unauthenticated users to disrupt service by sending crafted payloads to specific API endpoints. It affects versions 18.5.0–18.11.3 and is rated HIGH severity.
Am I affected by CVE-2025-14869 in GitLab?
You are affected if you are running GitLab CE/EE versions 18.5.0 through 18.11.3. Upgrade to 18.11.3 or later to mitigate the risk.
How do I fix CVE-2025-14869 in GitLab?
The recommended fix is to upgrade GitLab to version 18.11.3 or a later version. As a temporary workaround, implement rate limiting on affected API endpoints.
Is CVE-2025-14869 being actively exploited?
Currently, there are no reports of CVE-2025-14869 being actively exploited, but proactive patching is still recommended to prevent potential future attacks.
Where can I find the official GitLab advisory for CVE-2025-14869?
Refer to the official GitLab security advisory for CVE-2025-14869 on the GitLab website: [https://gitlab.com/security/advisories/](https://gitlab.com/security/advisories/)
Is jouw project getroffen?
Upload je dependency-bestand en kom direct te weten of deze en andere CVEs jou raken.
Probeer het nu — geen account
Upload een manifest (composer.lock, package-lock.json, WordPress pluginlijst…) of plak uw componentenlijst. U ontvangt direct een kwetsbaarheidsrapport. Een bestand uploaden is slechts het begin: met een account krijgt u continue monitoring, Slack/e-mail alerts, multi-project en white-label rapporten.
Sleep uw afhankelijkheidsbestand hierheen
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...