Vulnerabilities

151 via 694 paths

Dependencies

207

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
  • 147
Status
  • 151
  • 0
  • 0

medium severity
new

Improper Access Control

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

Detailed paths

  • Introduced through: golang@latest systemd/libsystemd0@257.9-1~deb13u1
  • Introduced through: golang@latest systemd/libudev1@257.9-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.

A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.

Remediation

There is no fixed version for Debian:13 systemd.

References

medium severity
new

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

libexpat before 2.7.5 allows an infinite loop while parsing DTD content.

Remediation

There is no fixed version for Debian:13 expat.

References

medium severity
new

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.

Remediation

There is no fixed version for Debian:13 expat.

References

medium severity
new

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Out-of-Bounds

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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: golang@latest 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

Improper Encoding or Escaping of Output

  • Vulnerable module: git
  • Introduced through: git@1:2.47.3-0+deb13u1 and git/git-man@1:2.47.3-0+deb13u1

Detailed paths

  • Introduced through: golang@latest git@1:2.47.3-0+deb13u1
  • Introduced through: golang@latest git/git-man@1:2.47.3-0+deb13u1

NVD Description

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

Git is a source code management tool. When cloning from a server (or fetching, or pushing), informational or error messages are transported from the remote Git process to the client via the so-called "sideband channel". These messages will be prefixed with "remote:" and printed directly to the standard error output. Typically, this standard error output is connected to a terminal that understands ANSI escape sequences, which Git did not protect against. Most modern terminals support control sequences that can be used by a malicious actor to hide and misrepresent information, or to mislead the user into executing untrusted scripts. As requested on the git-security mailing list, the patches are under discussion on the public mailing list. Users are advised to update as soon as possible. Users unable to upgrade should avoid recursive clones unless they are from trusted sources.

Remediation

There is no fixed version for Debian:13 git.

References

low severity

CVE-2019-1010023

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils up to 2.44. It has been rated as critical. Affected by this issue is the function elf_gc_sweep of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. Upgrading to version 2.45 is able to address this issue. It is recommended to upgrade the affected component.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability classified as critical has been found in GNU Binutils up to 2.44. This affects the function debug_type_samep of the file /binutils/debug.c of the component objdump. The manipulation leads to memory corruption. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability, which was classified as problematic, has been found in GNU Binutils 2.45. Affected by this issue is the function bfd_elf_set_group_contents of the file bfd/elf.c. The manipulation leads to out-of-bounds write. It is possible to launch the attack on the local host. The exploit has been disclosed to the public and may be used. The name of the patch is 41461010eb7c79fee7a9d5f6209accdaac66cc6b. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability classified as problematic was found in GNU Binutils 2.45. Affected by this vulnerability is the function copy_section of the file binutils/objcopy.c. The manipulation leads to heap-based buffer overflow. Attacking locally is a requirement. The exploit has been disclosed to the public and may be used. The patch is named 08c3cbe5926e4d355b5cb70bbec2b1eeb40c2944. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability has been found in GNU Binutils 2.45. The affected element is the function elf_swap_shdr in the library bfd/elfcode.h of the component Linker. The manipulation leads to heap-based buffer overflow. The attack must be carried out locally. The exploit has been disclosed to the public and may be used. The identifier of the patch is 9ca499644a21ceb3f946d1c179c38a83be084490. To fix this issue, it is recommended to deploy a patch. The code maintainer replied with "[f]ixed for 2.46".

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A flaw has been found in GNU Binutils 2.45. Impacted is the function _bfd_elf_parse_eh_frame of the file bfd/elf-eh-frame.c of the component Linker. Executing manipulation can lead to heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. This patch is called ea1a0737c7692737a644af0486b71e4a392cbca8. A patch should be applied to remediate this issue. The code maintainer replied with "[f]ixed for 2.46".

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Stack-based Buffer Overflow

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.4.7-21+deb13u1+b2, gnupg2/gnupg@2.4.7-21+deb13u1 and others

Detailed paths

  • Introduced through: golang@latest gnupg2/dirmngr@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gnupg@2.4.7-21+deb13u1
  • Introduced through: golang@latest gnupg2/gnupg-l10n@2.4.7-21+deb13u1
  • Introduced through: golang@latest gnupg2/gpg@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpg-agent@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpgconf@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpgsm@2.4.7-21+deb13u1+b2

NVD Description

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

In GnuPG before 2.5.17, a stack-based buffer overflow exists in tpm2daemon during handling of the PKDECRYPT command for TPM-backed RSA and ECC keys.

Remediation

There is no fixed version for Debian:13 gnupg2.

References

low severity
new

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: golang@latest ncurses/libncursesw6@6.5+20250216-2
  • Introduced through: golang@latest ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: golang@latest ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: golang@latest 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

CVE-2025-66864

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-66866

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in function d_abi_tags in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69649

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

GNU Binutils thru 2.46 readelf contains a null pointer dereference vulnerability when processing a crafted ELF binary with malformed header fields. During relocation processing, an invalid or null section pointer may be passed into display_relocations(), resulting in a segmentation fault (SIGSEGV) and abrupt termination. No evidence of memory corruption beyond the null pointer dereference, nor any possibility of code execution, was observed.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

Double Free

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

GNU Binutils thru 2.46 readelf contains a double free vulnerability when processing a crafted ELF binary with malformed relocation data. During GOT relocation handling, dump_relocations may return early without initializing the all_relocations array. As a result, process_got_section_contents() may pass an uninitialized r_symbol pointer to free(), leading to a double free and terminating the program with SIGABRT. No evidence of exploitable memory corruption or code execution was observed; the impact is limited to denial of service. NOTE: this is disputed by third parties because the observed behavior occurred only in pre-release code and did not affect any tagged version.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Exposure of Resource to Wrong Sphere

  • Vulnerable module: git
  • Introduced through: git@1:2.47.3-0+deb13u1 and git/git-man@1:2.47.3-0+deb13u1

Detailed paths

  • Introduced through: golang@latest git@1:2.47.3-0+deb13u1
  • Introduced through: golang@latest git/git-man@1:2.47.3-0+deb13u1

NVD Description

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

The --mirror documentation for Git through 2.35.1 does not mention the availability of deleted content, aka the "GitBleed" issue. This could present a security risk if information-disclosure auditing processes rely on a clone operation without the --mirror option. Note: This has been disputed by multiple 3rd parties who believe this is an intended feature of the git binary and does not pose a security risk.

Remediation

There is no fixed version for Debian:13 git.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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

Out-of-bounds Read

  • Vulnerable module: jansson/libjansson4
  • Introduced through: jansson/libjansson4@2.14-2+b3

Detailed paths

  • Introduced through: golang@latest jansson/libjansson4@2.14-2+b3

NVD Description

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

An issue was discovered in Jansson through 2.13.1. Due to a parsing error in json_loads, there's an out-of-bounds read-access bug. NOTE: the vendor reports that this only occurs when a programmer fails to follow the API specification

Remediation

There is no fixed version for Debian:13 jansson.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others

Detailed paths

  • Introduced through: golang@latest krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: golang@latest krb5/libk5crypto3@1.21.3-5
  • Introduced through: golang@latest krb5/libkrb5-3@1.21.3-5
  • Introduced through: golang@latest krb5/libkrb5support0@1.21.3-5

NVD Description

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

An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.

Remediation

There is no fixed version for Debian:13 krb5.

References

low severity

Use of a Broken or Risky Cryptographic Algorithm

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.11.0-7

Detailed paths

  • Introduced through: golang@latest libgcrypt20@1.11.0-7

NVD Description

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

cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.

Remediation

There is no fixed version for Debian:13 libgcrypt20.

References

low severity

Cryptographic Issues

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: golang@latest openldap/libldap2@2.6.10+dfsg-1

NVD Description

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

The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.

Remediation

There is no fixed version for Debian:13 openldap.

References

low severity

Out-of-Bounds

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: golang@latest openldap/libldap2@2.6.10+dfsg-1

NVD Description

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

contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.

Remediation

There is no fixed version for Debian:13 openldap.

References

low severity

Out-of-bounds Read

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When reading an HTTP response from a server, if no read amount is specified, the default behavior will be to use Content-Length. This allows a malicious server to cause the client to read large amounts of data into memory, potentially causing OOM or other DoS.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

OS Command Injection

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A flaw was found in GNU Binutils. This vulnerability, a heap-based buffer overflow, specifically an out-of-bounds read, exists in the bfd linker component. An attacker could exploit this by convincing a user to process a specially crafted malicious XCOFF object file. Successful exploitation may lead to the disclosure of sensitive information or cause the application to crash, resulting in an application level denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A flaw was found in GNU Binutils. This heap-based buffer overflow vulnerability, specifically an out-of-bounds read in the bfd linker, allows an attacker to gain access to sensitive information. By convincing a user to process a specially crafted XCOFF object file, an attacker can trigger this flaw, potentially leading to information disclosure or an application level denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Inappropriate Encoding for Output Context

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

In OpenSSH 7.9, due to accepting and displaying arbitrary stderr output from the server, a malicious server (or Man-in-The-Middle attacker) can manipulate the client output, for example to use ANSI control codes to hide additional files being transferred.

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A heap-based buffer over-read exists in the function d_expression_1 in cp-demangle.c in GNU libiberty, as distributed in GNU Binutils 2.31.1. A crafted input can cause segmentation faults, leading to denial-of-service, as demonstrated by c++filt.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in GNU libiberty, as distributed in GNU Binutils 2.36. It is a stack-overflow issue in demangle_type in rust-demangle.c.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Access Restriction Bypass

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

sshd in OpenSSH 4 on Debian GNU/Linux, and the 20070303 OpenSSH snapshot, allows remote authenticated users to obtain access to arbitrary SELinux roles by appending a :/ (colon slash) sequence, followed by the role name, to the username.

Remediation

There is no fixed version for Debian:13 openssh.

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: golang@latest shadow/login.defs@1:4.17.4-2
  • Introduced through: golang@latest 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
new

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A flaw was found in the GNU Binutils BFD library, a widely used component for handling binary files such as object files and executables. The issue occurs when processing specially crafted XCOFF object files, where a relocation type value is not properly validated before being used. This can cause the program to read memory outside of intended bounds. As a result, affected tools may crash or expose unintended memory contents, leading to denial-of-service or limited information disclosure risks.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/bsdutils@1:2.41-5 and others

Detailed paths

  • Introduced through: golang@latest util-linux@2.41-5
  • Introduced through: golang@latest util-linux/bsdutils@1:2.41-5
  • Introduced through: golang@latest util-linux/libblkid1@2.41-5
  • Introduced through: golang@latest util-linux/liblastlog2-2@2.41-5
  • Introduced through: golang@latest util-linux/libmount1@2.41-5
  • Introduced through: golang@latest util-linux/libsmartcols1@2.41-5
  • Introduced through: golang@latest util-linux/libuuid1@2.41-5
  • Introduced through: golang@latest util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: golang@latest util-linux/mount@2.41-5

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. This vulnerability allows a heap buffer overread when processing 256-byte usernames, specifically within the setpwnam() function, affecting SUID (Set User ID) login-utils utilities writing to the password database.

Remediation

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

References

low severity

Open Redirect

  • Vulnerable module: wget
  • Introduced through: wget@1.25.0-2

Detailed paths

  • Introduced through: golang@latest wget@1.25.0-2

NVD Description

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

GNU Wget through 1.21.1 does not omit the Authorization header upon a redirect to a different origin, a related issue to CVE-2018-1000007.

Remediation

There is no fixed version for Debian:13 wget.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability classified as problematic was found in GNU Binutils 2.43/2.44. Affected by this vulnerability is the function bfd_set_format of the file format.c. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. Upgrading to version 2.45 is able to address this issue. The identifier of the patch is 8d97c1a53f3dc9fd8e1ccdb039b8a33d50133150. It is recommended to upgrade the affected component.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

The client side in OpenSSH 5.7 through 8.4 has an Observable Discrepancy leading to an information leak in the algorithm negotiation. This allows man-in-the-middle attackers to target initial connection attempts (where no host key for the server has been cached by the client). NOTE: some reports state that 8.5 and 8.6 are also affected.

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. Affected by this vulnerability is the function bfd_putl64 of the file libbfd.c of the component ld. The manipulation leads to memory corruption. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The identifier of the patch is 75086e9de1707281172cc77f178e7949a4414ed0. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

The C++ symbol demangler routine in cplus-dem.c in libiberty, as distributed in GNU Binutils 2.29, allows remote attackers to cause a denial of service (excessive memory allocation and application crash) via a crafted file, as demonstrated by a call from the Binary File Descriptor (BFD) library (aka libbfd).

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69651

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an invalid pointer free when processing a crafted ELF binary with malformed relocation or symbol data. If dump_relocations returns early due to parsing errors, the internal all_relocations array may remain partially uninitialized. Later, process_got_section_contents() may attempt to free an invalid r_symbol pointer, triggering memory corruption checks in glibc and causing the program to terminate with SIGABRT. No evidence of further memory corruption or code execution was observed; the impact is limited to denial of service. NOTE: this is disputed by third parties because the observed behavior occurred only in pre-release code and did not affect any tagged version.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability has been found in GNU Binutils 2.43/2.44 and classified as problematic. Affected by this vulnerability is the function display_info of the file binutils/bucomm.c of the component objdump. The manipulation leads to memory leak. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The patch is named ba6ad3a18cb26b79e0e3b84c39f707535bbc344d. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was detected in GNU Binutils 2.45. This issue affects the function dump_dwarf_section of the file binutils/objdump.c. Performing manipulation results in out-of-bounds read. The attack is only possible with local access. The exploit is now public and may be used. The patch is named f87a66db645caf8cc0e6fc87b0c28c78a38af59b. It is suggested to install a patch to address this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was determined in GNU Binutils 2.45. The affected element is the function elf_x86_64_relocate_section of the file elf64-x86-64.c of the component Linker. This manipulation causes heap-based buffer overflow. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Patch name: 6b21c8b2ecfef5c95142cbc2c32f185cb1c26ab0. To fix this issue, it is recommended to deploy a patch.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.45. Impacted is the function _bfd_x86_elf_late_size_sections of the file bfd/elfxx-x86.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. The patch is identified as b6ac5a8a5b82f0ae6a4642c8d7149b325f4cc60a. A patch should be applied to remediate this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was determined in GNU Binutils 2.45. Affected by this vulnerability is the function get_link_hash_entry of the file bfd/elflink.c of the component Linker. This manipulation causes out-of-bounds read. The attack can only be executed locally. The exploit has been publicly disclosed and may be utilized. Upgrading to version 2.46 addresses this issue. Patch name: aeaaa9af6359c8e394ce9cf24911fec4f4d23703. It is advisable to upgrade the affected component.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.45. Affected is the function elf_link_add_object_symbols of the file bfd/elflink.c of the component Linker. The manipulation results in out-of-bounds read. The attack needs to be approached locally. The exploit has been made public and could be used. Upgrading to version 2.46 is able to address this issue. The patch is identified as 72efdf166aa0ed72ecc69fc2349af6591a7a19c0. Upgrading the affected component is advised.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability has been found in GNU Binutils 2.45. This impacts the function bfd_elf_gc_record_vtentry of the file bfd/elflink.c of the component Linker. The manipulation leads to out-of-bounds read. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used. The identifier of the patch is 047435dd988a3975d40c6626a8f739a0b2e154bc. To fix this issue, it is recommended to deploy a patch.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A weakness has been identified in GNU Binutils 2.45. The affected element is the function vfinfo of the file ldmisc.c. Executing a manipulation can lead to out-of-bounds read. The attack can only be executed locally. The exploit has been made available to the public and could be used for attacks. This patch is called 16357. It is best practice to apply a patch to resolve this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

The demangle_template function in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.31.1, contains an integer overflow vulnerability (for "Create an array for saving the template argument values") that can trigger a heap-based buffer overflow, as demonstrated by nm.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Unchecked Return Value

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A security flaw has been discovered in GNU Binutils 2.45. Impacted is the function tg_tag_type of the file prdbg.c. Performing a manipulation results in unchecked return value. The attack needs to be approached locally. The exploit has been released to the public and may be used for attacks.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in cplus-dem.c in GNU libiberty, as distributed in GNU Binutils 2.30. Stack Exhaustion occurs in the C++ demangling functions provided by libiberty, and there are recursive stack frames: demangle_template_value_parm, demangle_integral_value, and demangle_expression.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

In libexpat through 2.7.3, a crafted file with an approximate size of 2 MiB can lead to dozens of seconds of processing time.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

CVE-2025-13837

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When loading a plist file, the plistlib module reads data in size specified by the file itself, meaning a malicious file can cause OOM and DoS issues

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-6075

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

If the value passed to os.path.expandvars() is user-controlled a performance degradation is possible when expanding environment variables.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

Information Exposure

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/bsdutils@1:2.41-5 and others

Detailed paths

  • Introduced through: golang@latest util-linux@2.41-5
  • Introduced through: golang@latest util-linux/bsdutils@1:2.41-5
  • Introduced through: golang@latest util-linux/libblkid1@2.41-5
  • Introduced through: golang@latest util-linux/liblastlog2-2@2.41-5
  • Introduced through: golang@latest util-linux/libmount1@2.41-5
  • Introduced through: golang@latest util-linux/libsmartcols1@2.41-5
  • Introduced through: golang@latest util-linux/libuuid1@2.41-5
  • Introduced through: golang@latest util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: golang@latest util-linux/mount@2.41-5

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

Improper Validation of Specified Quantity in Input

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

Detailed paths

  • Introduced through: golang@latest 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

There is no fixed version for Debian:13 zlib.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability has been found in GNU Binutils 2.43 and classified as problematic. Affected by this vulnerability is the function __sanitizer::internal_strlen of the file binutils/nm.c of the component nm. The manipulation of the argument const leads to buffer overflow. The attack can be launched remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Information Exposure

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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

CVE-2016-20012

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

OpenSSH through 8.7 allows remote attackers, who have a suspicion that a certain combination of username and public key is known to an SSH server, to test whether this suspicion is correct. This occurs because a challenge is sent only when that combination could be valid for a login session. NOTE: the vendor does not recognize user enumeration as a vulnerability for this product

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity

Improper Authentication

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

OpenSSH 4.6 and earlier, when ChallengeResponseAuthentication is enabled, allows remote attackers to determine the existence of user accounts by attempting to authenticate via S/KEY, which displays a different response if the user account exists, a similar issue to CVE-2001-1483.

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

Remotely observable behaviour in auth-gss2.c in OpenSSH through 7.8 could be used by remote attackers to detect existence of users on a target system when GSS2 is in use. NOTE: the discoverer states 'We understand that the OpenSSH developers do not want to treat such a username enumeration (or "oracle") as a vulnerability.'

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity

CVE-2025-12084

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When building nested elements using xml.dom.minidom methods such as appendChild() that have a dependency on _clear_id_cache() the algorithm is quadratic. Availability can be impacted when building excessively nested documents.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-12781

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When passing data to the b64decode(), standard_b64decode(), and urlsafe_b64decode() functions in the "base64" module the characters "+/" will always be accepted, regardless of the value of "altchars" parameter, typically used to establish an "alternative base64 alphabet" such as the URL safe alphabet. This behavior matches what is recommended in earlier base64 RFCs, but newer RFCs now recommend either dropping characters outside the specified base64 alphabet or raising an error. The old behavior has the possibility of causing data integrity issues.

This behavior can only be insecure if your application uses an alternate base64 alphabet (without "+/"). If your application does not use the "altchars" parameter or the urlsafe_b64decode() function, then your application does not use an alternative base64 alphabet.

The attached patches DOES NOT make the base64-decode behavior raise an error, as this would be a change in behavior and break existing programs. Instead, the patch deprecates the behavior which will be replaced with the newly recommended behavior in a future version of Python. Users are recommended to mitigate by verifying user-controlled inputs match the base64 alphabet they are expecting or verify that their application would not be affected if the b64decode() functions accepted "+" or "/" outside of altchars.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: golang@latest systemd/libsystemd0@257.9-1~deb13u1
  • Introduced through: golang@latest systemd/libudev1@257.9-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.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1

Detailed paths

  • Introduced through: golang@latest systemd/libsystemd0@257.9-1~deb13u1
  • Introduced through: golang@latest systemd/libudev1@257.9-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.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1

Detailed paths

  • Introduced through: golang@latest systemd/libsystemd0@257.9-1~deb13u1
  • Introduced through: golang@latest systemd/libudev1@257.9-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

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.43 and classified as critical. This issue affects the function _bfd_elf_gc_mark_rsec of the file elflink.c of the component ld. The manipulation leads to heap-based buffer overflow. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. The patch is named f9978defb6fab0bd8583942d97c112b0932ac814. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability classified as critical was found in GNU Binutils 2.43. This vulnerability affects the function _bfd_elf_gc_mark_rsec of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. The name of the patch is 931494c9a89558acb36a03a340c01726545eef24. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability, which was classified as critical, was found in GNU Binutils 2.43. Affected is the function bfd_elf_reloc_symbol_deleted_p of the file bfd/elflink.c of the component ld. The manipulation leads to memory corruption. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. The patch is identified as b425859021d17adf62f06fb904797cf8642986ad. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Improper Input Validation

  • Vulnerable module: git
  • Introduced through: git@1:2.47.3-0+deb13u1 and git/git-man@1:2.47.3-0+deb13u1

Detailed paths

  • Introduced through: golang@latest git@1:2.47.3-0+deb13u1
  • Introduced through: golang@latest git/git-man@1:2.47.3-0+deb13u1

NVD Description

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

GIT version 2.15.1 and earlier contains a Input Validation Error vulnerability in Client that can result in problems including messing up terminal configuration to RCE. This attack appear to be exploitable via The user must interact with a malicious git server, (or have their traffic modified in a MITM attack).

Remediation

There is no fixed version for Debian:13 git.

References

low severity

Race Condition

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

Detailed paths

  • Introduced through: golang@latest 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

Improper Verification of Cryptographic Signature

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.4.7-21+deb13u1+b2, gnupg2/gnupg@2.4.7-21+deb13u1 and others

Detailed paths

  • Introduced through: golang@latest gnupg2/dirmngr@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gnupg@2.4.7-21+deb13u1
  • Introduced through: golang@latest gnupg2/gnupg-l10n@2.4.7-21+deb13u1
  • Introduced through: golang@latest gnupg2/gpg@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpg-agent@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpgconf@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpgsm@2.4.7-21+deb13u1+b2

NVD Description

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

In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.

Remediation

There is no fixed version for Debian:13 gnupg2.

References

low severity

Improper Initialization

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: golang@latest openldap/libldap2@2.6.10+dfsg-1

NVD Description

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

slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.

Remediation

There is no fixed version for Debian:13 openldap.

References

low severity

Stack-based Buffer Overflow

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

Detailed paths

  • Introduced through: golang@latest 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.9-1~deb13u1 and systemd/libudev1@257.9-1~deb13u1

Detailed paths

  • Introduced through: golang@latest systemd/libsystemd0@257.9-1~deb13u1
  • Introduced through: golang@latest systemd/libudev1@257.9-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

Resource Management Errors

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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

Improper Input Validation

  • Vulnerable module: gnutls28/libgnutls30t64
  • Introduced through: gnutls28/libgnutls30t64@3.8.9-3+deb13u2

Detailed paths

  • Introduced through: golang@latest gnutls28/libgnutls30t64@3.8.9-3+deb13u2

NVD Description

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

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity

Information Exposure

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

OpenSSH, when using OPIE (One-Time Passwords in Everything) for PAM, allows remote attackers to determine the existence of certain user accounts, which displays a different response if the user account exists and is configured to use one-time passwords (OTP), a similar issue to CVE-2007-2243.

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity

Memory Leak

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

Detailed paths

  • Introduced through: golang@latest sqlite3/libsqlite3-0@3.46.1-7+deb13u1

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

Improper Certificate Validation

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: golang@latest openldap/libldap2@2.6.10+dfsg-1

NVD Description

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

libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.

Remediation

There is no fixed version for Debian:13 openldap.

References

low severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: golang@latest apt@3.0.3
  • Introduced through: golang@latest apt/libapt-pkg7.0@3.0.3

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

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability classified as problematic has been found in GNU Binutils 2.43. Affected is the function xstrdup of the file xstrdup.c of the component ld. The manipulation leads to memory leak. It is possible to launch the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.44 and classified as problematic. This issue affects the function process_debug_info of the file binutils/dwarf.c of the component DWARF Section Handler. The manipulation leads to memory leak. Attacking locally is a requirement. The identifier of the patch is e51fdff7d2e538c0e5accdd65649ac68e6e0ddd4. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-bounds Write

  • Vulnerable module: gnupg2/dirmngr
  • Introduced through: gnupg2/dirmngr@2.4.7-21+deb13u1+b2, gnupg2/gnupg@2.4.7-21+deb13u1 and others

Detailed paths

  • Introduced through: golang@latest gnupg2/dirmngr@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gnupg@2.4.7-21+deb13u1
  • Introduced through: golang@latest gnupg2/gnupg-l10n@2.4.7-21+deb13u1
  • Introduced through: golang@latest gnupg2/gpg@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpg-agent@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpgconf@2.4.7-21+deb13u1+b2
  • Introduced through: golang@latest gnupg2/gpgsm@2.4.7-21+deb13u1+b2

NVD Description

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

GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.

Remediation

There is no fixed version for Debian:13 gnupg2.

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: golang@latest ncurses/libncursesw6@6.5+20250216-2
  • Introduced through: golang@latest ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: golang@latest ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: golang@latest 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
  • Introduced through: perl@5.40.1-6, perl/libperl5.40@5.40.1-6 and others

Detailed paths

  • Introduced through: golang@latest perl@5.40.1-6
  • Introduced through: golang@latest perl/libperl5.40@5.40.1-6
  • Introduced through: golang@latest perl/perl-base@5.40.1-6
  • Introduced through: golang@latest perl/perl-modules-5.40@5.40.1-6

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

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.43. It has been declared as problematic. This vulnerability affects the function bfd_malloc of the file libbfd.c of the component ld. The manipulation leads to memory leak. The attack can be initiated remotely. The complexity of an attack is rather high. The exploitation appears to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.43. It has been rated as problematic. This issue affects the function xmemdup of the file xmemdup.c of the component ld. The manipulation leads to memory leak. The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.43. It has been classified as problematic. This affects the function xstrdup of the file libiberty/xmalloc.c of the component ld. The manipulation leads to memory leak. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Memory Leak

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability was found in GNU Binutils 2.43 and classified as problematic. Affected by this issue is the function link_order_scan of the file ld/ldelfgen.c of the component ld. The manipulation leads to memory leak. The attack may be launched remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue. The code maintainer explains: "I'm not going to commit some of the leak fixes I've been working on to the 2.44 branch due to concern that would destabilise ld. All of the reported leaks in this bugzilla have been fixed on binutils master."

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

Out-of-Bounds

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A vulnerability classified as problematic has been found in GNU Binutils 2.43. This affects the function _bfd_elf_write_section_eh_frame of the file bfd/elf-eh-frame.c of the component ld. The manipulation leads to memory corruption. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

CVE-2025-66861

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in function d_unqualified_name in file cp-demangle.c in BinUtils 2.26 allowing attackers to cause a denial of service via crafted PE file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-66862

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

A buffer overflow vulnerability in function gnu_special in file cplus-dem.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-66863

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in function d_discriminator in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-66865

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in function d_print_comp_inner in file cp-demangle.c in BinUtils 2.26 allows attackers to cause a denial of service via crafted PE file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69644

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

An issue was discovered in Binutils before 2.46. The objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed debug information. A logic flaw in the handling of DWARF location list headers can cause objdump to enter an unbounded loop and produce endless output until manually interrupted. This issue affects versions prior to the upstream fix and allows a local attacker to cause excessive resource consumption by supplying a malicious input file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69645

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug information. A logic error in the handling of DWARF compilation units can result in an invalid offset_size value being used inside byte_get_little_endian, leading to an abort (SIGABRT). The issue was observed in binutils 2.44. A local attacker can trigger the crash by supplying a malicious input file.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69646

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

Binutils objdump contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF debug_rnglists data. A logic error in the handling of the debug_rnglists header can cause objdump to repeatedly print the same warning message and fail to terminate, resulting in an unbounded logging loop until the process is interrupted. The issue was observed in binutils 2.44. A local attacker can exploit this vulnerability by supplying a malicious input file, leading to excessive CPU and I/O usage and preventing completion of the objdump analysis.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69647

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

GNU Binutils thru 2.45.1 readelf contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF loclists data. A logic flaw in the DWARF parsing code can cause readelf to repeatedly print the same table output without making forward progress, resulting in an unbounded output loop that never terminates unless externally interrupted. A local attacker can trigger this behavior by supplying a malicious input file, causing excessive CPU and I/O usage and preventing readelf from completing its analysis.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69648

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

GNU Binutils thru 2.45.1 readelf contains a denial-of-service vulnerability when processing a crafted binary with malformed DWARF .debug_rnglists data. A logic flaw in the DWARF parsing path causes readelf to repeatedly print the same warning message without making forward progress, resulting in a non-terminating output loop that requires manual interruption. No evidence of memory corruption or code execution was observed.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity
new

CVE-2025-69652

  • Vulnerable module: binutils
  • Introduced through: binutils@2.44-3, binutils/binutils-common@2.44-3 and others

Detailed paths

  • Introduced through: golang@latest binutils@2.44-3
  • Introduced through: golang@latest binutils/binutils-common@2.44-3
  • Introduced through: golang@latest binutils/binutils-x86-64-linux-gnu@2.44-3
  • Introduced through: golang@latest binutils/libbinutils@2.44-3
  • Introduced through: golang@latest binutils/libctf-nobfd0@2.44-3
  • Introduced through: golang@latest binutils/libctf0@2.44-3
  • Introduced through: golang@latest binutils/libgprofng0@2.44-3
  • Introduced through: golang@latest binutils/libsframe1@2.44-3

NVD Description

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

GNU Binutils thru 2.46 readelf contains a vulnerability that leads to an abort (SIGABRT) when processing a crafted ELF binary with malformed DWARF abbrev or debug information. Due to incomplete state cleanup in process_debug_info(), an invalid debug_info_p state may propagate into DWARF attribute parsing routines. When certain malformed attributes result in an unexpected data length of zero, byte_get_little_endian() triggers a fatal abort. No evidence of memory corruption or code execution was observed; the impact is limited to denial of service.

Remediation

There is no fixed version for Debian:13 binutils.

References

low severity

CVE-2025-10966

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms.

This prevents curl from detecting MITM attackers and more.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2025-13034

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When using CURLOPT_PINNEDPUBLICKEY option with libcurl or --pinnedpubkey with the curl tool,curl should check the public key of the server certificate to verify the peer.

This check was skipped in a certain condition that would then make curl allow the connection without performing the proper check, thus not noticing a possible impostor. To skip this check, the connection had to be done with QUIC with ngtcp2 built to use GnuTLS and the user had to explicitly disable the standard certificate verification.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2025-14017

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers.

Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2025-14819

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When doing TLS related transfers with reused easy or multi handles and altering the CURLSSLOPT_NO_PARTIALCHAIN option, libcurl could accidentally reuse a CA store cached in memory for which the partial chain option was reversed. Contrary to the user's wishes and expectations. This could make libcurl find and accept a trust chain that it otherwise would not.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2025-15079

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2025-15224

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-1965

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

libcurl can in some circumstances reuse the wrong connection when asked to do an Negotiate-authenticated HTTP or HTTPS request.

libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead.

When reusing a connection a range of criterion must first be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. One underlying reason being that Negotiate sometimes authenticates connections and not requests, contrary to how HTTP is designed to work.

An application that allows Negotiate authentication to a server (that responds wanting Negotiate) with user1:password1 and then does another operation to the same server also using Negotiate but with user2:password2 (while the previous connection is still alive) - the second request wrongly reused the same connection and since it then sees that the Negotiate negotiation is already made, it just sends the request over that connection thinking it uses the user2 credentials when it is in fact still using the connection authenticated for user1...

The set of authentication methods to use is set with CURLOPT_HTTPAUTH.

Applications can disable libcurl's reuse of connections and thus mitigate this problem, by using one of the following libcurl options to alter how connections are or are not reused: CURLOPT_FRESH_CONNECT, CURLOPT_MAXCONNECTS and CURLMOPT_MAX_HOST_CONNECTIONS (if using the curl_multi API).

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-3783

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a redirect to a second URL, curl could leak that token to the second hostname under some circumstances.

If the hostname that the first request is redirected to has information in the used .netrc file, with either of the machine or default keywords, curl would pass on the bearer token set for the first host also to the second one.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-3784

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

curl would wrongly reuse an existing HTTP proxy connection doing CONNECT to a server, even if the new request uses different credentials for the HTTP proxy. The proper behavior is to create or use a separate connection.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-3805

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When doing a second SMB request to the same host again, curl would wrongly use a data pointer pointing into already freed memory.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Open Redirect

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u2, curl/libcurl3t64-gnutls@8.14.1-2+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest curl@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl3t64-gnutls@8.14.1-2+deb13u2
  • Introduced through: golang@latest curl/libcurl4t64@8.14.1-2+deb13u2

NVD Description

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

When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.7.1-2

Detailed paths

  • Introduced through: golang@latest expat/libexpat1@2.7.1-2

NVD Description

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

libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity
new

CVE-2026-4437

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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 gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity
new

CVE-2026-4438

  • Vulnerable module: glibc/libc-bin
  • Introduced through: glibc/libc-bin@2.41-12+deb13u2, glibc/libc-dev-bin@2.41-12+deb13u2 and others

Detailed paths

  • Introduced through: golang@latest glibc/libc-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc-dev-bin@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6@2.41-12+deb13u2
  • Introduced through: golang@latest glibc/libc6-dev@2.41-12+deb13u2

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 gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2024-26461

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others

Detailed paths

  • Introduced through: golang@latest krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: golang@latest krb5/libk5crypto3@1.21.3-5
  • Introduced through: golang@latest krb5/libkrb5-3@1.21.3-5
  • Introduced through: golang@latest krb5/libkrb5support0@1.21.3-5

NVD Description

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.

Remediation

There is no fixed version for Debian:13 krb5.

References

low severity

Memory Leak

  • Vulnerable module: krb5/libgssapi-krb5-2
  • Introduced through: krb5/libgssapi-krb5-2@1.21.3-5, krb5/libk5crypto3@1.21.3-5 and others

Detailed paths

  • Introduced through: golang@latest krb5/libgssapi-krb5-2@1.21.3-5
  • Introduced through: golang@latest krb5/libk5crypto3@1.21.3-5
  • Introduced through: golang@latest krb5/libkrb5-3@1.21.3-5
  • Introduced through: golang@latest krb5/libkrb5support0@1.21.3-5

NVD Description

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

Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.

Remediation

There is no fixed version for Debian:13 krb5.

References

low severity

Covert Timing Channel

  • Vulnerable module: libgcrypt20
  • Introduced through: libgcrypt20@1.11.0-7

Detailed paths

  • Introduced through: golang@latest libgcrypt20@1.11.0-7

NVD Description

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

A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.

Remediation

There is no fixed version for Debian:13 libgcrypt20.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libtasn1-6
  • Introduced through: libtasn1-6@4.20.0-2

Detailed paths

  • Introduced through: golang@latest libtasn1-6@4.20.0-2

NVD Description

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

Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.

Remediation

There is no fixed version for Debian:13 libtasn1-6.

References

low severity
new

Reachable Assertion

  • Vulnerable module: nghttp2/libnghttp2-14
  • Introduced through: nghttp2/libnghttp2-14@1.64.0-1.1

Detailed paths

  • Introduced through: golang@latest nghttp2/libnghttp2-14@1.64.0-1.1

NVD Description

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

nghttp2 is an implementation of the Hypertext Transfer Protocol version 2 in C. Prior to version 1.68.1, the nghttp2 library stops reading the incoming data when user facing public API nghttp2_session_terminate_session or nghttp2_session_terminate_session2 is called by the application. They might be called internally by the library when it detects the situation that is subject to connection error. Due to the missing internal state validation, the library keeps reading the rest of the data after one of those APIs is called. Then receiving a malformed frame that causes FRAME_SIZE_ERROR causes assertion failure. nghttp2 v1.68.1 adds missing state validation to avoid assertion failure. No known workarounds are available.

Remediation

There is no fixed version for Debian:13 nghttp2.

References

low severity

Out-of-bounds Read

  • Vulnerable module: openldap/libldap2
  • Introduced through: openldap/libldap2@2.6.10+dfsg-1

Detailed paths

  • Introduced through: golang@latest openldap/libldap2@2.6.10+dfsg-1

NVD Description

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

OpenLDAP Lightning Memory-Mapped Database (LMDB) versions up to and including 0.9.14, prior to commit 8e1fda8, contain a heap buffer underflow in the readline() function of mdb_load. When processing malformed input containing an embedded NUL byte, an unsigned offset calculation can underflow and cause an out-of-bounds read of one byte before the allocated heap buffer. This can cause mdb_load to crash, leading to a limited denial-of-service condition.

Remediation

There is no fixed version for Debian:13 openldap.

References

low severity
new

CVE-2026-3497

  • Vulnerable module: openssh/openssh-client
  • Introduced through: openssh/openssh-client@1:10.0p1-7+deb13u1

Detailed paths

  • Introduced through: golang@latest openssh/openssh-client@1:10.0p1-7+deb13u1

NVD Description

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

Vulnerability in the OpenSSH GSSAPI delta included in various Linux distributions. This vulnerability affects the GSSAPI patches added by various Linux distributions and does not affect the OpenSSH upstream project itself. The usage of sshpkt_disconnect() on an error, which does not terminate the process, allows an attacker to send an unexpected GSSAPI message type during the GSSAPI key exchange to the server, which will call the underlying function and continue the execution of the program without setting the related connection variables. As the variables are not initialized to NULL the code later accesses those uninitialized variables, accessing random memory, which could lead to undefined behavior. The recommended workaround is to use ssh_packet_disconnect() instead, which does terminate the process. The impact of the vulnerability depends heavily on the compiler flag hardening configuration.

Remediation

There is no fixed version for Debian:13 openssh.

References

low severity
new

CVE-2026-2673

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

Detailed paths

  • Introduced through: golang@latest openssl@3.5.5-1~deb13u1
  • Introduced through: golang@latest openssl/libssl3t64@3.5.5-1~deb13u1
  • Introduced through: golang@latest openssl/openssl-provider-legacy@3.5.5-1~deb13u1

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: An OpenSSL TLS 1.3 server may fail to negotiate the expected preferred key exchange group when its key exchange group configuration includes the default by using the 'DEFAULT' keyword.

Impact summary: A less preferred key exchange may be used even when a more preferred group is supported by both client and server, if the group was not included among the client's initial predicated keyshares. This will sometimes be the case with the new hybrid post-quantum groups, if the client chooses to defer their use until specifically requested by the server.

If an OpenSSL TLS 1.3 server's configuration uses the 'DEFAULT' keyword to interpolate the built-in default group list into its own configuration, perhaps adding or removing specific elements, then an implementation defect causes the 'DEFAULT' list to lose its 'tuple' structure, and all server-supported groups were treated as a single sufficiently secure 'tuple', with the server not sending a Hello Retry Request (HRR) even when a group in a more preferred tuple was mutually supported.

As a result, the client and server might fail to negotiate a mutually supported post-quantum key agreement group, such as 'X25519MLKEM768', if the client's configuration results in only 'classical' groups (such as 'X25519' being the only ones in the client's initial keyshare prediction).

OpenSSL 3.5 and later support a new syntax for selecting the most preferred TLS 1.3 key agreement group on TLS servers. The old syntax had a single 'flat' list of groups, and treated all the supported groups as sufficiently secure. If any of the keyshares predicted by the client were supported by the server the most preferred among these was selected, even if other groups supported by the client, but not included in the list of predicted keyshares would have been more preferred, if included.

The new syntax partitions the groups into distinct 'tuples' of roughly equivalent security. Within each tuple the most preferred group included among the client's predicted keyshares is chosen, but if the client supports a group from a more preferred tuple, but did not predict any corresponding keyshares, the server will ask the client to retry the ClientHello (by issuing a Hello Retry Request or HRR) with the most preferred mutually supported group.

The above works as expected when the server's configuration uses the built-in default group list, or explicitly defines its own list by directly defining the various desired groups and group 'tuples'.

No OpenSSL FIPS modules are affected by this issue, the code in question lies outside the FIPS boundary.

OpenSSL 3.6 and 3.5 are vulnerable to this issue.

OpenSSL 3.6 users should upgrade to OpenSSL 3.6.2 once it is released. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.6 once it is released.

OpenSSL 3.4, 3.3, 3.0, 1.0.2 and 1.1.1 are not affected by this issue.

Remediation

There is no fixed version for Debian:13 openssl.

References

low severity

CVE-2025-11468

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When folding a long comment in an email header containing exclusively unfoldable characters, the parenthesis would not be preserved. This could be used for injecting headers into email messages where addresses are user-controlled and not sanitized.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity
new

CVE-2025-13462

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The "tarfile" module would still apply normalization of AREGTYPE (\x00) blocks to DIRTYPE, even while processing a multi-block member such as GNUTYPE_LONGNAME or GNUTYPE_LONGLINK. This could result in a crafted tar archive being misinterpreted by the tarfile module compared to other implementations.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-15282

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

User-controlled data URLs parsed by urllib.request.DataHandler allow injecting headers through newlines in the data URL mediatype.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-15366

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The imaplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-15367

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The poplib module, when passed a user-controlled command, can have additional commands injected using newlines. Mitigation rejects commands containing control characters.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-6069

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The html.parser.HTMLParser class had worse-case quadratic complexity when processing certain crafted malformed inputs potentially leading to amplified denial-of-service.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-8194

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

There is a defect in the CPython “tarfile” module affecting the “TarFile” extraction and entry enumeration APIs. The tar implementation would process tar archives with negative offsets without error, resulting in an infinite loop and deadlock during the parsing of maliciously crafted tar archives.

This vulnerability can be mitigated by including the following patch after importing the “tarfile” module:  https://gist.github.com/sethmlarson/1716ac5b82b73dbcbf23ad2eff8b33e1

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2025-8291

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The 'zipfile' module would not check the validity of the ZIP64 End of Central Directory (EOCD) Locator record offset value would not be used to locate the ZIP64 EOCD record, instead the ZIP64 EOCD record would be assumed to be the previous record in the ZIP archive. This could be abused to create ZIP archives that are handled differently by the 'zipfile' module compared to other ZIP implementations.

Remediation maintains this behavior, but checks that the offset specified in the ZIP64 EOCD Locator record matches the expected value.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2026-0672

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When using http.cookies.Morsel, user-controlled cookie values and parameters can allow injecting HTTP headers into messages. Patch rejects all control characters within cookie names, values, and parameters.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2026-0865

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

User-controlled header names and values containing newlines can allow injecting HTTP headers.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity

CVE-2026-1299

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The email module, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't respect email folding rules, the new behavior will reject the incorrectly folded headers in "BytesGenerator".

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity
new

CVE-2026-2297

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The import hook in CPython that handles legacy *.pyc files (SourcelessFileLoader) is incorrectly handled in FileLoader (a base class) and so does not use io.open_code() to read the .pyc files. sys.audit handlers for this audit event therefore do not fire.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity
new

CVE-2026-3479

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

pkgutil.get_data() did not validate the resource argument as documented, allowing path traversals.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity
new

CVE-2026-3644

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The fix for CVE-2026-0672, which rejected control characters in http.cookies.Morsel, was incomplete. The Morsel.update(), |= operator, and unpickling paths were not patched, allowing control characters to bypass input validation. Additionally, BaseCookie.js_output() lacked the output validation applied to BaseCookie.output().

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity
new

CVE-2026-4224

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

When an Expat parser with a registered ElementDeclHandler parses an inline document type definition containing a deeply nested content model a C stack overflow occurs.

Remediation

There is no fixed version for Debian:13 python3.13.

References

low severity
new

CVE-2026-4519

  • Vulnerable module: python3.13
  • Introduced through: python3.13@3.13.5-2, python3.13/libpython3.13-minimal@3.13.5-2 and others

Detailed paths

  • Introduced through: golang@latest python3.13@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-minimal@3.13.5-2
  • Introduced through: golang@latest python3.13/libpython3.13-stdlib@3.13.5-2
  • Introduced through: golang@latest python3.13/python3.13-minimal@3.13.5-2

NVD Description

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

The webbrowser.open() API would accept leading dashes in the URL which could be handled as command line options for certain web browsers. New behavior rejects leading dashes. Users are recommended to sanitize URLs prior to passing to webbrowser.open().

Remediation

There is no fixed version for Debian:13 python3.13.

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: golang@latest shadow/login.defs@1:4.17.4-2
  • Introduced through: golang@latest 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
new

CVE-2025-70873

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

Detailed paths

  • Introduced through: golang@latest sqlite3/libsqlite3-0@3.46.1-7+deb13u1

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
new

Improper Privilege Management

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

Detailed paths

  • Introduced through: golang@latest systemd/libsystemd0@257.9-1~deb13u1
  • Introduced through: golang@latest systemd/libudev1@257.9-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, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

CVE-2026-3184

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/bsdutils@1:2.41-5 and others

Detailed paths

  • Introduced through: golang@latest util-linux@2.41-5
  • Introduced through: golang@latest util-linux/bsdutils@1:2.41-5
  • Introduced through: golang@latest util-linux/libblkid1@2.41-5
  • Introduced through: golang@latest util-linux/liblastlog2-2@2.41-5
  • Introduced through: golang@latest util-linux/libmount1@2.41-5
  • Introduced through: golang@latest util-linux/libsmartcols1@2.41-5
  • Introduced through: golang@latest util-linux/libuuid1@2.41-5
  • Introduced through: golang@latest util-linux/login@1:4.16.0-2+really2.41-5
  • Introduced through: golang@latest util-linux/mount@2.41-5

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

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

References