Skip to content
OpenAdvisories

Package · Azure Linux

librsvg2

6 known vulnerabilities.

6 results · Feed

  • High 7.8
    CVE-2026-96889 Public exploit

    Librsvg: use-after-free when xml includes have duplicated entities

    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 …

  • Medium 6.8

    time affected by a stack exhaustion denial of service attack

    time provides date and time handling in Rust. From 0.3.6 to before 0.3.47, when user-provided input is provided to any type that parses with the RFC 2822 format, a denial of service attack via stack exhaustion is possible. The attack relies on formally deprec…

  • High 7.5
    CVE-2022-24713 Public exploit EPSS 14%

    Regular expression denial of service in Rust's regex crate

    regex is an implementation of regular expressions for the Rust language. The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations…

  • High 8.1

    Improper Restriction of Operations within the Bounds of a Memory Buffer and Race Condition in crossbeam-utils

    crossbeam-utils provides atomics, synchronization primitives, scoped threads, and other utilities for concurrent programming in Rust. crossbeam-utils prior to version 0.8.7 incorrectly assumed that the alignment of `{i,u}64` was always the same as `Atomic{I,U…

  • Critical 9.8

    Out of bounds write in nalgebra

    An issue was discovered in the nalgebra crate before 0.27.1 for Rust. It allows out-of-bounds memory access because it does not ensure that the number of elements is equal to the product of the row count and column count.

  • Critical 9.8

    Incorrect check on buffer length in rand_core

    An issue was discovered in the rand_core crate before 0.6.2 for Rust. Because read_u32_into and read_u64_into mishandle certain buffer-length checks, a random number generator may be seeded with too little data.