CVE-2025-53603 json
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…
published 2025-07-05 16 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-20097
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 54%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- sope Debian 12 5.8.0-1+deb12u1
- sope Debian 14, Debian 13 5.12.1-2
debian advisories DEBIAN-CVE-2025-53603
- github.com/Alinto/sope@280104e commit
- github.com/Alinto/sope#69 pull request
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 16 mo ago
Exploit prediction
0.74% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- openwall.com https://www.openwall.com/lists/oss-security/2025/07/02/3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected products
- Alinto SOPE
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
- github.com /Alinto/sope/pull/69
- github.com /Alinto/sope/commit/280104e45c20519ac4849ebf8bca114d91383543
-
openwall.com
/lists/oss-security/2025/07/02/3
exploit
- github.com /Alinto/sope/compare/SOGo-2.0.1...SOGo-2.0.2
- github.com /Alinto/sope/blob/3146fbdb6ff3314e37e5c3682deeeef7d0f32064/sope-core/NGExtensions/NGHashMap.m#L790
- lists.debian.org /debian-lts-announce/2025/08/msg00001.html
- openwall.com /lists/oss-security/2025/07/05/1
Sources
- CVE List CVE-2025-53603
- NVD CVE-2025-53603
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.