CVE-2026-2369: Libsoup: libsoup: buffer overread due to integer underflow when handling zero-length resources

Published Feb 11, 2026
·
Updated

A flaw was found in libsoup. An integer underflow vulnerability occurs when processing content with a zero-length resource, leading to a buffer overread. This can allow an attacker to potentially access sensitive information or cause an application level denial of service.

Other sources

Integer underflow in CVE-2025-32052 fix when resourcelength=0

The fix for CVE-2025-32052 (commit a5b86bfc) introduces a potential integer underflow vulnerability when resourcelength is 0.

Affected Code: libsoup/soup-content-sniffer.c, line 507

Issue: The patch changes the condition from: while ((indexstream < resourcelength) && ...) to: while ((indexstream < resourcelength - 1) && ...)

When buffer->length = 0:

resourcelength = MIN(512, 0) = 0 resourcelength - 1 underflows to UINTMAX (gsize is unsigned) Condition (0 < UINTMAX) = TRUE Loop executes on empty buffer → buffer overread Fix: Add guard before hasws path: if (resourcelength == 0) continue;

This matches the pattern used in the else branch which already checks: if (resourcelength < typerow->patternlength) continue;

Patch :

--- a/libsoup/soup-content-sniffer.c +++ b/libsoup/soup-content-sniffer.c @@ -498,6 +498,11 @@ sniffunknown (SoupContentSniffer sniffer, SoupBuffer buffer, if (!sniffscriptable && typerow->scriptable) continue; + / Ensure we have data to sniff - prevents underflow in resourcelength - 1 / + if (resourcelength == 0) + continue; + if (typerow->hasws) { guint indexstream = 0; guint indexpattern = 0;

Red Hat

Libsoup: libsoup: buffer overread due to integer underflow when handling zero-length resources

Microsoft

Affected Software

7 affected componentsFixes available
Gnome libsoup
Microsoft azl3 libsoup 3.4.4-12
Microsoft azl3 libsoup 3.4.4-14
Microsoft cbl2 libsoup 3.0.4-13
debian/libsoup2.4<=2.72.0-2, <=2.72.0-2+deb11u3, <=2.74.3-1+deb12u1, <=2.74.3-10.1
debian/libsoup3<=3.2.3-0+deb12u2, <=3.6.5-3
3.6.6-1
Gnome libsoup

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 3.6.6-1
  2. Configuration

    Apply the guard in libsoup/soup-content-sniffer.c (sniff_unknown): before entering the has_ws path, add `if (resource_length == 0) continue;` to prevent the `resource_length - 1` unsigned underflow (CVE-2025-32052).

    libsoup (soup-content-sniffer.c) resource_length guard in sniff_unknown (has_ws path) = if (resource_length == 0) continue;

Event History

Feb 11, 2026
Data Sourced
via Red Hat·08:23 PM
DescriptionSeverityAffected Software
Mar 19, 2026
CVE Published
via MITRE·02:20 PM
Data Sourced
via MITRE·02:20 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
RemedyAffected Software
Mar 25, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
Affected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Jul 9, 2026
Data Sourced
via Ubuntu·08:52 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·08:53 PM
DescriptionAffected Software
Data Sourced
via Launchpad·08:54 PM
Description
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-2026-2369?

CVE-2026-2369 is rated as a medium severity vulnerability due to its potential for buffer overread.

2

How do I fix CVE-2026-2369?

To mitigate CVE-2026-2369, ensure that you update to the latest version of libsoup that addresses this integer underflow vulnerability.

3

What type of systems are affected by CVE-2026-2369?

CVE-2026-2369 primarily affects systems using the GNOME libsoup library.

4

What can an attacker potentially do with CVE-2026-2369?

An attacker could potentially leverage CVE-2026-2369 to access sensitive memory content through buffer overreads.

5

Is there a workaround for CVE-2026-2369?

Currently, the most effective action against CVE-2026-2369 is to apply the relevant security patches provided by the vendor.

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