Skip to content
Fencer Intel
high 8.4

CVE-2024-52531 json

GNOME libsoup before 3.6.1 allows a buffer overflow in applications that perform conversion to...

published 2y ago modified 2mo ago also EUVD-2024-45941 , GHSA-5mc3-gwcr-mgc3 , JLSEC-2026-1278

cvss
8.4
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

GNOME libsoup before 3.6.1 allows a buffer overflow in applications that perform conversion to UTF-8 in soup_header_parse_param_list_strict. There is a plausible way to reach this remotely via soup_message_headers_get_content_type (e.g., an application may want to retrieve the content type of a request or response).

Patch / fix

  • GNOME libsoup 3.6.1
  • libsoup3 Debian 12 3.2.3-0+deb12u1
  • libsoup3 Debian 13 3.6.0-4
  • libsoup2.4 Debian 12 2.74.3-1+deb12u1
  • libsoup2.4 Debian 13 2.74.3-8.1

debian advisories DEBIAN-CVE-2024-52531

  • libsoup3 Ubuntu 24.04 LTS 3.4.4-5ubuntu0.1
  • libsoup2.4 Ubuntu 20.04 LTS 2.70.0-1ubuntu0.1
  • libsoup2.4 Ubuntu 22.04 LTS 2.74.2-3ubuntu0.1
  • libsoup2.4 Ubuntu 24.04 LTS 2.74.3-6ubuntu1.1
  • libsoup3 Ubuntu Pro 22.04 LTS 3.0.7-0ubuntu1+esm1
  • libsoup2.4 Ubuntu Pro 16.04 LTS 2.52.2-1ubuntu0.3+esm4
  • libsoup2.4 Ubuntu Pro 18.04 LTS 2.62.1-1ubuntu0.4+esm1

ubuntu advisories UBUNTU-CVE-2024-52531

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • libsoup RHEL 8 2.62.3-7.el8_10
  • libsoup RHEL 9 2.72.0-8.el9_5.3
  • libsoup RHEL 8.8 EUS 2.62.3-3.el8_8.2
  • libsoup RHEL 7 ELS 2.62.2-4.el7_9
  • libsoup RHEL 8.6 TUS, RHEL 8.6 E4S, RHEL 8.6 AUS 2.62.3-2.el8_6.2
  • libsoup RHEL 8.2 AUS 2.62.3-1.el8_2.2
  • libsoup RHEL 8.4 TUS, RHEL 8.4 E4S, RHEL 8.4 AUS 2.62.3-2.el8_4.2
  • libsoup RHEL 9.0 E4S 2.72.0-8.el9_0.3

red hat advisories RHSA-2025:1075RHSA-2025:1047RHSA-2025:0949RHSA-2025:0903RHSA-2025:0889RHSA-2025:0882

  • libsoup Linux Micro 6.1 3.4.4-slfo.1.1_2.1
  • libsoup Linux Micro 6.0 3.4.2-5.1
  • libsoup SLES for SAP 15 SP3, SLES for SAP 15 SP2, SLES 15 SP3-LTSS +5 more 2.68.4-150200.4.3.1
  • libsoup SLE Module for Basesystem 15 SP6, openSUSE Leap 15.6 3.4.4-150600.3.3.1
  • libsoup SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Module for Basesystem 15 SP5 +5 more 3.0.4-150400.3.3.1
  • libsoup2 SLES for SAP 15 SP4, SLES 15 SP4-LTSS, SLE Module for Basesystem 15 SP5 +9 more 2.74.2-150400.3.3.1
  • libsoup2 SLE Module for Basesystem 15 SP6, openSUSE Leap 15.6 2.74.3-150600.4.3.1
  • libsoup SLES LTSS Extended Security 12 SP5, SLES 12 SP5-LTSS 2.62.2-5.12.1

suse advisories SUSE-SU-2025:1518-1SUSE-SU-2025:20252-1SUSE-SU-2025:20105-1SUSE-SU-2024:4365-1SUSE-SU-2024:4355-1SUSE-SU-2024:4352-1

  • libsoup openSUSE Tumbleweed 3.6.0-2.1
  • libsoup2 openSUSE Tumbleweed 2.74.3-4.1

opensuse advisories openSUSE-SU-2024:14488-1openSUSE-SU-2024:14489-1

  • libsoup AlmaLinux 8 2.62.3-7.el8_10
  • libsoup AlmaLinux 9 2.72.0-8.el9_5.3

almalinux advisories ALSA-2025:0838ALSA-2025:0791

  • libsoup Rocky Linux 9 2.72.0-8.el9_5.3
  • libsoup Rocky Linux 8 2.62.3-7.el8_10

rocky linux advisories RLSA-2025:0791RLSA-2025:0838

  • libsoup Azure Linux 3.0 3.4.4-2
  • libsoup CBL-Mariner 2.0 3.0.4-2

azure linux advisories AZL-53063AZL-53076

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2024-52531 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-52531 updated cvss 9.0

libsoup: buffer overflow via UTF-8 conversion in soup_header_parse_param_list_strict

  • Red Hat Enterprise Linux 6 libsoup
    affected: workaround, no fix planned “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Enterprise Linux 10 libsoup3
    affected: workaround, no fix available “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.”
  • Red Hat Enterprise Linux AppStream (v. 8) libsoup-devel 2.62.3-7.el8_10, libsoup-debuginfo 2.62.3-7.el8_10, libsoup-debugsource 2.62.3-7.el8_10
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0838
  • Red Hat Enterprise Linux AppStream (v. 9) libsoup 2.72.0-8.el9_5.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0791
  • Red Hat Enterprise Linux AppStream AUS (v.8.4) libsoup-devel 2.62.3-2.el8_4.2, libsoup-debuginfo 2.62.3-2.el8_4.2, libsoup-debugsource 2.62.3-2.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0889
  • Red Hat Enterprise Linux AppStream AUS (v.8.6) libsoup-devel 2.62.3-2.el8_6.2, libsoup-debuginfo 2.62.3-2.el8_6.2, libsoup-debugsource 2.62.3-2.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0949
  • Red Hat Enterprise Linux AppStream E4S (v.8.4) libsoup-devel 2.62.3-2.el8_4.2, libsoup-debuginfo 2.62.3-2.el8_4.2, libsoup-debugsource 2.62.3-2.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0889
  • Red Hat Enterprise Linux AppStream E4S (v.8.6) libsoup-devel 2.62.3-2.el8_6.2, libsoup-debuginfo 2.62.3-2.el8_6.2, libsoup-debugsource 2.62.3-2.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0949
show 18 more
  • Red Hat Enterprise Linux AppStream E4S (v.9.0) libsoup 2.72.0-8.el9_0.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0882
  • Red Hat Enterprise Linux AppStream EUS (v.8.8) libsoup-devel 2.62.3-3.el8_8.2, libsoup-debuginfo 2.62.3-3.el8_8.2, libsoup-debugsource 2.62.3-3.el8_8.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:1075
  • Red Hat Enterprise Linux AppStream EUS (v.9.2) libsoup 2.72.0-8.el9_2.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0847
  • Red Hat Enterprise Linux AppStream EUS (v.9.4) libsoup 2.72.0-8.el9_4.3
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0848
  • Red Hat Enterprise Linux AppStream TUS (v.8.4) libsoup-devel 2.62.3-2.el8_4.2, libsoup-debuginfo 2.62.3-2.el8_4.2, libsoup-debugsource 2.62.3-2.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0889
  • Red Hat Enterprise Linux AppStream TUS (v.8.6) libsoup-devel 2.62.3-2.el8_6.2, libsoup-debuginfo 2.62.3-2.el8_6.2, libsoup-debugsource 2.62.3-2.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0949
  • Red Hat Enterprise Linux BaseOS (v. 8) libsoup 2.62.3-7.el8_10
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0838
  • Red Hat Enterprise Linux BaseOS AUS (v. 8.2) libsoup 2.62.3-1.el8_2.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0903
  • Red Hat Enterprise Linux BaseOS AUS (v.8.4) libsoup 2.62.3-2.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0889
  • Red Hat Enterprise Linux BaseOS AUS (v.8.6) libsoup 2.62.3-2.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0949
  • Red Hat Enterprise Linux BaseOS E4S (v.8.4) libsoup 2.62.3-2.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0889
  • Red Hat Enterprise Linux BaseOS E4S (v.8.6) libsoup 2.62.3-2.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0949
  • Red Hat Enterprise Linux BaseOS EUS (v.8.8) libsoup 2.62.3-3.el8_8.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:1075
  • Red Hat Enterprise Linux BaseOS TUS (v.8.4) libsoup 2.62.3-2.el8_4.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0889
  • Red Hat Enterprise Linux BaseOS TUS (v.8.6) libsoup 2.62.3-2.el8_6.2
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:0949
  • Red Hat Enterprise Linux Server (v. 7 ELS) libsoup 2.62.2-4.el7_9
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:1047
  • Red Hat RHINT Camel-K 1.10.9
    fixed: vendor fix “Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible.” RHSA-2025:1154
  • Red Hat Enterprise Linux AppStream AUS (v. 8.2) libsoup-devel 2.62.3-1.el8_2.2, libsoup-debuginfo 2.62.3-1.el8_2.2, libsoup-debugsource 2.62.3-1.el8_2.2 Red Hat Enterprise Linux BaseOS AUS (v. 8.2) libsoup-debuginfo 2.62.3-1.el8_2.2, libsoup-debugsource 2.62.3-1.el8_2.2
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.68% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • offsec.almond.consulting https://offsec.almond.consulting/using-aflplusplus-on-bug-bounty-programs-an-example-with-gnome-libsoup.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L
CISA ADP 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA 3.1 8.4 CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
julia Soup3_jll
all versions
 no fix listed

Affected products

  • GNOME libsoup

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.