CVE-2025-4945: Libsoup: integer overflow in cookie expiration date handling in libsoup
A flaw was found in the cookie parsing logic of the libsoup HTTP library, used in GNOME applications and other software. The vulnerability arises when processing the expiration date of cookies, where a specially crafted value can trigger an integer overflow. This may result in undefined behavior, allowing an attacker to bypass cookie expiration logic, causing persistent or unintended cookie behavior. The issue stems from improper validation of large integer inputs during date arithmetic operations within the cookie parsing routines.
Security readout for executives and security teams
Plain-English summary
CVE-2025-4945 is a low-severity libsoup flaw where a specially crafted cookie expiration date can confuse date handling. The main business impact is integrity of cookie behavior: cookies may last longer than intended or behave unexpectedly. It is not described as data theft, service outage, or actively exploited in the supplied sources.
Executive priority
Treat this as routine patch management, not an emergency response. The issue can weaken cookie-expiration integrity, but the supplied evidence shows low severity, no confidentiality or availability impact, and no confirmed active exploitation. Include it in the next standard Linux maintenance cycle unless high-risk apps depend on libsoup cookie handling.
Technical view
libsoup cookie parsing can hit an integer overflow during expiration-date arithmetic, classified as CWE-190. The CVSS 3.1 score is 3.7 with network attack vector, high complexity, no privileges, no user interaction, and low integrity impact. Red Hat lists affected libsoup/libsoup3 packages across several RHEL streams.
Likely exposure
Exposure is most likely on Linux systems or applications using libsoup or libsoup3 cookie handling, especially the listed RHEL 7 ELS, 8, 9, and 10 package streams. RHEL 6 status is listed as unknown. Non-Red Hat exposure is not fully enumerated in the bundle.
Exploitation context
The bundle does not report active exploitation, and KEV status is false. A remote attacker would need a path to provide crafted cookie data to software using libsoup. The high attack complexity and limited integrity impact reduce urgency, but affected managed platforms should still receive vendor updates.
Researcher notes
Focus validation on cookie expiration parsing paths and large integer date handling, without assuming broader memory corruption impact beyond the supplied description. The affected-product evidence is strongest for Red Hat package streams. The bundle does not provide fixed version numbers or exploit telemetry beyond Red Hat advisories and the GNOME issue reference.
Mitigation direction
Apply the relevant Red Hat RHSA updates for affected RHEL package streams.
Check GNOME/libsoup and operating system vendor guidance for non-Red Hat distributions.
Prioritize systems where libsoup processes untrusted remote HTTP cookies.
Track RHEL 6 separately because the supplied status is unknown.
Validation and detection
Inventory installed libsoup and libsoup3 packages across Linux assets.
Compare package streams against the affected Red Hat entries in the source bundle.
Confirm applicable Red Hat errata are installed where RHEL is in use.
Identify applications that rely on libsoup cookie storage or HTTP session handling.
Document exceptions where vendor status remains unknown or unconfirmed.
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-190: 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-190 · source CWE mapping
Integer Overflow or Wraparound
Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.