# CVE-2026-96889: Librsvg: use-after-free when xml includes have duplicated entities > An attacker can trigger a use-after-free in librsvg via crafted SVG files, potentially leading to arbitrary code execution or denial of service. - **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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:** 23 Sep 2026 - **Updated:** 29 Oct 2026 - **Also known as:** ALSA-2026:86331, ALSA-2026:86841, ALSA-2026:86842, ALSA-2026:86921, AZL-104931, BELL-CVE-2026-96889, CLEANSTART-2026-OL77428, DEBIAN-CVE-2026-96889, ECHO-1749-9813-10f2, GHSA-cpvr-w4j5-2mpg, OESA-2026-4262, OESA-2026-4263, OESA-2026-4264, OESA-2026-4265, RLSA-2026:86331, RLSA-2026:86841, RLSA-2026:86842, RLSA-2026:86921, ROOT-OS-DEBIAN-12-CVE-2026-96889, RUSTSEC-2026-0305, SUSE-SU-2026:24117-1, SUSE-SU-2026:24202-1, UBUNTU-CVE-2026-96889, USN-8891-1, openSUSE-SU-2026:22051-1 ## What is CVE-2026-96889? CVE-2026-96889 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 23 Sep 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 librsvg. When processing an SVG document containing nested XML inclusions (Xincludes) with duplicate entity declarations, a use-after-free error can occur. This vulnerability arises because the library incorrectly frees an XML entity that is still in use by the parser. An attacker could potentially exploit this to cause a denial of service or execute arbitrary code. Weakness: CWE-416 (Use After Free) ## Which versions are affected by CVE-2026-96889? 11 open source packages ship an affected version, including librsvg. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `librsvg` | crates.io | All versions | 2.57.5 | | `librsvg` | crates.io | All versions | 2.57.5 | | `librsvg` | crates.io | From 0.0.0-0 | 2.57.5, 2.60.3, 2.61.5, 2.62.4, 2.63.2 | | `librsvg` | crates.io | From 2.60.0-beta.0 | 2.60.3 | | `librsvg` | crates.io | From 2.60.0-beta.0 | 2.60.3 | | `librsvg` | crates.io | From 2.61.0 | 2.61.5 | | `librsvg` | crates.io | From 2.61.0 | 2.61.5 | | `librsvg` | crates.io | From 2.62.0-beta.0 | 2.62.4 | | `librsvg` | crates.io | From 2.62.0-beta.0 | 2.62.4 | | `librsvg` | crates.io | From 2.63.0-beta.0 | 2.63.2 | | `librsvg` | crates.io | From 2.63.0-beta.0 | 2.63.2 | | `glycin-loaders` | AlmaLinux:10 | All versions | 1.0.1-1.el10_2.2 | | `librsvg2` | AlmaLinux:10 | All versions | 2.57.1-9.el10_2.10 | | `librsvg2-devel` | AlmaLinux:10 | All versions | 2.57.1-9.el10_2.10 | | `librsvg2-tools` | AlmaLinux:10 | All versions | 2.57.1-9.el10_2.10 | | `rsvg-pixbuf-loader` | AlmaLinux:10 | All versions | 2.57.1-9.el10_2.10 | | `librsvg2` | AlmaLinux:8 | All versions | 2.42.7-6.el8_10 | | `librsvg2-devel` | AlmaLinux:8 | All versions | 2.42.7-6.el8_10 | | `librsvg2-tools` | AlmaLinux:8 | All versions | 2.42.7-6.el8_10 | | `librsvg2` | AlmaLinux:9 | All versions | 2.50.7-3.el9_8.1 | | `librsvg2-devel` | AlmaLinux:9 | All versions | 2.50.7-3.el9_8.1 | | `librsvg2-tools` | AlmaLinux:9 | All versions | 2.50.7-3.el9_8.1 | | `glycin-loaders` | Rocky Linux:10 | All versions | 0:1.0.1-1.el10_2.2 | | `librsvg2` | Rocky Linux:10 | All versions | 0:2.57.1-9.el10_2.10 | | `librsvg2` | Rocky Linux:8 | All versions | 0:2.42.7-6.el8_10 | | `librsvg2` | Rocky Linux:9 | All versions | 0:2.50.7-3.el9_8.1 | | `librsvg` | SUSE:Linux Enterprise Server 16.0 | All versions | 2.60.3-160000.1.1 | | `librsvg` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 2.60.3-160000.1.1 | | `librsvg` | SUSE:Linux Micro 6.2 | All versions | 2.60.3-160000.1.1 | | `librsvg` | openSUSE:Leap 16.0 | All versions | 2.60.3-160000.1.1 | ## How do I fix CVE-2026-96889? Upgrade librsvg to a fixed version for your release line: 2.57.5, 2.60.3, 2.61.5 or 2.62.4. ## Is CVE-2026-96889 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-96889 exists. Public exploit code: - This repository documents the VectorFreed RCE chain and includes a PoC for CVE-2026-96889. (github_poc): https://github.com/rafabd1/VectorFreed - Lab PoC for CVE-2026-96889: Next.js Image Optimization SVG typed as AVIF reaches librsvg UAF (RUSTSEC-2026-0305). Unauthenticated RCE on glibc Linux. (github_poc): https://github.com/lion9453/CVE-2026-96889-nextjs-rce - Projet de Cybersécurité (TP1 à TP9) Recherche réseau (Nmap, Scapy) • Attaques DDoS (hping3) • Force brute (Hydra, LaZagne) • Ingénierie sociale (Zphisher, Gophish) • Sécurité Wi-Fi (Airgeddon, Aircrack-ng) • Malwares (msfvenom) • Injection de code (Shellter) • MITM (Ettercap, Yersinia) • Vulnérabilités (CVE-2026-96889). (github_poc): https://github.com/pauleprichna/cybersecurity - Check a Next.js project against the October 14, 2026 security advisories (CVE-2026-96889, use cache RCE, Server Actions DoS). No dependencies. (github_poc): https://github.com/AmanSin001/next-security-check - Offline Sharp / librsvg evidence checker for CVE-2026-96889. Sharp and librsvg version and build evidence. Standalone Python; JSON/CSV/HTML reports; no exploit payloads. (github_poc): https://github.com/CompleteTech-Security/sharp-vectorfreed-check ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-96889 and fix it if it is affected. What it is: CVE-2026-96889 is a high-severity use after free vulnerability in Red Hat Enterprise Linux 10, published on 23 Sep 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-96889 exists. Affected packages and fixed versions: - librsvg (crates.io): affected all versions; fixed in 2.57.5 - librsvg (crates.io): affected all versions; fixed in 2.57.5 - librsvg (crates.io): affected from 0.0.0-0; fixed in 2.57.5, 2.60.3, 2.61.5, 2.62.4, 2.63.2 - librsvg (crates.io): affected from 2.60.0-beta.0; fixed in 2.60.3 - librsvg (crates.io): affected from 2.60.0-beta.0; fixed in 2.60.3 - librsvg (crates.io): affected from 2.61.0; fixed in 2.61.5 - librsvg (crates.io): affected from 2.61.0; fixed in 2.61.5 - librsvg (crates.io): affected from 2.62.0-beta.0; fixed in 2.62.4 - librsvg (crates.io): affected from 2.62.0-beta.0; fixed in 2.62.4 - librsvg (crates.io): affected from 2.63.0-beta.0; fixed in 2.63.2 - librsvg (crates.io): affected from 2.63.0-beta.0; fixed in 2.63.2 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-96889/ (Markdown: https://insights.sbomify.com/CVE-2026-96889/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-96889 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-96889 - OSV: https://osv.dev/vulnerability/CVE-2026-96889 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-96889/ Summaries are generated and may contain mistakes; the official description above is the record.