CVE-2025-11021: Libsoup: out-of-bounds read in cookie date handling of libsoup http library
A flaw was found in the cookie date handling logic of the libsoup HTTP library, widely used by GNOME and other applications for web communication. When processing cookies with specially crafted expiration dates, the library may perform an out-of-bounds memory read. This flaw could result in unintended disclosure of memory contents, potentially exposing sensitive information from the process using libsoup.
Security readout for executives and security teams
Plain-English summary
CVE-2025-11021 is an out-of-bounds read in libsoup cookie expiration-date parsing. A malicious or compromised web endpoint could trigger memory disclosure from an application using libsoup to process cookies. The known impact is confidentiality only; the provided sources do not show code execution, data modification, or service outage.
Executive priority
Treat this as a high-priority patching item for Red Hat fleets because it can expose process memory without authentication or user interaction. It is not currently supported as an emergency exploitation response by the provided sources, but confidentiality impact warrants timely remediation.
Technical view
libsoup and libsoup3 can read past intended memory bounds while handling specially crafted cookie expiration dates. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, score 7.5. Red Hat lists multiple RHEL 7 ELS, 8, 9, and 10 package streams as affected.
Likely exposure
Exposure is most likely on Red Hat systems running affected libsoup or libsoup3 packages, especially applications that make HTTP requests and accept cookies from remote services. Non-Red Hat exposure is plausible because libsoup is used beyond RHEL, but the provided affected list only substantiates Red Hat package streams.
Exploitation context
The bundle does not cite active exploitation, and KEV is false. The issue is remotely reachable in theory because cookie data can arrive over network HTTP interactions, but the sources do not provide exploit maturity, proof-of-concept status, or attacker prevalence.
Researcher notes
Focus validation on package provenance, linked applications, and cookie-handling exposure. The provided evidence supports out-of-bounds read and memory disclosure risk, not integrity or availability impact. Red Hat marks RHEL 6 status unknown, so do not infer exposure or fixes without vendor confirmation.
Mitigation direction
Apply the relevant Red Hat security advisory updates for affected RHEL streams.
Inventory systems for installed libsoup and libsoup3 packages.
Prioritize internet-facing or high-trust applications that process external HTTP cookies.
Check upstream GNOME/libsoup and OS vendor guidance for non-Red Hat platforms.
Restart affected applications after library updates where required by vendor guidance.
Validation and detection
Confirm installed libsoup or libsoup3 package versions against the affected Red Hat list.
Verify applicable RHSA updates are installed on each affected RHEL stream.
Identify applications dynamically linked to libsoup that process untrusted HTTP responses.
Review vulnerability scanner findings for CVE-2025-11021 and reconcile false positives manually.
Document unsupported or unknown-status platforms, including RHEL 6, for risk acceptance or upgrade planning.
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.