CVE-2025-32913: Libsoup: null pointer dereference in soup_message_headers_get_content_disposition when "filename" parameter is present, but has no value in content-disposition header

Published Apr 14, 2025
·
Updated

A flaw was found in libsoup, where the soupmessageheadersgetcontentdisposition() function is vulnerable to a NULL pointer dereference. This flaw allows a malicious HTTP peer to crash a libsoup client or server that uses this function.

Other sources

libsoup prior to 3.6.2 is vulnerable to a null pointer dereference in soupmessageheadersgetcontentdisposition() . A malicious HTTP peer may crash a libsoup client or server that uses this function.

Red Hat

Libsoup: null pointer dereference in soupmessageheadersgetcontentdisposition when "filename" parameter is present, but has no value in content-disposition header

Microsoft

This CVE was automatically created from a reference found in an email or other text. If you are reading this, then this CVE entry is probably erroneous, since this text should be replaced by the official CVE description automatically.

Launchpad

Affected Software

7 affected componentsFixes available
Gnome libsoup<3.6.2
debian/libsoup2.4<=2.72.0-2, <=2.74.3-1+deb12u1, <=2.74.3-10
2.72.0-2+deb11u22.74.3-10.1
debian/libsoup3<=3.2.2-2
3.6.5-1
Microsoft cbl2 libsoup 3.0.4-6<3.0.4-3
3.0.4-3
Microsoft azl3 libsoup 3.4.4-3<3.4.4-3
3.4.4-3
Microsoft azl3 libsoup 3.4.4-6<3.4.4-3
3.4.4-3
Microsoft cbl2 libsoup 3.0.4-3<3.0.4-3
3.0.4-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/libsoup2.4 to a version that resolves this vulnerability.

    Fixed in 2.72.0-2+deb11u2Fixed in 2.74.3-10.1
  2. Upgrade

    Upgrade debian/libsoup3 to a version that resolves this vulnerability.

    Fixed in 3.6.5-1
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.0.4-3
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.4.4-3
  5. Upgrade

    Upgrade libsoup to a version that resolves this vulnerability.

    Fixed in 3.6.2

Event History

Apr 14, 2025
Data Sourced
via Red Hat·02:00 AM
DescriptionSeverityAffected Software
CVE Published
via MITRE·01:37 PM
Data Sourced
via MITRE·01:37 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeakness
Apr 22, 2025
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
May 7, 2025
Data Sourced
via Launchpad·03:23 PM
Description
May 11, 2025
Data Sourced
via Ubuntu·03:22 PM
RemedyDescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-32913?

CVE-2025-32913 is a high-severity vulnerability that could lead to crashes in libsoup clients or servers.

2

How do I fix CVE-2025-32913?

To fix CVE-2025-32913, upgrade libsoup to version 3.6.2 or later.

3

Which versions of libsoup are affected by CVE-2025-32913?

CVE-2025-32913 affects libsoup versions prior to 3.6.2.

4

What type of vulnerability is CVE-2025-32913?

CVE-2025-32913 is a NULL pointer dereference vulnerability in the soup_message_headers_get_content_disposition() function.

5

Who can exploit CVE-2025-32913?

A malicious HTTP peer can exploit CVE-2025-32913 to crash a libsoup client or server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203