dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2025-32906

HIGH · 7.5 CVSS v3.1 Published 2025-04-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A flaw was found in libsoup, where the soup_headers_parse_request() function may be vulnerable to an out-of-bound read. This flaw allows a malicious user to use a specially crafted HTTP request to crash the HTTP server.

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 confidence

libsoup's soup_headers_parse_request() function contains an out-of-bounds read vulnerability that allows attackers to crash the HTTP server by sending specially crafted HTTP requests with malformed headers.

MitigationUpdate libsoup to the patched version. If no patch available, implement input validation/filtering at the application layer to reject malformed HTTP headers before they reach the vulnerable function.

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Detect if libsoup library is installed
    Search for libsoup library files on the system. On Debian/Ubuntu: dpkg -l | grep libsoup. On RHEL/CentOS: rpm -qa | grep libsoup. Alternatively, find /usr/lib*/lib*.so* | grep -i soup
    Affected if No libsoup library is found on the system, then it is not affected
  2. Identify the installed libsoup version
    Run: pkg-config --modversion libsoup-3.0 (for libsoup3) or pkg-config --modversion libsoup-2.4 (for libsoup2). Or check via package manager: apt show lib libsoup-3.0-0 (Debian) or rpm -qi libsoup (RHEL)
    Affected if The installed version is lower than the patched version for CVE-2025-32906; if the exact patched version is unknown, any unpatched libsoup version is potentially affected
  3. Locate applications or services that use libsoup
    Search for binaries or services that link against libsoup: ldd /usr/sbin/* 2>/dev/null | grep -i soup; also check for custom applications in /opt, /usr/local, or application-specific directories
    Affected if Services or applications that handle HTTP requests are linked against libsoup and are running
  4. Determine if HTTP services using libsoup are network-exposed
    Review running services: netstat -tlnp | grep -E ':(80|443|8080)' or ss -tlnp. Identify which services use libsoup from step 3 and check if they bind to network interfaces other than localhost
    Affected if A network service using libsoup accepts HTTP connections from network sources, enabling remote attackers to send malformed headers

The environment is affected if libsoup is installed and any HTTP-handling service using it is network-accessible, allowing remote attackers to trigger the out-of-bounds read via malformed headers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update libsoup to the patched version. If no patch available, implement input validation/filtering at the application layer to reject malformed HTTP headers before they reach the vulnerable function.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,472.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32906 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-32906 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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