Server memory corruption via valueless filename parameter
Published Apr 15, 2025 · Updated Jun 29, 2026
Memory corruption in GNOME libsoup before 3.6.3 allows remote attackers to corrupt a server process via a crafted HTTP header. The content-disposition parser accepts a filename parameter without a value, then treats its NULL params-table value as a string during path stripping. Exposure requires a server application to pass attacker-controlled Content-Disposition headers through the affected API; the bounded result is process memory corruption.
Summary
What happened
Memory corruption in GNOME libsoup before 3.6.3 allows remote attackers to corrupt a server process via a crafted HTTP header. The content-disposition parser accepts a filename parameter without a value, then treats its NULL params-table value as a string during path stripping. Exposure requires a server application to pass attacker-controlled Content-Disposition headers through the affected API; the bounded result is process memory corruption.
The record
- CVE
- CVE-2025-32911
- Published
- Apr 15, 2025
- Updated
- Jun 29, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions
- Classifications
- CWE-590, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 15, 2025CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo