CVE-2025-4969: Libsoup: off-by-one out-of-bounds read in find_boundary() in soup-multipart.c
A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond its allocated memory boundaries (out-of-bounds read).
Security readout for executives and security teams
Plain-English summary
CVE-2025-4969 is a libsoup multipart HTTP parsing flaw. A remote unauthenticated sender could provide a malformed multipart body that makes a libsoup-using server read beyond allocated memory. The cited impact is limited confidentiality exposure and possible service disruption, with no integrity impact stated.
Executive priority
Treat this as a moderate patch-management item, higher for externally reachable services handling multipart uploads. It does not currently justify emergency response based on the provided evidence, but affected RHEL 9 and 10 systems should be tracked for vendor updates.
Technical view
The flaw is an off-by-one out-of-bounds read in find_boundary() in soup-multipart.c. Sources attribute it to incorrect verification of multipart HTTP message termination. CVSS 3.1 is 6.5: network reachable, low complexity, no privileges, no user interaction, low confidentiality and availability impact.
Likely exposure
Most relevant exposure is servers or applications using libsoup/libsoup3 to process multipart HTTP bodies. Red Hat lists RHEL 9 and RHEL 10 libsoup3 as affected, while RHEL 6, 7, and 8 libsoup status is unknown in the provided data.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The vulnerability is remotely reachable over network paths where a libsoup-consuming service accepts crafted multipart HTTP input, but the provided sources do not describe public exploit code or real-world attacks.
Researcher notes
Evidence supports CWE-125 out-of-bounds read from multipart boundary termination handling in libsoup. The bundle does not provide exact fixed versions, patch commits, or exploit telemetry. Avoid assuming impact beyond low confidentiality and low availability unless vendor analysis adds detail.
Mitigation direction
Check Red Hat and GNOME guidance for fixed libsoup or libsoup3 packages.
Apply vendor-provided updates when they become available for affected platforms.
Prioritize internet-facing services that accept multipart HTTP uploads or form submissions.
Track RHEL 6, 7, and 8 status because the provided bundle marks them unknown.
Use existing edge controls to limit untrusted multipart request exposure where practical.
Validation and detection
Inventory systems with libsoup or libsoup3 installed.
Identify applications that link to libsoup and process multipart HTTP bodies.
Confirm whether any affected RHEL 9 or RHEL 10 hosts are exposed externally.
Review Red Hat advisories for package status and remediation availability.
Document unknown-status platforms separately until vendor status is clarified.
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-125: 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-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.