CVE-2025-32051: Libsoup: segmentation fault when parsing malformed data uri
A flaw was found in libsoup. The libsoup soup_uri_decode_data_uri() function may crash when processing malformed data URI. This flaw allows an attacker to cause a denial of service (DoS).
Security readout for executives and security teams
Plain-English summary
CVE-2025-32051 is a denial-of-service flaw in libsoup. A malformed data URI can make the library crash, potentially taking down an application that relies on it. The available sources do not show data theft, code execution, or active exploitation.
Executive priority
Treat this as a moderate availability risk. It is not currently evidenced as exploited or confidentiality-impacting, but services that parse untrusted data URIs should be checked because a crash can still affect uptime.
Technical view
The flaw is in libsoup's soup_uri_decode_data_uri() handling of malformed data URIs, leading to a segmentation fault. CVSS 3.1 is 5.9 with network attack vector, high complexity, no privileges, no user interaction, and availability impact only. CWE-754 is listed.
Likely exposure
Exposure is most likely in applications that use libsoup and process untrusted data URIs. Red Hat lists RHEL 8, 9, and 10 as unaffected for the relevant packages, while RHEL 6 and 7 status is unknown in the bundle.
Exploitation context
The bundle does not indicate active exploitation, and KEV is false. Exploitation would require malformed data URI input reaching the vulnerable parsing path. The CVSS vector rates attack complexity as high and impact as availability-only.
Researcher notes
The source evidence describes a crash in soup_uri_decode_data_uri() but does not provide complete affected upstream version ranges or a named fixed release. Red Hat marks several enterprise versions unaffected and older versions unknown, so validation should be package-specific.
Mitigation direction
Check Red Hat and upstream GNOME guidance for package status and fixes.
Inventory applications and packages that depend on libsoup or libsoup3.
Prioritize review of internet-facing services that parse untrusted data URIs.
Update affected packages when vendor-supported fixes become available.
Monitor crash loops or segmentation faults in libsoup-linked services.
Validation and detection
Confirm installed OS versions and libsoup package names against vendor status.
Identify services or applications linking against libsoup or libsoup3.
Review whether those services accept untrusted data URI input.
Check application logs for crashes around URI or data URI parsing.
Track Red Hat Bugzilla and GNOME issue updates for confirmed affected versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-754: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-754 · source CWE mapping
Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.