Vulnerabilities
Misconfiguration
Compliance
CVE Vulnerabilities

CVE-2025-49796

Out-of-bounds Read

Published: Jun 16, 2025 | Modified: Aug 07, 2025
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
RedHat/V2
RedHat/V3
9.1 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Ubuntu
MEDIUM
Vulnerability-free packages from our partners
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2025-49796
CWEhttps://cwe.mitre.org/data/definitions/125.html

A vulnerability was found in libxml2. Processing certain sch:name elements from the input XML file can trigger a memory corruption issue. This flaw allows an attacker to craft a malicious XML input file that can lead libxml to crash, resulting in a denial of service or other possible undefined behavior due to sensitive data being corrupted in memory.

Weakness

The product reads data past the end, or before the beginning, of the intended buffer.

Affected Software

Name Vendor Start Version End Version
Red Hat Enterprise Linux 10 RedHat libxml2-0:2.12.5-7.el10_0 *
Red Hat Enterprise Linux 7 Extended Lifecycle Support RedHat libxml2-0:2.9.1-6.el7_9.10 *
Red Hat Enterprise Linux 8 RedHat libxml2-0:2.9.7-21.el8_10.1 *
Red Hat Enterprise Linux 8 RedHat libxml2-0:2.9.7-21.el8_10.1 *
Red Hat Enterprise Linux 8.2 Advanced Update Support RedHat libxml2-0:2.9.7-9.el8_2.3 *
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support RedHat libxml2-0:2.9.7-9.el8_4.6 *
Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On RedHat libxml2-0:2.9.7-9.el8_4.6 *
Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support RedHat libxml2-0:2.9.7-13.el8_6.10 *
Red Hat Enterprise Linux 8.6 Telecommunications Update Service RedHat libxml2-0:2.9.7-13.el8_6.10 *
Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions RedHat libxml2-0:2.9.7-13.el8_6.10 *
Red Hat Enterprise Linux 8.8 Telecommunications Update Service RedHat libxml2-0:2.9.7-16.el8_8.9 *
Red Hat Enterprise Linux 8.8 Update Services for SAP Solutions RedHat libxml2-0:2.9.7-16.el8_8.9 *
Red Hat Enterprise Linux 9 RedHat libxml2-0:2.9.13-10.el9_6 *
Red Hat Enterprise Linux 9 RedHat libxml2-0:2.9.13-10.el9_6 *
Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions RedHat libxml2-0:2.9.13-1.el9_0.5 *
Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions RedHat libxml2-0:2.9.13-3.el9_2.7 *
Red Hat Enterprise Linux 9.4 Extended Update Support RedHat libxml2-0:2.9.13-10.el9_4 *
Red Hat Discovery 2 RedHat registry.redhat.io/discovery/discovery-server-rhel9:sha256:c517869dacaf4d3650310d4a52e83706e0b311d6ebb4a9b37b1c7acff5c142ec *
Red Hat Insights proxy 1.5 RedHat registry.redhat.io/insights-proxy/insights-proxy-container-rhel9:sha256:e54a5a5f9d69dd6a03e2bcd845e2202910a188d266d4a79b12c387ceffc36f2d *
Libxml2 Ubuntu esm-infra-legacy/trusty *
Libxml2 Ubuntu esm-infra/bionic *
Libxml2 Ubuntu esm-infra/focal *
Libxml2 Ubuntu esm-infra/xenial *
Libxml2 Ubuntu jammy *
Libxml2 Ubuntu noble *
Libxml2 Ubuntu oracular *
Libxml2 Ubuntu plucky *
Libxml2 Ubuntu upstream *

Potential Mitigations

  • Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
  • To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.

References

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2025 Aqua Security Software Ltd.   Privacy Policy | Terms of Use