Memory disclosure or crash via boundary-check errors
Published Apr 3, 2025 · Updated Jun 30, 2026
Heap buffer over-read in GNOME libsoup before 3.6.1 allows remote attackers to read process memory or crash clients via crafted HTTP responses. In soup-content-sniffer.c, skip_insignificant_space() accepts a position equal to the buffer length, while sniff_feed_or_html() advances and reads resource[pos] without reserving the next byte. The target application must use content sniffing on a response from an attacker-controlled HTTP server; impact is limited to client memory disclosure or process termination.
Summary
What happened
Heap buffer over-read in GNOME libsoup before 3.6.1 allows remote attackers to read process memory or crash clients via crafted HTTP responses. In soup-content-sniffer.c, skip_insignificant_space() accepts a position equal to the buffer length, while sniff_feed_or_html() advances and reads resource[pos] without reserving the next byte. The target application must use content sniffing on a response from an attacker-controlled HTTP server; impact is limited to client memory disclosure or process termination.
The record
- CVE
- CVE-2025-32053
- Published
- Apr 3, 2025
- Updated
- Jun 30, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Enterprise Linux 9.2 Extended Update Support
- Classifications
- CWE-126
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 3, 2025CVE publishedPublication date reported by the CVE source.
- Jun 30, 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?
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