CVE-2025-4969
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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).
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA memory safety vulnerability exists in libsoup's multipart HTTP message parser. The library fails to properly verify message termination boundaries, allowing a remote attacker to send specially crafted multipart HTTP bodies that cause the server to read beyond allocated memory buffers (out-of-bounds read). This occurs during parsing of the multipart/form-data or similar multipart content types.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if libsoup is installedCheck for libsoup library files on the system (common paths include /usr/lib/, /usr/local/lib/, or via package manager: dpkg -l | grep libsoup, rpm -qa | grep libsoup)Affected if libsoup library is present on the system
-
Determine installed libsoup versionRun 'pkg-config --modversion libsoup-3.0' or 'pkg-config --modversion libsoup-2.4' depending on the version found, or check via package managerAffected if the installed version has not yet received the boundary termination verification fix (compare against the latest patched release)
-
Verify if applications use libsoup for HTTP handlingReview application dependencies or configuration to confirm libsoup is used for handling HTTP requests (check application documentation, ldd output on binaries, or runtime dependencies)Affected if applications or services rely on libsoup to handle incoming HTTP requests
-
Confirm if multipart content types are processedCheck if the server or application accepts multipart/form-data, multipart/mixed, or similar multipart content types in HTTP requests (inspect configuration files, web server settings, or API endpoints)Affected if the environment processes multipart HTTP body content through libsoup
-
Check for application-layer validation before libsoupInspect if there is a proxy, WAF, or application-layer validation that validates multipart message structure and enforces request size limits before content reaches libsoupAffected if no intermediate validation layer exists and multipart content goes directly to libsoup for parsing
The environment is affected if libsoup is used to parse multipart HTTP content without additional validation or a patched version.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate libsoup to the latest patched version that includes proper boundary termination verification. If patching is not immediately possible, implement request size limits and validate multipart message structure at a proxy or application layer before reaching libsoup.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4969 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4969 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data