CVE-2026-0719VulnerabilityPublished 5 Feb 2026Updated 27 Jun 2026

Red Hat Security Advisory: libsoup security update

Affects Red Hat libsoupSource GCVE Database

Mentioned vulnerabilities

CVE-2026-1761

Authoritative record:CVE-2026-0719· High 8.6

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 09:16 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Red Hatredhat/libsoup`pkg:rpm/redhat/libsoup`Other threats	Affected =2.72.0 =2.72.0-8.el9_0.9	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released updated libsoup packages (version 2.72.0-8.el9_0.9) that fix these vulnerabilities. Users of affected Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions should apply the available security updates promptly. Refer to the Red Hat article https://access.redhat.com/articles/11258 for detailed update instructions. No additional mitigation actions are indicated by the vendor advisory.

Description

Two security vulnerabilities have been identified in the libsoup HTTP client and server library used in GNOME, affecting Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions. The first vulnerability (CVE-2026-0719) involves a signed to unsigned conversion error that leads to a stack-based buffer overflow in libsoup NTLM authentication. The second vulnerability (CVE-2026-1761) is a stack-based buffer overflow in libsoup multipart response parsing. Red Hat has released security updates addressing these issues in libsoup version 2.72.0-8.el9_0.9 for multiple architectures. These vulnerabilities are rated as having a high security impact by Red Hat. No known exploits in the wild have been reported at this time.

Impact

Successful exploitation of these vulnerabilities could result in stack-based buffer overflows, which may lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a denial of service. The vulnerabilities affect the libsoup library used in HTTP client and server operations, including NTLM authentication and multipart response parsing. No public exploits are currently known.

CWE-121Stack-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #14
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Implementation
Implement and perform bounds checking on input.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Jun 2026, 00:23 UTC

WeaknessesCWE-121

Technical details

References

Community reviews

Related threats