Skip to main content
VulnerabilityPublished Updated

CVE-2026-102555: Red Hat Enterprise Linux 10 · Out-of-bounds Read

Affects Red Hat Enterprise Linux 10Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High.

Data as of 13 Nov 2026, 12:10 UTC

CVSS 3.1 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.18.2
EPSS
0.4% chance of exploitation in 30 days – higher than 41% 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:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Enterprise Linux 10libsoup3Affected–Fixed in–
Red Hat Enterprise Linux 10libsoup3Affected–Fixed in–
Red Hat Enterprise Linux 10.0 Extended Update Supportlibsoup3Affected–Fixed in–
Red Hat Enterprise Linux 6libsoupAffected–Fixed in–
Red Hat Enterprise Linux 7libsoupAffected–Fixed in–
Red Hat Enterprise Linux 8libsoupAffected–Fixed in–

AI-suggested

Red Hat advises not to pass untrusted data URIs to the soup_uri_decode_data_uri() function to mitigate this vulnerability. There is no explicit mention of an official patch or fixed version in the advisory content provided.

Description

A flaw was found in libsoup. The soup_uri_decode_data_uri() function incorrectly treated base64 data-URI payloads as NUL-terminated strings when calling g_base64_decode_inplace(). If the percent-decoded payload contained embedded NUL bytes, the decoded length could remain uninitialized and be used as the size of the returned GBytes. This can lead to an out-of-bounds read or application crash when processing a crafted data URI.

References

Community reviews

Loading reviews…