CVE-2025-32909
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 flaw was found in libsoup. SoupContentSniffer may be vulnerable to a NULL pointer dereference in the sniff_mp4 function. The HTTP server may cause the libsoup client to crash.
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 · moderate confidenceA NULL pointer dereference vulnerability exists in libsoup's SoupContentSniffer component, specifically in the sniff_mp4 function. When an attacker-controlled HTTP server sends a specially crafted response, the content sniffing logic attempts to dereference a NULL pointer, causing the libsoup client to crash.
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
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm libsoup library is installedOn Debian/Ubuntu: dpkg -l | grep libsoup. On RHEL/CentOS: rpm -qa | grep libsoup. On general Linux: find /usr -name 'libsoup*' 2>/dev/nullAffected if libsoup is present on the system
-
Identify installed libsoup versionRun: pkg-config --modversion libsoup-3.0 (for libsoup3) or pkg-config --modversion libsoup-2.4 (for libsoup2). Also check: dpkg -l | grep libsoup or rpm -q libsoupAffected if installed version is within the affected range and has not been patched
-
Determine if content sniffing is enabledCheck application code or configuration for SoupContentSniffer usage. Look for soup_content_sniffer_new() calls or SoupContentSniffer in any loaded modules. Grep source code or binary for 'ContentSniffer' patterns if possible.Affected if content sniffing is actively used in any client application making HTTP requests
-
Verify HTTP client usage with untrusted serversReview applications using libsoup for HTTP client functionality. Identify if they connect to external or untrusted HTTP servers where a malicious response could be received.Affected if libsoup-based applications make HTTP requests to potentially untrusted servers (especially without TLS)
You are affected if libsoup with an unpatched version is installed AND content sniffing is enabled in an application that makes HTTP requests to potentially attacker-controlled servers.
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 dataApply the vendor patch for CVE-2025-32909 which adds proper NULL pointer validation in the sniff_mp4 function before dereferencing pointers, and ensure libsoup is updated to the patched version in all affected deployments.
- Consultation3.0 h
- Implementation2.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32909 — 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-32909 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