Vulnerabilities

100 via 228 paths

Dependencies

87

Source

Group 6 Copy Created with Sketch. Docker

Target OS

debian:13
Test your Docker Hub image against our market leading vulnerability database Sign up for free
Severity
  • 4
  • 3
  • 93
Status
  • 100
  • 0
  • 0

high severity
new

Directory Traversal

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1
  • Fixed in: 1:1.3.dfsg+really1.3.1-1+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

webpack-dev-middleware 5.3.4, 6.1.2 through 6.1.3, 7.1.0 before 7.4.6, and 8.0.0 before 8.3.0 contains a path traversal vulnerability in getFilenameFromUrl that bypasses the fix for CVE-2024-29180: a publicPath without a trailing slash is matched by string prefix, and the '..' guard runs before that prefix is stripped. Unauthenticated attackers can request a path such as /assets../secret to read files one directory above the output directory when the middleware serves from the physical filesystem through writeToDisk or a custom outputFileSystem.

Remediation

Upgrade Debian:13 zlib to version 1:1.3.dfsg+really1.3.1-1+deb13u1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1
  • Fixed in: 1:1.3.dfsg+really1.3.1-1+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

zlib 1.2.11 through 1.3.2 contains a heap buffer overflow: after an underlying write() fails, gz_write() returns without resetting strm.next_in, leaving it pointed at the caller's buffer. A later gz* write call then derives a position from the stale pointer and writes past a heap allocation; any write() failure reaches it, including EPIPE on a blocking descriptor, and in versions before 1.3.1.2 the failed write must be followed by a gzclearerr() call.

Remediation

Upgrade Debian:13 zlib to version 1:1.3.dfsg+really1.3.1-1+deb13u1 or higher.

References

high severity

Link Following

  • Vulnerable module: acl/libacl1
  • Introduced through: acl/libacl1@2.3.2-2+b1

Detailed paths

  • Introduced through: python@3.11-slim › acl/libacl1@2.3.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream acl package and not the acl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

acl before version 2.4.0 contains a symlink traversal vulnerability in the libacl pathname-based functions acl_get_file(), acl_set_file(), acl_extended_file(), and acl_delete_def_file() that allows local attackers to escalate privileges by replacing any pathname component with a symbolic link. Attackers who control any component of a pathname processed by a privileged caller can redirect ACL read or write operations to arbitrary files or directories, enabling unauthorized manipulation of access control lists and local privilege escalation.

Remediation

There is no fixed version for Debian:13 acl.

References

high severity

Link Following

  • Vulnerable module: attr/libattr1
  • Introduced through: attr/libattr1@1:2.5.2-3

Detailed paths

  • Introduced through: python@3.11-slim › attr/libattr1@1:2.5.2-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream attr package and not the attr package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

attr before version 2.6.0 contains a symlink traversal vulnerability in the getfattr and setfattr utilities that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link during directory hierarchy traversal. Attackers who control a pathname component can redirect getfattr and setfattr operations to arbitrary files by substituting a symlink, leading to local privilege escalation when getfattr or setfattr is invoked by a privileged process over an attacker-controlled path.

Remediation

There is no fixed version for Debian:13 attr.

References

medium severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: acl/libacl1
  • Introduced through: acl/libacl1@2.3.2-2+b1

Detailed paths

  • Introduced through: python@3.11-slim › acl/libacl1@2.3.2-2+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream acl package and not the acl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

acl before version 2.4.0 contains a time-of-check to time-of-use (TOCTOU) race condition vulnerability that allows local attackers to escalate privileges by replacing a pathname component with a symbolic link between an lstat() check and subsequent symlink-following operations such as stat(), chown(), chmod(), acl_get_file(), and acl_set_file(). Attackers who control a pathname component can redirect file access control list operations to arbitrary files when getfacl, setfacl, or chacl is invoked by a privileged process over an attacker-controlled path, resulting in local privilege escalation.

Remediation

There is no fixed version for Debian:13 acl.

References

medium severity

Improper Validation of Specified Quantity in Input

  • Vulnerable module: zlib/zlib1g
  • Introduced through: zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1
  • Fixed in: 1:1.3.dfsg+really1.3.1-1+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › zlib/zlib1g@1:1.3.dfsg+really1.3.1-1+b1

NVD Description

Note: Versions mentioned in the description apply only to the upstream zlib package and not the zlib package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

zlib before 1.3.2 allows CPU consumption via crc32_combine64 and crc32_combine_gen64 because x2nmodp can do right shifts within a loop that has no termination condition.

Remediation

Upgrade Debian:13 zlib to version 1:1.3.dfsg+really1.3.1-1+deb13u1 or higher.

References

medium severity
new

Out-of-bounds Write

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in libstdc++. When a byte-by-byte write operation fails during file stream processing, the library may still append data into the internal memory buffer. An attacker capable of inducing repeated write failures in an affected service can trigger a buffer overflow, potentially resulting in a Denial of Service (DoS) or memory corruption.

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2005-2541

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: python@3.11-slim › tar@1.35+dfsg-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Missing Release of File Descriptor or Handle after Effective Lifetime

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41.5-0+deb13u1, util-linux/bsdutils@1:2.41.5-0+deb13u1 and others

Detailed paths

  • Introduced through: python@3.11-slim › util-linux@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/bsdutils@1:2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libblkid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/liblastlog2-2@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libmount1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libsmartcols1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libuuid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/login@1:4.16.0-2+really2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/mount@2.41.5-0+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The nsenter --join-cgroup option opens the target cgroup.procs file as root and leaves that file descriptor open across later namespace and credential changes and across execve(). Because the kernel checks later cgroup migrations using the credentials from the original open, a program run in an attacker-controlled target can inherit root's ability to move host processes between cgroups. After a privileged operator uses --join-cgroup against that target, an unprivileged user can migrate and terminate unrelated root processes.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity

Stack-based Buffer Overflow

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.5+20250216-2, ncurses/libtinfo6@6.5+20250216-2 and others

Detailed paths

  • Introduced through: python@3.11-slim › ncurses/libncursesw6@6.5+20250216-2
  • Introduced through: python@3.11-slim › ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: python@3.11-slim › ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: python@3.11-slim › ncurses/ncurses-bin@6.5+20250216-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The infocmp command-line tool in ncurses before 6.5-20251213 has a stack-based buffer overflow in analyze_string in progs/infocmp.c.

Remediation

There is no fixed version for Debian:13 ncurses.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

Detection of Error Condition Without Action

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41.5-0+deb13u1, util-linux/bsdutils@1:2.41.5-0+deb13u1 and others

Detailed paths

  • Introduced through: python@3.11-slim › util-linux@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/bsdutils@1:2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libblkid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/liblastlog2-2@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libmount1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libsmartcols1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libuuid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/login@1:4.16.0-2+really2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/mount@2.41.5-0+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

util-linux versions through 2.41.5 and 2.42.2 fail to check mount helper exit status before running post-mount hooks, allowing unprivileged users to execute privileged operations on pre-existing filesystems. Attackers can exploit X-mount.idmap or X-mount.owner hooks to clone filesystems with inherited suid bits or modify target inode permissions after a helper fails, achieving privilege escalation.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41.5-0+deb13u1, util-linux/bsdutils@1:2.41.5-0+deb13u1 and others

Detailed paths

  • Introduced through: python@3.11-slim › util-linux@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/bsdutils@1:2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libblkid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/liblastlog2-2@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libmount1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libsmartcols1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libuuid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/login@1:4.16.0-2+really2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/mount@2.41.5-0+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in util-linux. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in libstdc++. An integer overflow can occur when processing large inputs to the aligned operator new in the C++ library. This vulnerability could lead to an undersized memory allocation, potentially causing memory corruption or application instability.

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-9538

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.40.1-6+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › perl/perl-base@5.40.1-6+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Archive::Tar versions before 3.10 for Perl allow memory exhaustion via attacker controlled entry size field in tar header.

_read_tar() reads each entry's payload with $handle->read($$data, $block), where $block is derived from the entry's 12-byte size field in the tar header with no upper bound on that value.

A crafted header declaring a multi-gigabyte size causes Perl to allocate a scalar of that size.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

Expired Pointer Dereference

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in GCC. When an application calls the erase_if function on a binary heap priority queue in libstdc++, the library reallocates storage but fails to update its internal entry pointer. An attacker capable of triggering this operation can exploit this use-after-free condition, leading to a Denial of Service (DoS) via an application crash or potential memory corruption.

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity

Link Following

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41.5-0+deb13u1, util-linux/bsdutils@1:2.41.5-0+deb13u1 and others

Detailed paths

  • Introduced through: python@3.11-slim › util-linux@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/bsdutils@1:2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libblkid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/liblastlog2-2@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libmount1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libsmartcols1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libuuid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/login@1:4.16.0-2+really2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/mount@2.41.5-0+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The X-mount.subdir option uses a detached-tree fast path on Linux 6.15 and later and passes the configured subdirectory to open_tree() with AT_SYMLINK_NOFOLLOW. That flag does not stop intermediate symlink traversal or keep resolution inside the newly mounted filesystem. A local unprivileged user with an fstab-authorized X-mount.subdir entry can attach a host path at the intended mountpoint.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in GCC libstdc++. When an application extracts data into a bitset from a wide-character stream, internal stack memory allocation fails to properly account for character size and alignment. An attacker capable of supplying crafted input to an affected application could trigger a stack-based buffer overflow leading denial of service (DoS).

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in GCC. An out-of-bounds memory access vulnerability exists in the libstdc++ parallel search implementation due to an undersized internal buffer. A local attacker can exploit this flaw by providing crafted search data to an application compiled with parallel mode, causing the process to crash and leading to a Denial of Service (DoS).

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity

Access Restriction Bypass

  • Vulnerable module: shadow/login.defs
  • Introduced through: shadow/login.defs@1:4.17.4-2 and shadow/passwd@1:4.17.4-2

Detailed paths

  • Introduced through: python@3.11-slim › shadow/login.defs@1:4.17.4-2
  • Introduced through: python@3.11-slim › shadow/passwd@1:4.17.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.

Remediation

There is no fixed version for Debian:13 shadow.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.7-3

Detailed paths

  • Introduced through: python@3.11-slim › coreutils@9.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

GNU coreutils unexpand is vulnerable to a heap-based buffer overflow due to an integer overflow during buffer allocation when processing large tab stop (-t) values. The multiplication used to calculate the allocation size can wrap around, resulting in an undersized buffer. When processing crafted input, subsequent writes exceed the allocated memory, leading to an out‑of‑bounds heap write.

When running GNU coreutils unexpand with attacker-provided large tab stop (-t) arguments, this behavior leads to a crash and potentially achieve a heap write primitive depending on memory layout.

This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.7-3

Detailed paths

  • Introduced through: python@3.11-slim › coreutils@9.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

GNU coreutils uniq is vulnerable to an out‑of‑bounds read due to incorrect handling of multibyte input when the -w (--check-chars) option is used. The find_field() function miscalculates the byte length of characters by repeatedly processing a fixed pointer instead of advancing through the input, resulting in an inflated length value. This incorrect length is later used in a memcmp operation, causing reads beyond the allocated buffer when processing crafted multibyte input.

When running GNU coreutils uniq with attacker-provided arguments, this behavior leads to a crash and potential adjacent heap memory exposure.

This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371.

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity
new

Integer Overflow or Wraparound

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in the libstdc++ component of GCC. An attacker who can provide an excessively large element count to a boolean vector (std::vector<bool>) constructor can trigger an integer wrap during internal memory calculations. This issue leaves the container in an inconsistent state, leading to out-of-bounds memory access and resulting in an application crash or a Denial of Service (DoS) during subsequent operations.

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity

Inefficient Regular Expression Complexity

  • Vulnerable module: dash
  • Introduced through: dash@0.5.12-12

Detailed paths

  • Introduced through: python@3.11-slim › dash@0.5.12-12

NVD Description

Note: Versions mentioned in the description apply only to the upstream dash package and not the dash package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in dash. When built without libc fnmatch, the internal pmatch() matcher implements * by unbounded recursion over candidate positions. A local user who can plant filenames, or otherwise feed that matcher, can make a short multi-star pattern such as ....*.tar.gz consume excessive CPU.

Remediation

There is no fixed version for Debian:13 dash.

References

low severity
new

Uncontrolled Recursion

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH nesting limit because common table expressions are not counted against it. Attackers can supply a WITH clause chaining tens of thousands of CTEs, via plain SQL or a view in an untrusted database file, causing unbounded selectExpander() recursion that crashes the process.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Uncontrolled Recursion

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 contains a stack exhaustion vulnerability in countOfViewOptimization() that allows attackers to crash the host process via count(*) over a large multi-row VALUES clause. Attackers supplying SQL or a database file with a crafted view can trigger deeply nested TK_PLUS expressions whose recursive freeing in sqlite3ExprDeleteNN() exhausts the C stack, causing denial of service.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Uncontrolled Recursion

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators. Attackers can supply roughly 175,000 chained COLLATE operators in SQL or an untrusted database view to trigger unbounded recursion in sqlite3WalkExprNN() and crash the process.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap memory and crash the process.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Use After Free

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 contains a use-after-free vulnerability in the R-Tree extension that allows attackers to make applications use freed heap memory by manipulating the %_node shadow table. Attackers can supply a database declaring %_node WITHOUT ROWID or with a RAISE(IGNORE) trigger so nodeWrite() hashes nodes as 0, crashing the process after node splits.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity
new

Use of Uninitialized Resource

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 contains an information disclosure vulnerability that allows attackers to read uninitialized page-cache memory by supplying a WAL file with an undersized page size. Attackers can craft a database and WAL file whose oversized record payload makes queries like substr() return stale bytes, disclosing other table rows and internal pointers.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

Unrestricted Upload of File with Dangerous Type

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: python@3.11-slim › tar@1.35+dfsg-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in tar. A remote attacker could exploit this vulnerability by crafting a malicious archive, leading to hidden file injection with fully attacker-controlled content. This bypasses pre-extraction inspection mechanisms, potentially allowing an attacker to introduce malicious files onto a system without detection.

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41.5-0+deb13u1, util-linux/bsdutils@1:2.41.5-0+deb13u1 and others

Detailed paths

  • Introduced through: python@3.11-slim › util-linux@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/bsdutils@1:2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libblkid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/liblastlog2-2@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libmount1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libsmartcols1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libuuid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/login@1:4.16.0-2+really2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/mount@2.41.5-0+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Improper Validation of Integrity Check Value

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Authentication Bypass

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41.5-0+deb13u1, util-linux/bsdutils@1:2.41.5-0+deb13u1 and others

Detailed paths

  • Introduced through: python@3.11-slim › util-linux@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/bsdutils@1:2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libblkid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/liblastlog2-2@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libmount1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libsmartcols1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/libuuid1@2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/login@1:4.16.0-2+really2.41.5-0+deb13u1
  • Introduced through: python@3.11-slim › util-linux/mount@2.41.5-0+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream util-linux package and not the util-linux package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in util-linux. Improper hostname canonicalization in the login(1) utility, when invoked with the -h option, can modify the supplied remote hostname before setting PAM_RHOST. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.

Remediation

There is no fixed version for Debian:13 util-linux.

References

low severity

Race Condition

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.7-3

Detailed paths

  • Introduced through: python@3.11-slim › coreutils@9.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity

Stack-based Buffer Overflow

  • Vulnerable module: coreutils
  • Introduced through: coreutils@9.7-3

Detailed paths

  • Introduced through: python@3.11-slim › coreutils@9.7-3

NVD Description

Note: Versions mentioned in the description apply only to the upstream coreutils package and not the coreutils package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity

Link Following

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Link Following

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: python@3.11-slim › tar@1.35+dfsg-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in GNU tar. When extracting an archive with the --one-top-level option, hardlink targets are not confined to the designated top-level directory and may resolve relative to the extraction working directory. A crafted archive can create hardlinks that escape the intended boundary and, when combined with a preexisting symbolic link under the working directory, may allow writing outside that boundary during a single extraction.

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

Time-of-check Time-of-use (TOCTOU)

  • Vulnerable module: tar
  • Introduced through: tar@1.35+dfsg-3.1

Detailed paths

  • Introduced through: python@3.11-slim › tar@1.35+dfsg-3.1

NVD Description

Note: Versions mentioned in the description apply only to the upstream tar package and not the tar package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A TOCTOU (Time-of-Check Time-of-Use) vulnerability in GNU tar's incremental dumpdir 'X' rename handling allows a local attacker with write access to a directory being backed up to influence the restore process if the attacker has access to the system where the restore is being performed. During restoration, files or directories may be created, renamed or overwritten outside the intended extraction directory. This could lead to unauthorized file modification or, in some cases, privilege escalation. Exploitation does not require the attacker to modify or craft the archive, and standard backup and restore workflows—including extracting into a newly created directory without using the -P option do not mitigate the issue.

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Memory Leak

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A Memory Leak vulnerability exists in SQLite Project SQLite3 3.35.1 and 3.37.0 via maliciously crafted SQL Queries (made via editing the Database File), it is possible to query a record, and leak subsequent bytes of memory that extend beyond the record, which could let a malicious user obtain sensitive information. NOTE: The developer disputes this as a vulnerability stating that If you give SQLite a corrupted database file and submit a query against the database, it might read parts of the database that you did not intend or expect.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

Out-of-bounds Write

  • Vulnerable module: dash
  • Introduced through: dash@0.5.12-12

Detailed paths

  • Introduced through: python@3.11-slim › dash@0.5.12-12

NVD Description

Note: Versions mentioned in the description apply only to the upstream dash package and not the dash package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in dash. The printf builtin reserves four bytes before converting a Unicode \u or \U escape, but the multi-byte token can need five or six bytes. A local user who can supply such an escape to dash printf or echo %b, including through dash -c and a positional argument, can write one or two bytes past that reservation.

Remediation

There is no fixed version for Debian:13 dash.

References

low severity

Improper Verification of Cryptographic Signature

  • Vulnerable module: apt
  • Introduced through: apt@3.0.4 and apt/libapt-pkg7.0@3.0.4

Detailed paths

  • Introduced through: python@3.11-slim › apt@3.0.4
  • Introduced through: python@3.11-slim › apt/libapt-pkg7.0@3.0.4

NVD Description

Note: Versions mentioned in the description apply only to the upstream apt package and not the apt package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.

Remediation

There is no fixed version for Debian:13 apt.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: gcc-14/gcc-14-base
  • Introduced through: gcc-14/gcc-14-base@14.2.0-19, gcc-14/libgcc-s1@14.2.0-19 and others

Detailed paths

  • Introduced through: python@3.11-slim › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: python@3.11-slim › gcc-14/libstdc++6@14.2.0-19

NVD Description

Note: Versions mentioned in the description apply only to the upstream gcc-14 package and not the gcc-14 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A flaw was found in gcc. An attacker could cause a Denial of Service (DoS) by passing a string that is not null-terminated to the std::from_chars() function in the libstdc++ library. This issue triggers an out-of-bounds read beyond the allocated buffer, potentially leading to invalid data parsing or an application crash.

Remediation

There is no fixed version for Debian:13 gcc-14.

References

low severity

Out-of-Bounds

  • Vulnerable module: ncurses/libncursesw6
  • Introduced through: ncurses/libncursesw6@6.5+20250216-2, ncurses/libtinfo6@6.5+20250216-2 and others

Detailed paths

  • Introduced through: python@3.11-slim › ncurses/libncursesw6@6.5+20250216-2
  • Introduced through: python@3.11-slim › ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: python@3.11-slim › ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: python@3.11-slim › ncurses/ncurses-bin@6.5+20250216-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream ncurses package and not the ncurses package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A vulnerability has been found in GNU ncurses up to 6.5-20250322 and classified as problematic. This vulnerability affects the function postprocess_termcap of the file tinfo/parse_entry.c. The manipulation leads to stack-based buffer overflow. The attack needs to be approached locally. Upgrading to version 6.5-20250329 is able to address this issue. It is recommended to upgrade the affected component.

Remediation

There is no fixed version for Debian:13 ncurses.

References

low severity

Link Following

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.40.1-6+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › perl/perl-base@5.40.1-6+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

_is_safe in the File::Temp module for Perl does not properly handle symlinks.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity
new

Incorrect Authorization

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

SQLite before 3.54.0 contains an authorization bypass vulnerability in lookupName() that invokes the authorizer only for the first joined table's USING column. Attackers able to submit SQL can query a shared USING column in a RIGHT or FULL JOIN to read columns denied via sqlite3_set_authorizer() SQLITE_READ restrictions.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

Incorrect Resource Transfer Between Spheres

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

In systemd 259, systemd-journald can send ANSI escape sequences to the terminals of arbitrary users when a "logger -p emerg" command is executed, if ForwardToWall=yes is set.

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Out-of-bounds Write

  • Vulnerable module: bzip2/libbz2-1.0
  • Introduced through: bzip2/libbz2-1.0@1.0.8-6

Detailed paths

  • Introduced through: python@3.11-slim › bzip2/libbz2-1.0@1.0.8-6

NVD Description

Note: Versions mentioned in the description apply only to the upstream bzip2 package and not the bzip2 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

bzip2 contains an off‑by‑one error in the bzip2recover utility. When processing a specially crafted file, the application performs an out‑of‑bounds write to a global buffer, resulting in memory corruption and a crash (denial of service).

This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67

Remediation

There is no fixed version for Debian:13 bzip2.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: diffutils
  • Introduced through: diffutils@1:3.10-4

Detailed paths

  • Introduced through: python@3.11-slim › diffutils@1:3.10-4

NVD Description

Note: Versions mentioned in the description apply only to the upstream diffutils package and not the diffutils package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

diff3 tool from GNU diffutils is vulnerable to a heap‑based buffer overflow due to multiple signed integer overflows in line‑mapping calculations. Incorrect arithmetic in mapping line ranges can result in corrupted values being used for memory allocation and loop bounds. When processing crafted diff output, these overflows may cause the application to allocate insufficient memory and subsequently perform out‑of‑bounds writes during internal processing.  An attacker who can control the output of the diff program used by diff3 (e.g. via --diff-program pointing to a malicious script) can trigger out-of-bounds writes, resulting in a crash and potentially remote code execution depending on the environment.

This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815 

NOTE: The project maintainers claim that this is not a security issue. They state that the worst outcome this issue can cause is a crash of diff and that it cannot be used to escalate privileges.

Remediation

There is no fixed version for Debian:13 diffutils.

References

low severity
new

CVE-2026-91094

  • Vulnerable module: dpkg
  • Introduced through: dpkg@1.22.22

Detailed paths

  • Introduced through: python@3.11-slim › dpkg@1.22.22

NVD Description

Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A directory traversal bug was discovered when unpacking 3.0 (quilt) source packages, where the packaging tarball could contain the quilt database directory (.pc) with attacker controlled symlinks, where that in combination with patches that would fail to apply, could be used to make the code used to restore the backup files to either modify or remove the files pointed to by the attacker controlled symlinks.

Remediation

There is no fixed version for Debian:13 dpkg.

References

low severity
new

CVE-2026-100290

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The regcomp and regexec functions in the GNU C Library version 2.3 to version 2.44 may read freed memory and free the same heap block twice when a memory allocation fails while a regular expression is compiled or matched. The re_dfa_add_node (the NFA node table) and build_range_exp (bracket ranges) grow several arrays with consecutive realloc calls and store the new pointers only after all of them succeed. When a later call fails, the pattern buffer keeps pointers to blocks that were already freed, and the error cleanup frees them again. In regexec, the back-reference cache (match_ctx_add_entry) frees its array when a realloc fails but keeps the pointer, which is freed again on the error path.

An attacker does not need to supply a crafted regular expression: patterns large enough to grow these arrays are common. The failure has to hit a specific allocation, though, so the issue can only be reached when the system is already under memory pressure. An attacker who supplies the pattern or the subject string has little control over which allocation fails, so the expected impact is a crash of the process. This issue affects all architectures and ABIs supported by the GNU C Library.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-115819

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Calling the wide scanf family of functions (swscanf, fwscanf, wscanf, vswscanf, vfwscanf and vwscanf) with a %s or %[ conversion without the 'l' length modifier in the GNU C Library version 2.2 to version 2.44 writes an extra null byte one past the end of the destination array when the converted multibyte string and its terminating null byte exactly fill that array.

These conversions store each wide input character into the caller's char array as a multibyte sequence. The conversion ends with the sequence that returns to the initial shift state, which also stores the terminating null byte, and the functions then append a second null byte. A destination sized for the converted string and one terminator, as the C standard requires the caller to provide, is therefore written one byte past its end. The out-of-bounds byte is always a null byte, which may corrupt adjacent data or crash the process. An attacker who supplies the input can trigger the overflow with a string whose converted length exactly fills the destination.

The narrow scanf functions, the %ls and %l[ conversions into a wchar_t array, and the 'a' and 'm' allocation modifiers are not affected, and storing a wide scanf conversion into a narrow char array is uncommon. This issue affects all architectures and ABIs supported by the GNU C Library.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-121757

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Converting crafted CP949 input to UTF-8 character encoding and ignoring invalid characters, in the GNU C Library version 2.1 or later may result in the converter reading past the end of the input buffer, causing the calling application to crash.

When the CP949 decoder encounters an invalid input byte sequence like '\xa2\xe8' it ends up advancing the pointer tracking the read buffer position twice. If //IGNORE is set on the destination encoding and this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer. To exploit this, the target iconv function needs to set //IGNORE on the destination of the conversion and the input and encoding needs to be attacker controlled.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-121758

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Converting crafted ISO-2022-CN-EXT input to UTF-8 character encoding, in the GNU C Library version 2.2 through 2.44 may result in the converter reading past the end of the input buffer, causing the calling application to crash.

When the ISO-2022-CN-EXT decoder encounters an invalid input byte sequence like '\x0e' it ends up advancing the pointer tracking the read buffer position twice. If this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer. To exploit this, the input and encoding needs to be attacker controlled.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-124024

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Converting crafted input from UCS-4 to IBM1390 or IBM1399 character encoding, in the GNU C Library version 2.3.3 and later may result in the converter reading past the end of the input buffer, causing the calling application to crash.

When converting from UCS-4, these encoders may encounter a combining base such as U+00E6 and jump ahead by 4 bytes to check the next UCS-4 code point. The check for end of buffer however does not account for this, which may result in a buffer overread if the following code point has less than 4 bytes remaining. Exploitation of this bug not only requires attacker control of input and encoding, but also strict control over layout of the input in memory.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-18374

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Passing an effectively empty string to the ,ccs= syntax extension of the mode argument in the fopen function in the GNU C Library version 2.45 or earlier may result in a heap buffer overflow when the mode string input to the function is attacker controlled.

This usage pattern is not seen in applications in common GNU/Linux distributions and applications that process user-supplied values for ccs should not pass them through without validation.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-19499

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Calling strfmon and strfmon_l in the GNU C Library version 2.38 to 2.44 can write past the end of the caller-supplied output buffer when a conversion uses right-justified width padding.

Exploitation requires an application code path that calls strfmon or strfmon_l with right-justified width padding into a destination buffer that is large enough for the padding to succeed but too small for the internal memmove call. The field width or format may be attacker-influenced or a fixed susceptible pattern in the caller.

At the time of publication, no network-facing application impact is known.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-19542

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Calling tdelete on a sufficiently deep tree in the GNU C Library version 2.1 to 2.44 may write one pointer past the end of an alloca-allocated array on the stack, which may crash the application.

The tdelete implementation keeps an explicit stack of parent nodes for rebalancing, which is grown as needed while descending the tree. Two rebalancing branches push an additional entry without checking the capacity, and write past the array when the stack is exactly full. Triggering this requires a node at a depth of exactly 40 (or 40 plus a multiple of 20), which implies a tree with at least a million nodes, so an attacker must drive a large number of insertions and deletions through an application that uses tsearch and tdelete. The written value is a pointer into a tree node and is not directly attacker controlled. No affected application in common distributions has been identified.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-5435

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.2 and newer fail to enforce the caller-supplied buffer length, and can result in an out-of-bounds write when printing TSIG records.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-6238

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.0.1 to version 2.43 fail to validate the RDATA content against the RDATA length in a DNS response when processing A6, CERT, LOC, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory.

These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-6368

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Calling wordexp with WRDE_APPEND in the GNU C Library version 2.0 to version 2.43 can cause the interface to return invalid memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-6791

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

When expanding paths that begin with a tilde (~) followed by a username, the internal parse_tilde function extracts the username to determine the user's home directory. The implementation allocates memory for this username directly on the stack using the strndupa macro. Because the size of this allocation was determined by the length of the user-supplied input without any bounds checks, passing an excessively long username e.g. thousands of characters, forces the thread to exhaust its stack space. Thus if an application passes untrusted, attacker-controlled input to the wordexp function, an attacker can trigger a stack clash.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-77117

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Converting crafted SHIFT_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.

Some SHIFT_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the SHIFT_JISX0213 character set is affected, which is not commonly used. The related defect in the EUC_JISX0213 converter is tracked separately as CVE-2026-80489.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-80489

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Converting crafted EUC_JISX0213 input to UCS-4 or the internal wide character encoding, for example with iconv, in the GNU C Library version 2.3 to 2.44 may result in the converter making no progress, causing the calling application to hang.

Some EUC_JISX0213 sequences decode to two code points. If the output buffer has room for only the first one, the converter stores the second in the conversion state and returns E2BIG, but it never clears that pending character after emitting it on the next call. The converter then keeps emitting the pending character without consuming further input, so an application that retries the conversion loops forever. The input must be attacker controlled and the application must convert it with an output buffer small enough to split the two code points. Only the EUC_JISX0213 character set is affected, which is not commonly used. The related defect in SHIFT_JISX0213 converter is tracked separately as CVE-2026-77117.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-84243

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to "..", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this.

The fix for CVE-2014-0475 rejects ".." path components in locale names passed to setlocale or taken from the LC_ALL, LC_* and LANG environment variables. gettext reads LANGUAGE directly and appends each colon-separated entry to the message catalog directory, so that fix did not cover LANGUAGE.

LANGUAGE is only used when the LC_MESSAGES locale is not "C", "C.<encoding>" or "POSIX", so the attacker must also be able to select another installed locale, for example through LANG or LC_ALL. Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE. An example is an SSH server that accepts LANGUAGE and LANG from clients through the AcceptEnv directive and restricts an account to a forced command; the attacker may use this to escape the restriction.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-8674

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Initializing the DNS stub resolver from an /etc/resolv.conf file, or a LOCALDOMAIN environment variable, whose search list contains a domain of roughly 200 characters or more in the GNU C Library version 2.26 to 2.44 results in an assertion failure which aborts the process.

The resolver truncates the search list when copying it into the fixed-size _res.defdname buffer, then asserts that the copy is consistent with the full configuration. The consistency check compared against the wrong size and did not handle a first entry that does not fit, so a correctly truncated list failed the assertion. Any process that resolves names through the library is affected, including long-running processes that reload /etc/resolv.conf on the next query after it changes. Search domains are commonly written to /etc/resolv.conf from data received over DHCP or from a VPN server, so an attacker on the local network may be able to trigger this without privileges on the target system, subject to validation by the network configuration software.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-86805

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A time-of-check to time-of-use (TOCTOU) race condition in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to escalate privileges. When expanding $ORIGIN in DT_RPATH for setuid/setgid (AT_SECURE) programs, glibc validates the lexically normalized search path against the trusted directories but then opens the raw, un-normalized path. On systems where the Linux fs.protected_hardlinks sysctl is disabled, a local attacker who hard-links such a program into an attacker-controlled directory and wins a race to replace an intermediate path component with a symbolic link can direct the loader outside the trusted directory, causing it to load an attacker-controlled shared object and execute arbitrary code with the elevated privileges of the program.

Exploitation requires an installed setuid or setgid binary whose DT_RPATH uses $ORIGIN followed by ".." traversal that normalizes into a trusted directory, and the ability to hard-link that binary and win the race by swapping a path component for a symbolic link. Major Linux-based OS distributions ship with fs.protected_hardlinks enabled by default and mitigate the vulnerability.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-89092

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The nscd service in the GNU C Library 2.3.4 onwards may crash due to a stack overflow when a malicious DNS server returns too large a response for a DNS query, resulting in degraded DNS resolution for the system.

Exploitation of this bug needs a system that has nscd enabled and using an untrusted DNS server for name resolution, with the compromised DNS server being capable of processing records large enough to result in a stack overflow in an nscd thread stack.  During experimentation, bind 9 was unable to handle large records, but that could change in future or with a different name server.  In typical installations, nscd is executed in an isolated context as its own user without a shell, due to which any compromise of that service is isolated.

There is a remote possibility of nscd cache corruption if an attacker manages to get the stack pointer into a desired point in the heap, potentially resulting in other caches in nscd being overwritten with corrupt data through the stack overflow, until the buggy code path eventually results in a crash.

Finally, a crash in nscd may result in performance degradation when resolving names, but it does not result in a denial of service.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-95818

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A stack-based buffer overflow in the dynamic loader (ld.so) of the GNU C Library (glibc) versions 2.14 through 2.44 allows a local attacker to crash or corrupt the memory of setuid/setgid (AT_SECURE) programs.

When such a program's DT_RPATH or DT_RUNPATH begins with $ORIGIN and is followed by NUL or '/' the loader both reads past the end of the path buffer and writes past the end of a stack-allocated internal buffer. The corrupted loader stack can lead to a loader crash (denial of service) and limited disclosure of process memory.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-97399

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u4 and glibc/libc6@2.41-12+deb13u4

Detailed paths

  • Introduced through: python@3.11-slim › glibc/libc-bin@2.41-12+deb13u4
  • Introduced through: python@3.11-slim › glibc/libc6@2.41-12+deb13u4

NVD Description

Note: Versions mentioned in the description apply only to the upstream glibc package and not the glibc package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

The strncasecmp function in the GNU C Library 2.24 and later optimized for the Power8 architecture may read one byte beyond the input size limit, which may crash a program when that byte is not readable.

This condition may happen when the input strings to the strncasecmp function are attacker controlled in an application and they match all the way up to the edge of their page and the neighbouring page is either not mapped or is not readable.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-107493

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack.

Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this.

CWE: CWE-416: Use After Free

Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged.

If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack.

An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory.

Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack.

The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions.

FIPS impact: no The affected code is outside the FIPS module boundary.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-107496

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.

Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service.

CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')

Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns.

The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop.

OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option.

The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected.

The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely.

FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-124709

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: A QUIC server that rejects a stream opened by the peer may retain that stream's state for the lifetime of the connection if the peer resets the stream before the rejection is signalled, even though the peer's stream credit is returned.

Impact summary: A remote client that completes a QUIC handshake can repeatedly open and reset streams, causing server memory to grow without bound until the process runs out of memory and every connection on it is lost. This is a Denial of Service.

CWE: CWE-401: Missing Release of Memory after Effective Lifetime

Description: QUIC servers track each stream the peer opens. When the incoming stream policy rejects a stream, OpenSSL schedules a STOP_SENDING frame, marks the stream deleted and returns the peer's stream credit. A deleted stream is collected only once its receive part is fully drained, which for a rejected stream means the STOP_SENDING has been acknowledged. If the peer sends RESET_STREAM first, the reset cancels the pending STOP_SENDING, so it is never sent or acknowledged and the stream is never collected.

The default configuration reaches this path. Once a connection has a default stream, meaning the application has read from or written to the connection as the tutorial server does, the effective incoming stream policy rejects streams the application does not accept. Applications that set the REJECT policy explicitly are affected too.

Each retained stream costs about 300 bytes, and the peer's stream credit window paces how quickly they accumulate. A client that keeps the connection open and keeps opening and resetting streams grows server memory without bound. The severity is Low because growth is slow, needs a long-lived connection, and causes no memory corruption or disclosure.

FIPS impact: no The affected code is outside the FIPS module boundary.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-35190

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: A server configured with the Suite B certificate flag through SSL_CTX_set_cert_flags() and with TLS 1.3 enabled may read past the end of a fixed group list when it processes a ClientHello whose supported_groups and key_share contain no Suite B group.

Impact summary: A remote client can send a ClientHello that makes the server read past the end of a static array. The values read are never returned to the client, so no memory is disclosed; on builds with sanitizers or hardened allocators the read may crash the process, causing Denial of Service.

CWE: CWE-125: Out-of-bounds Read

Description: When the Suite B certificate flag is set, OpenSSL restricts the accepted groups to P-256 and P-384 by substituting a fixed two-element list for the configured group list. The tuple machinery used for key-share selection was not updated for this substitution: tls1_get_group_tuples() still returns the configured tuples, which by default describe eight groups. The server-side walk in tls_parse_ctos_key_share() then advances through the two-element list using those tuple counts without checking the cumulative offset against the number of groups present.

Only applications that call SSL_CTX_set_cert_flags() with SSL_CERT_FLAG_SUITEB_128_LOS and leave TLS 1.3 enabled are affected. The openssl s_server -suiteB_128 option sets an X.509 verification parameter instead, so the stock command line server is not vulnerable. Default configurations do not reach this code.

A client that offers only groups outside the Suite B set, such as X25519, forces every tuple to be walked and the read to run past the array. The bytes read are compared against client group IDs and never sent back, so no memory is disclosed. On builds with address sanitizers or hardened allocators the read can abort the process; in ordinary release builds it reads a few bytes of adjacent constant data.

FIPS impact: no The affected code is outside the FIPS module boundary.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-84786

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-88822

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: QUIC, when performing automated peer detection, may allow uninitialized stack data to leak into the received address which is then used as the destination for outgoing packets.

Impact summary: Applications using QUIC's automated peer detection mechanism may receive an invalid address, leading to connection loss and disclosure of uninitialized stack data to an attacker observing the outgoing network traffic.

CWE: CWE-457 (Use of Uninitialized Variable)

Description: The OpenSSL QUIC stack contains a feature in which, when using an already connected socket, it will auto-detect the peer address during the SSL handshake. This feature uses the getpeername() function, passing a buffer of sufficient length to hold any supported address family, but passes a buffer length that is only sized such that larger addresses, such as IPv6, cannot be retrieved. The getpeername() function however, still returns the full address length, which is accepted as the valid input buffer length, leading to the address buffer containing uninitialized stack data instead of the actual peer address. The invalid peer address is then used as destination for the outgoing packets which leads to a connectivity breakage and a leakage of the uninitialized stack data to passive network observers.

FIPS impact: no The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this CVE as the affected protocol is not implemented in the FIPS module.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-88823

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: The AES-GCM-SIV implementation treats a zero-length Additional Authenticated Data (AAD) update as a reset of all the AAD supplied so far, instead of leaving the AAD unchanged. An application that supplies its AAD in several fragments, one of which is empty, therefore produces or verifies messages whose authentication tag does not cover the AAD supplied before the empty fragment.

Impact summary: Data an application intended to authenticate alongside a message is silently left unauthenticated. An attacker can forge the AAD of such a message.

CWE: CWE-325: Missing Cryptographic Step

Description: An application passing AAD in multiple chunks of which some have zero length will have the previous AAD chunks effectively unauthenticated. Also, on context re-initialisation, the AAD was not reset, which meant that any AAD accumulated from the previous context usage were also included in the AAD of the new message.

The fix makes a zero-length AAD update a no-op and clears any accumulated AAD whenever the context is re-initialised with a key or a nonce. A re-initialisation that only changes parameters keeps the AAD.

FIPS impact: no The FIPS modules are not affected, as AES-GCM-SIV is not a FIPS approved algorithm and is implemented only in the default provider, outside the OpenSSL FIPS module boundary.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-95690

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-95691

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: A retransmitted QUIC CRYPTO frame can release packet storage while the TLS record layer retains a direct pointer into that storage causing use after free.

Impact summary: A malicious QUIC server can cause a heap-use-after-free read in the OpenSSL QUIC client. The server can also identify one allocator-adjacent byte through the client's protected Handshake response.

CWE: CWE-416: Use After Free

Description: During CRYPTO stream processing, a pointer into the first frame's memory on the stream is lent to the TLS handshake processing. The memory must remain stable until it is processed and released. However the processing of retransmitted CRYPTO frames could release the memory if the retransmitted frame fully overlapped the existing frame. This then causes use-after-free read when the TLS handshake processing continues.

The use-after-free read can lead to a Denial-of-Service of the client application or a minor leak of information about the heap memory contents that might be overwritten with other data, subsequently allocated by the application, to the peer.

FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside of the OpenSSL FIPS module boundary.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity
new

CVE-2026-95692

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.7-1~deb13u3, openssl/libssl3t64@3.5.7-1~deb13u3 and others

Detailed paths

  • Introduced through: python@3.11-slim › openssl@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/libssl3t64@3.5.7-1~deb13u3
  • Introduced through: python@3.11-slim › openssl/openssl-provider-legacy@3.5.7-1~deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream openssl package and not the openssl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Issue summary: Setting an AES-GCM-SIV IV shorter than the expected nonce length via EVP_CipherInit_ex() may trigger a heap out-of-bounds read. Supplying a longer IV is silently truncated instead of rejected.

Impact summary: An application passing a caller-supplied IV of the wrong length may crash or read beyond its buffer. Because trailing IV bytes are ignored, an attacker who knows one message and tag may forge messages under a different IV.

CWE: CWE-125: Out-of-bounds Read

Description: AES-GCM-SIV copies the caller-supplied IV or nonce into its internal state using a copy whose length is taken from the expected nonce size rather than from the length the caller actually provided. When the caller passes a shorter IV, the copy reads past the end of the caller's buffer; AddressSanitizer confirms a heap out-of-bounds read reached through EVP_CipherInit_ex() into ossl_aes_gcm_siv_init(). When the caller passes a longer IV, the implementation silently discards the trailing bytes instead of rejecting the length.

The truncation breaks the binding between the IV and the computed authentication tag. An attacker who has observed a message and its tag under one IV can produce a message and tag that verify under a different IV whose first bytes match, since the surplus bytes never influence the computation. The message itself is unchanged, so this is a failure of IV commitment rather than a classic existential forgery.

Only applications that call EVP_CipherInit_ex() (or the equivalent provider cipher initialization) with an IV length other than the standard 12 bytes for AES-GCM-SIV are affected. The severity is limited because the out-of-bounds read is small and attacker-controlled only in length, and the forgery requires an unusual IV length choice by the application.

FIPS impact: no The FIPS modules are not affected by this issue, as AES-GCM-SIV is not an approved algorithm.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity

CVE-2026-54411

  • Vulnerable module: pam/libpam-modules
  • Introduced through: pam/libpam-modules@1.7.0-5, pam/libpam-modules-bin@1.7.0-5 and others

Detailed paths

  • Introduced through: python@3.11-slim › pam/libpam-modules@1.7.0-5
  • Introduced through: python@3.11-slim › pam/libpam-modules-bin@1.7.0-5
  • Introduced through: python@3.11-slim › pam/libpam-runtime@1.7.0-5
  • Introduced through: python@3.11-slim › pam/libpam0g@1.7.0-5

NVD Description

Note: Versions mentioned in the description apply only to the upstream pam package and not the pam package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Linux-PAM through 1.7.2 contains an observable timing discrepancy (CWE-208) in the pam_userdb module's plaintext-password comparison path in modules/pam_userdb/pam_userdb.c that allows a local or network-adjacent attacker able to repeatedly drive authentication through a calling service to recover the plaintext password of a target account by measuring response-timing differences.

Remediation

There is no fixed version for Debian:13 pam.

References

low severity

CVE-2026-15534

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.40.1-6+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › perl/perl-base@5.40.1-6+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Perl versions through 5.45.1 have out-of-bounds heap reads and writes during regular expression matching via an undersized superlinear cache in S_regmatch.

The regex engine's superlinear cache holds one bit per subject position for each participating WHILEM node, so the bit count is the subject length plus one times the number of nodes. Nothing checks that product for positive overflow of the signed 32-bit count: a 286331153 byte subject matched against a pattern with 15 participating nodes stores the count as 14, leaving a two byte cache. The cache is then indexed from the real match position and node number, so reads go past the end of the allocation, and on failure CACHEsayNO sets a bit past it.

A caller that matches an attacker controlled subject of this size against a pattern of this shape can crash the process or corrupt heap memory.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

CVE-2026-82560

  • Vulnerable module: perl/perl-base
  • Introduced through: perl/perl-base@5.40.1-6+deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › perl/perl-base@5.40.1-6+deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream perl package and not the perl package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Pod::Text versions before 6.1.1 for Perl allow CPU and memory exhaustion formatting a POD document whose =over nesting drives the margin to the output width.

Each =over adds its indent to the margin, which wrap() subtracts from the output width to get the space available for text. When that space reaches zero, the line-splitting substitution matches the empty string, and the loop consumes no input while appending the margin padding on every pass.

Formatting an attacker-supplied POD document never returns, and the output grows until memory is exhausted.

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

CVE-2024-56433

  • Vulnerable module: shadow/login.defs
  • Introduced through: shadow/login.defs@1:4.17.4-2 and shadow/passwd@1:4.17.4-2

Detailed paths

  • Introduced through: python@3.11-slim › shadow/login.defs@1:4.17.4-2
  • Introduced through: python@3.11-slim › shadow/passwd@1:4.17.4-2

NVD Description

Note: Versions mentioned in the description apply only to the upstream shadow package and not the shadow package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

shadow-utils (aka shadow) 4.4 through 4.17.0 establishes a default /etc/subuid behavior (e.g., uid 100000 through 165535 for the first user account) that can realistically conflict with the uids of users defined on locally administered networks, potentially leading to account takeover, e.g., by leveraging newuidmap for access to an NFS home directory (or same-host resources in the case of remote logins by these local network users). NOTE: it may also be argued that system administrators should not have assigned uids, within local networks, that are within the range that can occur in /etc/subuid.

Remediation

There is no fixed version for Debian:13 shadow.

References

low severity

CVE-2025-70873

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

An information disclosure issue in the zipfileInflate function in the zipfile extension in SQLite v3.51.1 and earlier allows attackers to obtain heap memory via supplying a crafted ZIP file.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

CVE-2026-50812

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

A NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and SQLite trunk builds before check-in e807d4e3798efd53 allows an attacker who can supply a malformed changeset blob to cause a denial of service. The issue occurs when sqlite3changeset_apply_v3() applies a corrupt changeset and reaches sqlite3_value_type() with a NULL sqlite3_value pointer.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

CVE-2026-50813

  • Vulnerable module: sqlite3/libsqlite3-0
  • Introduced through: sqlite3/libsqlite3-0@3.46.1-7+deb13u2

Detailed paths

  • Introduced through: python@3.11-slim › sqlite3/libsqlite3-0@3.46.1-7+deb13u2

NVD Description

Note: Versions mentioned in the description apply only to the upstream sqlite3 package and not the sqlite3 package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

An issue in SQLite before Fossil check-in 869a51ae84df allows a local attacker to obtain sensitive information via the Session Extension changeset concat/changegroup merge path

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

CVE-2026-15059

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

Local unprivileged users can terminate arbitrary local processes via a systemd-oomd IPC API due to a missing path traversal validation.

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

CVE-2026-16742

  • Vulnerable module: systemd/libsystemd0
  • Introduced through: systemd/libsystemd0@257.13-1~deb13u1 and systemd/libudev1@257.13-1~deb13u1

Detailed paths

  • Introduced through: python@3.11-slim › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: python@3.11-slim › systemd/libudev1@257.13-1~deb13u1

NVD Description

Note: Versions mentioned in the description apply only to the upstream systemd package and not the systemd package as distributed by Debian. See How to fix? for Debian:13 relevant fixed versions and status.

systemd-homed contains a local privilege escalation bug via arbitrary system group addition to a local, logged in, homed-managed user

Remediation

There is no fixed version for Debian:13 systemd.

References