CVE-2025-32912
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, where SoupAuthDigest is vulnerable to a NULL pointer dereference. 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 confidenceIn libsoup, the SoupAuthDigest implementation contains a NULL pointer dereference vulnerability. When a malicious HTTP server sends specially crafted authentication challenges, it can trigger a crash in the libsoup client due to the dereference of an uninitialized or NULL pointer during digest authentication processing.
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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Identify libsoup installation and versionRun 'pkg-config --modversion libsoup-3.0' or 'dpkg -l | grep libsoup' (Debian) or 'rpm -qa | grep libsoup' (RHEL) to find the installed libsoup versionAffected if The installed version is any version prior to the fix for CVE-2025-32912 and the application using libsoup performs HTTP digest authentication
-
Identify applications using libsoup for HTTP requestsCheck installed applications known to use libsoup (such as GNOME Web/Epiphany, Evolution, or custom applications using libsoup/GIO) by reviewing installed packages or examining application dependenciesAffected if Applications linked against the vulnerable libsoup library are in use
-
Determine if digest authentication is in useInspect application logs, configuration files, or network traffic for HTTP 401 responses with 'WWW-Authenticate: Digest' headers, or check if applications are configured to connect to servers requiring digest authenticationAffected if Any client application using libsoup connects to HTTP servers that require or may attempt digest authentication
-
Monitor for authentication-related crashesReview system logs (journalctl, /var/log/syslog) or application crash reports for NULL pointer dereference errors occurring during HTTP authentication processingAffected if Crashes are observed in applications performing digest authentication against untrusted servers
A system is affected if it runs any version of libsoup prior to the fix that is used by applications performing HTTP digest authentication with potentially untrusted 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 dataUpdate libsoup to the version containing the fix. Until then, ensure clients only connect to trusted HTTP servers to avoid malicious authentication challenges.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32912 — 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-32912 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