# CVE-2025-4945: Libsoup: integer overflow in cookie expiration date handling in libsoup > An integer overflow in libsoup cookie parsing allows attackers to bypass expiration logic, leading to persistent or unintended cookie behavior. - **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 19 May 2025 - **Updated:** 30 Jun 2026 - **Also known as:** AZL-110483, DEBIAN-CVE-2025-4945, GHSA-mwcf-jv2p-mmpx, RHSA-2025:19720, RLSA-2025:19720, SUSE-SU-2025:02212-1, SUSE-SU-2025:02276-1, SUSE-SU-2025:02277-1, SUSE-SU-2025:02737-1, SUSE-SU-2025:03026-1, SUSE-SU-2025:03091-1, UBUNTU-CVE-2025-4945, openSUSE-SU-2025:15241-1, openSUSE-SU-2025:15242-1 ## What is CVE-2025-4945? CVE-2025-4945 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2025-4945? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `libsoup3` | Red Hat:enterprise_linux:10.0 | All versions | 0:3.6.5-3.el10_0.9 | | `libsoup3-debuginfo` | Red Hat:enterprise_linux:10.0 | All versions | 0:3.6.5-3.el10_0.9 | | `libsoup3-debugsource` | Red Hat:enterprise_linux:10.0 | All versions | 0:3.6.5-3.el10_0.9 | | `libsoup3-devel` | Red Hat:enterprise_linux:10.0 | All versions | 0:3.6.5-3.el10_0.9 | | `libsoup3-doc` | Red Hat:enterprise_linux:10.0 | All versions | 0:3.6.5-3.el10_0.9 | | `libsoup3` | Rocky Linux:10 | All versions | 0:3.6.5-3.el10_0.9 | | `libsoup` | SUSE:Linux Enterprise Micro 5.2 | All versions | 2.68.4-150200.4.12.1 | | `libsoup2` | SUSE:Linux Enterprise Micro 5.3 | All versions | 2.74.2-150400.3.12.1 | | `libsoup2` | SUSE:Linux Enterprise Micro 5.4 | All versions | 2.74.2-150400.3.12.1 | | `libsoup2` | SUSE:Linux Enterprise Micro 5.5 | All versions | 2.74.2-150400.3.12.1 | | `libsoup` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 3.4.4-150600.3.13.1 | | `libsoup2` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 2.74.3-150600.4.12.1 | | `libsoup` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 3.4.4-150600.3.13.1 | | `libsoup2` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 2.74.3-150600.4.12.1 | | `libsoup` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.62.2-5.18.1 | | `libsoup` | openSUSE:Leap 15.6 | All versions | 3.4.4-150600.3.13.1 | | `libsoup2` | openSUSE:Leap 15.6 | All versions | 2.74.3-150600.4.12.1 | | `libsoup` | openSUSE:Tumbleweed | All versions | 3.6.5-6.1 | | `libsoup2` | openSUSE:Tumbleweed | All versions | 2.74.3-12.1 | ## How do I fix CVE-2025-4945? Apply the vendor's patch. ## Is CVE-2025-4945 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4945 exists. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-4945 and fix it if it is affected. What it is: CVE-2025-4945 is a low-severity vulnerability in Red Hat Enterprise Linux 10, published on 19 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-4945 exists. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-4945/ (Markdown: https://insights.sbomify.com/CVE-2025-4945/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4945 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4945 - OSV: https://osv.dev/vulnerability/CVE-2025-4945 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-4945/ Summaries are generated and may contain mistakes; the official description above is the record.