# CVE-2026-44605: Rpm: heap buffer overflow in ndb slot table parsing > A local attacker can cause a denial of service via heap buffer overflow in RPM's NDB database parsing, affecting Linux distributions. - **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 5 Aug 2026 - **Updated:** 16 Oct 2026 - **Also known as:** AZL-94665, DEBIAN-CVE-2026-44605, ECHO-2a56-4b8c-bc8e, GHSA-jgh7-mh2q-3476, OESA-2026-3099, RHSA-2026:33507, SUSE-SU-2026:23192-1, SUSE-SU-2026:23204-1, SUSE-SU-2026:3600-1, SUSE-SU-2026:4457-1, UBUNTU-CVE-2026-44605 ## What is CVE-2026-44605? CVE-2026-44605 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description A flaw was found in the RPM Package Manager (RPM). A local user could be affected by a heap buffer overflow vulnerability when processing a specially crafted NDB database file. This issue arises from an error in how RPM handles certain calculations during file parsing, leading to an incorrect memory allocation. An attacker could leverage this to cause a denial of service, making the system unavailable. Weakness: CWE-190 (Integer Overflow or Wraparound) ## Which versions are affected by CVE-2026-44605? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `python3-rpm` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-apidocs` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-build` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-build-libs` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-cron` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-devel` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-libs` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-audit` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-dbus-announce` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-fapolicyd` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-fsverity` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-ima` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-prioreset` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-selinux` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-syslog` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-systemd-inhibit` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-plugin-unshare` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-sign` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `rpm-sign-libs` | Red Hat:hummingbird:1 | All versions | 0:6.0.1-6.2.hum1 | | `python-rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 4.14.3-150400.59.19.1 | | `python-rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 4.14.3-150400.59.19.1 | | `python-rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-ESPOS | All versions | 4.14.3-150400.59.19.1 | | `python-rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise High Performance Computing 15 SP5-LTSS | All versions | 4.14.3-150400.59.19.1 | | `python-rpm` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.14.3-150300.58.1 | | `rpm` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.14.3-150300.58.1 | | `rpm-ndb` | SUSE:Linux Enterprise Micro 5.3 | All versions | 4.14.3-150300.58.1 | | `python-rpm` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.14.3-150400.59.19.1 | | `rpm-ndb` | SUSE:Linux Enterprise Micro 5.4 | All versions | 4.14.3-150400.59.19.1 | | `python-rpm` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.14.3-150400.59.19.1 | | `rpm-ndb` | SUSE:Linux Enterprise Micro 5.5 | All versions | 4.14.3-150400.59.19.1 | | `python-rpm` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 4.14.3-150400.59.19.1 | | `rpm` | SUSE:Linux Enterprise Module for Development Tools 15 SP7 | All versions | 4.14.3-150400.59.19.1 | ## How do I fix CVE-2026-44605? Apply the vendor's patch. ## Is CVE-2026-44605 being exploited? There is no known exploitation of CVE-2026-44605 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-44605 and fix it if it is affected. What it is: CVE-2026-44605 is a medium-severity memory corruption vulnerability in Red Hat Enterprise Linux 10, published on 5 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2026-44605 in the wild and no public exploit code. Affected product: Red Hat Enterprise Linux 10. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-44605/ (Markdown: https://insights.sbomify.com/CVE-2026-44605/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44605 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44605 - OSV: https://osv.dev/vulnerability/CVE-2026-44605 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-44605/ Summaries are generated and may contain mistakes; the official description above is the record.