dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2025-32910

MEDIUM · 6.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 →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 soup_auth_digest_authenticate() is vulnerable to a NULL pointer dereference. This issue 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 confidence

In libsoup, the soup_auth_digest_authenticate() function contains a NULL pointer dereference vulnerability. When processing digest authentication responses, certain conditions can lead to dereferencing a NULL pointer, causing the libsoup client to crash.

MitigationIf a patch is available, upgrade libsoup to the fixed version. Otherwise, implement NULL pointer checks in soup_auth_digest_authenticate() before dereferencing any pointers, particularly when handling authentication header parsing.

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 checks

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

  1. Identify installed libsoup version
    Run 'pkg-config --modversion libsoup-3.0' or check your package manager (dpkg -l libsoup*, rpm -q libsoup, etc.)
    Affected if The version is unknown or within any affected range; compare to any vendor advisory
  2. Confirm libsoup is in use
    Search application dependencies (requirements.txt, package.json, Makefile, or ldd/objdump on binaries) for libsoup linkage
    Affected if libsoup is linked and digest authentication may be used for HTTP client functionality
  3. Check for digest authentication usage
    Review application code for soup_auth_digest_new() calls or HTTP requests using Digest authentication headers
    Affected if The application makes HTTP requests that could trigger digest authentication flow
  4. Inspect crash logs for NULL dereference
    Check application logs, core dumps, or stderr for crashes mentioning 'soup_auth_digest_authenticate' or NULL pointer errors during auth
    Affected if Crashes occur during authentication handshake with digest method

You are affected if libsoup is installed, your application uses digest authentication, and crashes occur in soup_auth_digest_authenticate() or NULL pointer errors appear during auth processing.

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

If a patch is available, upgrade libsoup to the fixed version. Otherwise, implement NULL pointer checks in soup_auth_digest_authenticate() before dereferencing any pointers, particularly when handling authentication header parsing.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32910 — 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-32910 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