# CVE-2025-53603: Null dereference in SOPE

> An attacker can crash the SOGo server by sending a request with duplicate parameters in the query string and POST body.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jul 2025
- **Updated:** 26 Jan 2026
- **Also known as:** DEBIAN-CVE-2025-53603, DLA-4260-1, DSA-5970-1, GHSA-78j7-w964-99fc, MGASA-2025-0255, UBUNTU-CVE-2025-53603

## What is CVE-2025-53603?

CVE-2025-53603 is a high-severity vulnerability in Alinto SOPE, published on 5 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Alinto SOPE SOGo 2.0.2 through 5.12.2, sope-core/NGExtensions/NGHashMap.m allows a NULL pointer dereference and SOGo crash via a request in which a parameter in the query string is a duplicate of a parameter in the POST body.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2025-53603?


## How do I fix CVE-2025-53603?

Apply the vendor's patch.

## Is CVE-2025-53603 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53603 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53603 and fix it if it is affected.

What it is: CVE-2025-53603 is a high-severity vulnerability in Alinto SOPE, published on 5 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53603 exists.

Affected product: Alinto SOPE. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53603/ (Markdown: https://insights.sbomify.com/CVE-2025-53603/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53603
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53603
- OSV: https://osv.dev/vulnerability/CVE-2025-53603

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53603/
Summaries are generated and may contain mistakes; the official description above is the record.