Vulnerabilities

289 via 577 paths

Dependencies

151

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
  • 35
  • 14
  • 236
Status
  • 289
  • 0
  • 0

critical severity
new

CVE-2026-111497

  • Vulnerable module: brotli/libbrotli1
  • Introduced through: brotli/libbrotli1@1.1.0-2+b7
  • Fixed in: 1.1.0-2+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › brotli/libbrotli1@1.1.0-2+b7

NVD Description

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

A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream.

Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1.

Remediation

Upgrade Debian:13 brotli to version 1.1.0-2+deb13u1 or higher.

References

critical severity

CVE-2026-8376

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have a heap buffer overflow when compiling regular expressions with a repeated fixed string on 32-bit builds.

Perl_study_chunk in regcomp_study.c checked the size of the joined substring buffer in characters rather than bytes. For a quantified fixed substring with a large minimum count, the byte length mincount * l could overflow SSize_t, producing an undersized SvGROW allocation; the subsequent copy writes past the end of the buffer.

A caller that compiles an attacker-controlled regular expression on a 32-bit perl build triggers a heap buffer overflow at compile time.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

critical severity

CVE-2026-13221

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.10 produce silently incorrect regular expression matches when an alternation of more than 65535 fixed string branches is compiled into a trie in Perl_study_chunk.

When such branches are combined into a trie, the delta between the first branch and the shared tail is stored in a 16-bit field. A branch count above 65535 overflows the field, and the trie's match decision table is truncated with no warning or error.

A pattern of this shape produces false positive matches (matching strings it should not) and false negative matches (failing to match strings it should). When such a pattern gates an access or filtering decision, the result is wrong.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

critical severity

CVE-2026-42496

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Archive::Tar versions before 3.08 for Perl extract symlinks with attacker controlled targets outside the extraction directory.

_make_special_file() passes the tar header's linkname to symlink() without validating it against absolute paths or .. segments. The secure-extract mode check that guards regular file extraction does not cover the symlink target.

A subsequent open through the extracted name reads or writes the attacker chosen path.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

high severity

Double Free

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
  • Fixed in: 1.11.1-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libssh2/libssh2-1t64@1.11.1-1+deb13u1

NVD Description

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

libssh2 through 1.11.1, fixed in commit 5e47761, contains a double-free vulnerability in the sftp_open() function in src/sftp.c that allows a malicious SSH server to corrupt the heap of any authenticated client opening an SFTP session. When a server responds to SSH_FXP_OPEN with SSH_FXP_STATUS containing FX_OK, the response data buffer is freed, and if a subsequent sftp_packet_require() call returns a specific error such as LIBSSH2_ERROR_CHANNEL_PACKET_EXCEEDED, the same pointer is freed a second time, enabling tcache dup conditions on glibc systems that allow overlapping allocations and function pointer overwrites.

Remediation

Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.

References

high severity

Release of Invalid Pointer or Reference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

A flaw was found in libxml2 with Python bindings enabled. A remote attacker could exploit this vulnerability by providing a specially crafted XML document containing a Document Type Definition (DTD) with enumerated attribute values. This triggers a double-free error in the SAX attributeDecl callback handler, where a string is freed twice. This flaw can lead to a denial of service (DoS) due to a reproducible crash in Python applications using the libxml2 SAX bindings.

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

CVE-2026-57432

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Perl versions before 5.40.5-RC1, from 5.41.0 before 5.42.3-RC1, from 5.43.0 before 5.43.11 have an integer overflow in S_measure_struct leading to an out-of-bounds heap read in pack and unpack.

S_measure_struct adds each item's size times its repeat count to a running total with no overflow check, so a large repeat count in a pack or unpack template wraps the signed SSize_t total negative. The @, X, and x position codes then guard their moves with a signed length comparison that passes when the length is negative, advancing the buffer pointer out of bounds.

A template derived from untrusted input can read heap memory past the buffer and return it to the caller.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

high severity
new

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.9.0-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 commit 13c5f63 contains a heap buffer over-read vulnerability in xmlparse.c. XML_ParseBuffer advances the parse buffer end with parser->m_bufferEnd += len using a caller-supplied length that is not validated against the allocated buffer size, so repeated XML_ParseBuffer calls move m_bufferEnd past the end of the heap allocation and subsequent parsing reads out of bounds. Reaching this path requires a parse buffer to already be present; otherwise XML_ParseBuffer returns XML_ERROR_NO_BUFFER. A buffer is present after a prior call to XML_GetBuffer, either directly (the common case) or indirectly through a prior XML_Parse call that allocates the buffer internally. The over-read discloses adjacent heap memory to the calling application, recovering heap pointers, libc function pointers, and code pointers sufficient to defeat ASLR and build further exploitation primitives.

Remediation

Upgrade Debian:13 expat to version 2.9.0-1~deb13u1 or higher.

References

high severity

Use After Free

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.9.0-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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.8.4 lacks handler call depth tracking with custom encoding callbacks. Thus, a use-after-free can occur. NOTE: this is similar to CVE-2026-50219, CVE-2026-56131 and CVE-2026-56412.

Remediation

Upgrade Debian:13 expat to version 2.9.0-1~deb13u1 or higher.

References

high severity

Out-of-bounds Write

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.19.0 through 1.21.2, a crafted HEIF file (uncompressed unci codec, tiled, component-interleaved, 4:2:0) triggers a heap out-of-bounds write in libheif's uncompressed tile decoder. The write overwrites the C++ vtable pointer of an adjacent unc_decoder_component_interleave object; the next virtual call dispatches to an attacker-chosen address. Version 1.22.0 patches the issue.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In libxml2 before 2.15.4, there is a heap-based buffer overflow in xmlXPtrEvalXPtrPart because of xmlXPtrEval xpointer length saturation.

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

Incorrect Resource Transfer Between Spheres

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In xinclude in libxml2 before 2.15.4, xmlXIncludeProcess and xmlXIncludeProcessTree do not propagate parseFlags. This has security relevance for, for example, the XML_PARSE_NONET flag, if (without it) a custom resource loader accesses the internet and triggers XML external entity injection, SSRF, or a denial of service (e.g., for an attacker-controlled internet resource that is intentionally slow).

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In libxml2 before 2.15.4, xmlURIEscapeStr in uri.c has an integer overflow.

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In libxml2 before 2.15.4, xmlDictAddQString in dict.c has an integer overflow and resultant heap-based buffer overflow.

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

Stack-based Buffer Overflow

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In libxml2 before 2.15.4, xmlSnprintfElements in valid.c has a strcat stack-based buffer overflow.

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

Free of Memory not on the Heap

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

In PCRE2 before 10.48, pcre2_jit_match mishandles a previously copied subject being passed in as a context. An incorrect free operation can occur.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

high severity

Heap-based Buffer Overflow

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

Detailed paths

  • Introduced through: nginx@mainline › 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.

SQLite before 3.53.2 contains memory corruption vulnerabilities in the FTS5 full-text search extension that allow attackers to cause process crashes, memory exhaustion, or arbitrary code execution by supplying a crafted database with malformed FTS5 page data. Attackers can trigger an out-of-bounds read in fts5LeafSeek() via an attacker-controlled loop bound and a heap buffer overflow write in fts5ChunkIterate() through a crafted continuation page causing an integer underflow, exploitable when an FTS5 MATCH query is executed against the malicious database.

Remediation

Upgrade Debian:13 sqlite3 to version 3.46.1-7+deb13u2 or higher.

References

high severity

Heap-based Buffer Overflow

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

Detailed paths

  • Introduced through: nginx@mainline › 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.

SQLite before 3.53.2 contains a heap-based buffer overflow vulnerability in the FTS5 full-text search extension that allows attackers to cause a crash or execute arbitrary code by supplying a crafted database with malicious continuation page metadata specifying a szLeaf value smaller than 4. Attackers can trigger an integer underflow in fts5ChunkIterate() causing an inflated remaining byte count during FTS5 MATCH query processing, leading to a heap buffer overflow of attacker-controlled data in applications compiled with SQLITE_ENABLE_FTS5.

Remediation

Upgrade Debian:13 sqlite3 to version 3.46.1-7+deb13u2 or higher.

References

high severity

CVE-2026-56208

  • Vulnerable module: aom/libaom3
  • Introduced through: aom/libaom3@3.12.1-1
  • Fixed in: 3.12.1-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › aom/libaom3@3.12.1-1

NVD Description

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

A heap buffer overflow vulnerability was found in libaom, the reference AV1 codec implementation. A flaw in the AV1 encoder's Look-Ahead Processing (LAP) mode causes the first-pass stats ring buffer wrap-around guard to be bypassed when g_lag_in_frames is set to 1 or higher. This results in a 232-byte out-of-bounds write on every encoded frame after the second, corrupting adjacent heap objects. An attacker who can influence encoder configuration in a transcoding service or WebRTC session could exploit this to cause a denial of service (process crash) or potentially achieve code execution.

Remediation

Upgrade Debian:13 aom to version 3.12.1-1+deb13u1 or higher.

References

high severity
new

Heap-based Buffer Overflow

  • Vulnerable module: cyrus-sasl2/libsasl2-2
  • Introduced through: cyrus-sasl2/libsasl2-2@2.1.28+dfsg1-9 and cyrus-sasl2/libsasl2-modules-db@2.1.28+dfsg1-9

Detailed paths

  • Introduced through: nginx@mainline › cyrus-sasl2/libsasl2-2@2.1.28+dfsg1-9
  • Introduced through: nginx@mainline › cyrus-sasl2/libsasl2-modules-db@2.1.28+dfsg1-9

NVD Description

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

A heap-based buffer overflow flaw was found in Cyrus SASL. The add_to_challenge() function in the DIGEST-MD5 plugin computes the size of the buffer needed for a challenge/response field before DIGEST-MD5 quoting is applied, but does not recompute that size when quoting (escaping special characters) makes the value longer. The under-sized buffer is then passed to strcat(), causing a heap-based out-of-bounds write whose size depends on attacker-controlled input. A malicious or on-path DIGEST-MD5 (or HTTP Digest) server can trigger this flaw in a connecting client by supplying a crafted challenge field, such as realm or nonce, most likely resulting in a crash of the client application.

Remediation

There is no fixed version for Debian:13 cyrus-sasl2.

References

high severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.9.0-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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.

Expat through 2.8.3 contains a denial of service vulnerability caused by quadratic algorithmic complexity in the storeAtts() function in xmlparse.c, where processing N specified attributes with non-normalized values triggers an O(N^2) linear scan of elementType->defaultAtts to determine CDATA status. A remote unauthenticated attacker can supply a single well-formed XML document of a few megabytes to an application parsing untrusted XML to cause excessive CPU consumption, resulting in denial of service without requiring authentication, external entity resolution, or non-default parser options.

Remediation

Upgrade Debian:13 expat to version 2.9.0-1~deb13u1 or higher.

References

high severity

Improper Handling of Unicode Encoding

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.9.0-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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.

Expat before 2.8.5 fails to validate that a high surrogate in UTF-16 input is followed by a low surrogate, allowing malformed UTF-16 sequences to be accepted. Attackers can supply UTF-16 encoded XML containing lone high surrogates that consume the following code unit, causing Expat to pass unpaired surrogates to applications built with XML_UNICODE and to silently replace input characters in other builds.

Remediation

Upgrade Debian:13 expat to version 2.9.0-1~deb13u1 or higher.

References

high severity

Unexpected Status Code or Return Value

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.9.0-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 2.8.2 and 2.8.3 before 2.8.4, misinterpretation of getentropy's return code leads to insufficient entropy, which results in being vulnerable to hash flooding attacks, causing a denial of service via crafted XML content.

Remediation

Upgrade Debian:13 expat to version 2.9.0-1~deb13u1 or higher.

References

high severity

Buffer Over-read

  • Vulnerable module: gzip
  • Introduced through: gzip@1.13-1
  • Fixed in: 1.13-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › gzip@1.13-1

NVD Description

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

GNU gzip contains a global buffer overflow vulnerability in the LZH decompression logic caused by improper reuse of shared global state between different decompression formats within a single execution. GNU gzip maintains a global array that is shared across the LZ77, LZW, and LZH decompression routines and is not reinitialized between files processed in the same invocation. By decompressing a specially crafted LZW file followed by a specially crafted LZH file in a single gzip -d command, an attacker can poison the shared global state and subsequently trigger an out‑of‑bounds read in the LZH decoder. The LZH decompression logic follows stale values left in the shared array, causing reads past the end of the allocated global buffer.

This issue has been fixed in commits 63dbf6b3b9e6e781df1a6a64e609b10e23969681 and e7378c2d421be6a286922374425680bbe9ad8b7d.

Remediation

Upgrade Debian:13 gzip to version 1.13-1+deb13u1 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.17, a malformed H.265 PPS NAL unit causes a segmentation fault in pic_parameter_set::set_derived_values(). This issue has been patched in version 1.0.17.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u2 or higher.

References

high severity

Heap-based Buffer Overflow

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
  • Fixed in: 1.11.1-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libssh2/libssh2-1t64@1.11.1-1+deb13u1

NVD Description

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

libssh2 through 1.11.1, fixed in commit 42e33d8, contains a pre-authentication heap buffer overflow vulnerability that allows a malicious SSH server to corrupt heap metadata in any connecting client by sending a packet with a packet_length smaller than the cipher's block size during Encrypt-then-MAC cipher negotiation. In the fullpacket() function in src/transport.c, the ETM path allocates a buffer of packet_length bytes but copies blocksize minus one bytes via memcpy, causing an overflow that on 32-bit glibc writes attacker-controlled bytes into an adjacent chunk's SIZE field, enabling tcache bin confusion, overlapping live objects, and function pointer overwrite during the session handshake before authentication.

Remediation

Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
  • Fixed in: 1.11.1-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libssh2/libssh2-1t64@1.11.1-1+deb13u1

NVD Description

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

libssh2 through 1.11.1 reads an attacker-controlled 32-bit attribute count from a publickey-subsystem response and uses it in the allocation num_attrs * sizeof(libssh2_publickey_attribute) without bounds checking, so on 32-bit platforms the multiplication overflows to an undersized buffer. A malicious SSH server can then drive the attribute-parsing loop to write past the allocation, causing a heap buffer overflow in a connecting libssh2 client.

Remediation

Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
  • Fixed in: 1.11.1-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libssh2/libssh2-1t64@1.11.1-1+deb13u1

NVD Description

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

libssh2 through 1.11.1, fixed in commit a13bb6c, contains a missing bounds check vulnerability that allows a malicious SSH server to trigger an arbitrary-length heap out-of-bounds read and a free of an uninitialized pointer via the publickey subsystem. In libssh2_publickey_list_fetch(), the version 1 response parser reads a server-controlled comment_len value and advances the parse pointer without verifying sufficient bytes remain in the buffer, causing the out-of-bounds read to leak heap pointers from adjacent allocations defeating ASLR, followed by heap allocator state corruption when the error cleanup path frees an uninitialized pointer from a non-zeroed realloc() region.

Remediation

Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
  • Fixed in: 1.11.1-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libssh2/libssh2-1t64@1.11.1-1+deb13u1

NVD Description

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

libssh2 through 1.11.1, fixed in commit a2ed82d, contains a pre-authentication integer underflow vulnerability in the ssh2_cipher_crypt() function in src/openssl.c that allows a malicious SSH server to crash any connecting client by negotiating AES-GCM ciphers during handshake. Attackers can exploit the underflow in the expression computing blocksize minus aadlen minus authentication tag length to trigger an out-of-bounds read and a memcpy call with a near-SIZE_MAX length argument, causing immediate process crash before any authentication occurs.

Remediation

Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.

References

high severity

CVE-2026-42497

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Archive::Tar versions before 3.08 for Perl extract hardlinks to attacker controlled paths outside the extraction directory.

_make_special_file() passes the tar header's linkname to link() without validating it against absolute paths or .. segments, creating a hardlink that shares the victim file's inode.

A subsequent write through the extracted name modifies the victim file, and the post-extraction chmod, chown, and utime block in _extract_file() (guarded only against symlinks via -l) applies the tar header's mode, owner, and timestamps to the shared inode during extraction alone.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

high severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

PCRE2 before 10.48, on 32-bit platforms, has a pcre2_pattern_convert out-of-bounds write when an attacker can provide a large pattern.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

high severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: nginx@mainline › 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 versions 1.3.1.2 through 1.3.2 contain a heap buffer overflow vulnerability in the gz_vacate() function when processing non-blocking gzwrite() operations with stale external buffer pointers. Attackers can trigger the overflow by calling gzprintf() or gzvprintf() after a write stall, causing an unchecked memmove() to write beyond the internal input buffer boundary.

Remediation

There is no fixed version for Debian:13 zlib.

References

high severity

Integer Coercion Error

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In xmlIO in libxml2 before 2.15.4, an inconsistency in xmlOutputWriteCallback and xmlBufUse causes negative lengths to reach write callbacks, aka a lack of a check for integer overflow before calling writecallback. This has security relevance for many types of uses of that length value within a callback.

Remediation

There is no fixed version for Debian:13 libxml2.

References

high severity

Link Following

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

Detailed paths

  • Introduced through: nginx@mainline › acl/libacl1@2.3.2-2+b1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 acl.

References

high severity

CVE-2026-56209

  • Vulnerable module: aom/libaom3
  • Introduced through: aom/libaom3@3.12.1-1
  • Fixed in: 3.12.1-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › aom/libaom3@3.12.1-1

NVD Description

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

An arbitrary address write vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows an attacker to inject an arbitrary pointer into the cyclic refresh map field via crafted image pixel values. The encoder then writes approximately 1,200 bytes at the attacker-controlled address. This is fully deterministic and does not require a separate information leak. An attacker who can supply frames to a network-facing libaom encoder with SVC enabled could exploit this for denial of service or potential code execution.

Remediation

Upgrade Debian:13 aom to version 3.12.1-1+deb13u1 or higher.

References

high severity

CVE-2026-56210

  • Vulnerable module: aom/libaom3
  • Introduced through: aom/libaom3@3.12.1-1
  • Fixed in: 3.12.1-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › aom/libaom3@3.12.1-1

NVD Description

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

A heap-buffer-overflow read vulnerability was found in libaom, the reference AV1 codec implementation. A missing bounds check in the SVC (Scalable Video Coding) layer ID control function allows setting a spatial_layer_id exceeding the configured number of layers. This causes an out-of-bounds heap read of approximately 40,728 bytes when computing a layer context array index. An attacker who can influence SVC encoder parameters in a network-facing service could exploit this for information disclosure (heap content leak) or denial of service (segmentation fault from hitting unmapped memory).

Remediation

Upgrade Debian:13 aom to version 3.12.1-1+deb13u1 or higher.

References

high severity

CVE-2026-56211

  • Vulnerable module: aom/libaom3
  • Introduced through: aom/libaom3@3.12.1-1
  • Fixed in: 3.12.1-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › aom/libaom3@3.12.1-1

NVD Description

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

A remote code execution vulnerability was found in libaom, the reference AV1 codec implementation. Insufficient bounds validation in the AV1 encoder's SVC (Scalable Video Coding) layer ID control allows an attacker to supply crafted video frame pixels that overlap with internal encoder layer context structures. In fork-based video processing services, an attacker can use this to hijack the cyclic refresh map pointer, brute-force the process base address via a crash oracle, and redirect control flow to achieve arbitrary command execution. Exploitation requires the target service to use libaom with SVC encoding enabled and accept attacker-supplied video frames.

Remediation

Upgrade Debian:13 aom to version 3.12.1-1+deb13u1 or higher.

References

high severity

Link Following

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

Detailed paths

  • Introduced through: nginx@mainline › attr/libattr1@1:2.5.2-3

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 attr.

References

high severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is an HEIF and AVIF file format decoder and encoder. Prior to version 1.21.0, a crafted HEIF that exercises the overlay image item path triggers a heap buffer over-read in HeifPixelImage::overlay(). The function computes a negative row length (likely from an unclipped overlay rectangle or invalid offsets), which then underflows when converted to size_t and is passed to memcpy, causing a very large read past the end of the source plane and a crash. Version 1.21.0 contains a patch. As a workaround, avoid decoding images using iovl overlay boxes.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

medium severity

Use of Uninitialized Resource

  • Vulnerable module: libssh2/libssh2-1t64
  • Introduced through: libssh2/libssh2-1t64@1.11.1-1+deb13u1
  • Fixed in: 1.11.1-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libssh2/libssh2-1t64@1.11.1-1+deb13u1

NVD Description

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

libssh2 through 1.11.1 grows its publickey list with SSH2_REALLOC but does not zero-initialize new entries before parsing populates them, so a parse failure reaching the cleanup path leaves libssh2_publickey_list_free operating on an uninitialized entry. A malicious SSH server offering the publickey subsystem can use a malformed response to make cleanup free an uninitialized, attacker-influenceable attrs pointer in a connecting libssh2 client.

Remediation

Upgrade Debian:13 libssh2 to version 1.11.1-1+deb13u2 or higher.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

PCRE2 before 10.48, on 32-bit platforms, has a pcre2_compile_32 integer overflow and resultant out-of-bounds write.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

PCRE2 before 10.48 has a pcre2_match out-of-bounds read during the PCRE2_MATCH_INVALID_UTF matching of an invalid UTF subject.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

medium severity

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

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

Detailed paths

  • Introduced through: nginx@mainline › acl/libacl1@2.3.2-2+b1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 acl.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

In libxml2 before 2.15.4, xmlFAParsePosCharGroup has an out-of-bounds read, aka an out-of-bounds read in the NXT macro in xmlregexp.

Remediation

There is no fixed version for Debian:13 libxml2.

References

medium severity

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.9.0-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 versions 2.7.2 through 2.8.5 contain an integer overflow vulnerability in expat_realloc() function on 32-bit platforms when computing allocation sizes. Attackers supplying malicious XML to applications parsing with vulnerable libexpat can cause heap buffer overflow, memory corruption, or denial of service.

Remediation

Upgrade Debian:13 expat to version 2.9.0-1~deb13u1 or higher.

References

medium severity
new

Integer Overflow or Wraparound

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 through 2.9.0 contains a signed integer overflow vulnerability in storeAtts() in lib/xmlparse.c that allows attackers to trigger out-of-bounds writes via oversized attribute counts. Attackers can supply a multi-gigabyte document with a start tag carrying over 2^30 attributes to overflow attIndex and nPrefixes, crashing applications or corrupting heap memory.

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.8.2-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 through 2.9.0 contains a NULL pointer dereference vulnerability in externalEntityInitProcessor2() in lib/xmlparse.c that mishandles the XML_TOK_NONE token from empty input. Attackers who control stream chunking can force an empty non-final first parse on an external entity subparser, causing a later parse to crash the application.

Remediation

There is no fixed version for Debian:13 expat.

References

medium severity

Out-of-bounds Read

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

PCRE2 before 10.48 has a pcre2_match out-of-bounds read after a JIT fallback when an attacker can provide invalid UTF data.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Versions prior to 1.22.0 crashes in the public C API heif_image_handle_get_image_tiling() when a malformed uncompressed HEIF image item has an associated uncC property but no associated ispe property. In debug builds this trips the ispe && uncC assertion in ImageItem_uncompressed::get_heif_image_tiling(). In a release/NDEBUG ASan build, the same file causes a null pointer read at address 0xa8. Version 1.22.0 fixes the issue.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

medium severity

NULL Pointer Dereference

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

A flaw was found in libxml2. A local user or an attacker providing a specially crafted XML catalog can trigger a NULL pointer dereference during XML catalog parsing. This occurs when a nextCatalog element lacks its mandatory catalog attribute, leading to the application crashing and causing a Denial of Service (DoS).

Remediation

There is no fixed version for Debian:13 libxml2.

References

medium severity

Use After Free

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.5-0+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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 libblkid library of util-linux. During nested partition probing, the BSD, Minix, Solaris x86, and UnixWare partition probers cache a raw pointer to a parent partition entry in a dynamically allocated array. When subsequent partition additions cause the array to be reallocated, this pointer becomes stale, leading to a heap use-after-free read. An attacker who can present a crafted block device image (for example, via USB insertion or a loop-mounted disk image) can trigger this flaw without user interaction, as libblkid is invoked automatically by udev/udisks as root on block-device hot-plug events. This could lead to limited information disclosure or denial of service.

Remediation

Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.

References

medium severity

Out-of-bounds Write

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u2

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.17, a crafted HEVC bitstream causes an out-of-bounds heap write confirmed by AddressSanitizer. The trigger is a stale ctb_info.log2unitSize after an SPS change where PicWidthInCtbsY and PicHeightInCtbsY stay constant but Log2CtbSizeY changes, causing set_SliceHeaderIndex to index past the allocated image metadata array and write 2 bytes past the end of a heap allocation. This issue has been patched in version 1.0.17.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u2 or higher.

References

medium severity

Insecure Temporary File

  • Vulnerable module: gzip
  • Introduced through: gzip@1.13-1
  • Fixed in: 1.13-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › gzip@1.13-1

NVD Description

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

GNU gzip contains a vulnerability in the gzexe utility related to insecure temporary file handling. When the mktemp utility is not available in the user’s PATH, gzexe falls back to constructing a temporary file path based solely on the process ID (PID). This predictable filename is created without exclusive access or existence checks. A local attacker can pre‑create the predicted temporary file path as a symbolic link pointing to an arbitrary file writable by the victim. When gzexe runs, it follows the symlink and overwrites the target file, resulting in a time‑of‑check to time‑of‑use (TOCTOU) condition that allows arbitrary file overwrite.

This issue has been fixed in the commit 4e6f8b24ab823146ab8776f0b7fe486ab34d4269

Remediation

Upgrade Debian:13 gzip to version 1.13-1+deb13u1 or higher.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

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-2026-6653

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

Use After Free in libxml2's xmlParseInternalSubset from GNOME libxml2 version 2.9.11 to 2.11.0 allows a remote attacker to cause a denial-of-service via maliciously crafted XML input with improper entity resolution handling.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

CVE-2005-2541

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

Detailed paths

  • Introduced through: nginx@mainline › tar@1.35+dfsg-3.1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

CVE-2019-1010023

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Missing Release of File Descriptor or Handle after Effective Lifetime

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

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/mount@2.41-5
  • Introduced through: nginx@mainline › util-linux/bsdutils@1:2.41-5
  • Introduced through: nginx@mainline › util-linux/login@1:4.16.0-2+really2.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.

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

Remediation

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

References

low severity

Stack-based Buffer Overflow

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

libxml2 is vulnerable to multiple stack-based buffer overflows in the xmlcatalog utility when running in --shell mode. The usershell() function processes user input using fixed-size stack buffers without proper bounds checking. By supplying an overly long input line, an attacker can overflow internal buffers (command, arg, and argv) during input parsing. This results in memory corruption within the stack frame. Successful exploitation may cause a crash or potentially allow arbitrary code execution in the context of the xmlcatalog process.

This issue has been fixed in the commit c2e233fc.

NOTE: The maintainers of this project did not agree that this issue is a vulnerability and considered it a bug.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

Stack-based Buffer Overflow

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

Detailed paths

  • Introduced through: nginx@mainline › ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: nginx@mainline › ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: nginx@mainline › 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

Out-of-Bounds

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

A vulnerability was found in LibTIFF up to 4.7.0. It has been declared as critical. This vulnerability affects the function get_histogram of the file tools/tiffmedian.c. The manipulation leads to use after free. The attack needs to be approached locally. The exploit has been disclosed to the public and may be used. The patch is identified as fe10872e53efba9cc36c66ac4ab3b41a839d5172. It is recommended to apply a patch to fix this issue.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

A vulnerability was found in LibTIFF up to 4.7.0. It has been rated as critical. This issue affects the function setrow of the file tools/thumbnail.c. The manipulation leads to buffer overflow. An attack has to be approached locally. The patch is named e8c9d6c616b19438695fd829e58ae4fde5bfbc22. It is recommended to apply a patch to fix this issue. This vulnerability only affects products that are no longer supported by the maintainer.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Detection of Error Condition Without Action

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

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/mount@2.41-5
  • Introduced through: nginx@mainline › util-linux/bsdutils@1:2.41-5
  • Introduced through: nginx@mainline › util-linux/login@1:4.16.0-2+really2.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.

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

Remediation

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

References

low severity

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

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

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/mount@2.41-5
  • Introduced through: nginx@mainline › util-linux/bsdutils@1:2.41-5
  • Introduced through: nginx@mainline › util-linux/login@1:4.16.0-2+really2.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. Restricted bind mounts take the source path from fstab but do not pin that source before the privileged mount. A local unprivileged user who can replace the authorized source or a writable ancestor can redirect SUID mount(8) to bind another host directory. If the fstab entry also sets X-mount.owner, X-mount.group, or X-mount.mode, root then changes ownership or mode on that redirected inode.

Remediation

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

References

low severity
new

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@mainline › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: nginx@mainline › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: nginx@mainline › gcc-14/libgomp1@14.2.0-19
  • Introduced through: nginx@mainline › gcc-14/libstdc++6@14.2.0-19

NVD Description

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

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

Remediation

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

References

low severity
new

Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 through 2.9.0 contains a denial of service vulnerability because billion laughs protection in accountingDiffTolerated() in xmlparse.c detects entity amplification too late. Attackers can supply a moderately sized XML document with a large DTD and nested entity expansions to consume tens of seconds of CPU per parse.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity

Uncontrolled Recursion

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

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+deb13u3 and glibc/libc6@2.41-12+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

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

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@mainline › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libk5crypto3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5-3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5support0@1.21.3-5+deb13u1

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+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libgcrypt20@1.11.0-7+deb13u1

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: nginx@mainline › 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: nginx@mainline › 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

CVE-2026-9538

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

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

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

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

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

Missing Release of Resource after Effective Lifetime

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

LibTIFF 4.0.8 has multiple memory leak vulnerabilities, which allow attackers to cause a denial of service (memory consumption), as demonstrated by tif_open.c, tif_lzw.c, and tif_aux.c. NOTE: Third parties were unable to reproduce the issue

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Access Restriction Bypass

  • Vulnerable module: nginx
  • Introduced through: nginx@1.31.3-1~trixie

Detailed paths

  • Introduced through: nginx@mainline › nginx@1.31.3-1~trixie

NVD Description

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

The default configuration of nginx, possibly 1.3.13 and earlier, uses world-readable permissions for the (1) access.log and (2) error.log files, which allows local users to obtain sensitive information by reading the files.

Remediation

There is no fixed version for Debian:13 nginx.

References

low severity

Out-of-Bounds

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

libtiff up to v4.7.1 was discovered to contain a stack overflow via the readSeparateStripsIntoBuffer function.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity
new

Expired Pointer Dereference

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

Detailed paths

  • Introduced through: nginx@mainline › gcc-14/gcc-14-base@14.2.0-19
  • Introduced through: nginx@mainline › gcc-14/libgcc-s1@14.2.0-19
  • Introduced through: nginx@mainline › gcc-14/libgomp1@14.2.0-19
  • Introduced through: nginx@mainline › gcc-14/libstdc++6@14.2.0-19

NVD Description

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

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

Remediation

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

References

low severity

Link Following

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

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/mount@2.41-5
  • Introduced through: nginx@mainline › util-linux/bsdutils@1:2.41-5
  • Introduced through: nginx@mainline › util-linux/login@1:4.16.0-2+really2.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.

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

Remediation

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

References

low severity

Out-of-Bounds

  • Vulnerable module: jbigkit/libjbig0
  • Introduced through: jbigkit/libjbig0@2.1-6.1+b2

Detailed paths

  • Introduced through: nginx@mainline › jbigkit/libjbig0@2.1-6.1+b2

NVD Description

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

In LibTIFF 4.0.8, there is a memory malloc failure in tif_jbig.c. A crafted TIFF document can lead to an abort resulting in a remote denial of service attack.

Remediation

There is no fixed version for Debian:13 jbigkit.

References

low severity
new

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: nginx@mainline › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libk5crypto3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5-3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5support0@1.21.3-5+deb13u1

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.

MIT Kerberos 5 (krb5) through 1.22.2 contains a NULL pointer dereference in make_cred_list() in rd_cred.c that allows authenticated Kerberos clients to crash services by sending mismatched KRB-CRED arrays. Attackers can send forwarded credentials with more tickets than ticket_info entries through gss_accept_sec_context() to crash GSS-API acceptor services, causing denial of service.

Remediation

There is no fixed version for Debian:13 krb5.

References

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff 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 LibTIFF 4.3.0. Affected by this vulnerability is the TIFF File Handler of tiff2ps. Opening a malicious file leads to a denial of service. The attack can be launched remotely but requires user interaction. The exploit has been disclosed to the public and may be used.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

ijg-libjpeg before 9d, as used in tiff2pdf (from LibTIFF) and other products, does not check for a NULL pointer at a certain place in jpeg_fdct_16x16 in jfdctint.c.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

CVE-2009-4487

  • Vulnerable module: nginx
  • Introduced through: nginx@1.31.3-1~trixie

Detailed paths

  • Introduced through: nginx@mainline › nginx@1.31.3-1~trixie

NVD Description

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

nginx 0.7.64 writes data to a log file without sanitizing non-printable characters, which might allow remote attackers to modify a window's title, or possibly execute arbitrary commands or overwrite files, via an HTTP request containing an escape sequence for a terminal emulator.

Remediation

There is no fixed version for Debian:13 nginx.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.25.5-3

Detailed paths

  • Introduced through: nginx@mainline › p11-kit/libp11-kit0@0.25.5-3

NVD Description

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

A flaw was found in p11-kit. A local attacker, or one with equivalent access to a reachable RPC channel, could exploit an integer overflow vulnerability. By sending specially crafted messages, the attacker can cause the system to miscalculate memory allocation for nested attributes. This leads to a memory corruption issue, specifically a heap out-of-bounds write, which can crash the p11-kit RPC parsing process, resulting in a Denial of Service (DoS). This vulnerability is only exploitable on 32 bit systems.

Remediation

There is no fixed version for Debian:13 p11-kit.

References

low severity

Uncontrolled Recursion

  • Vulnerable module: p11-kit/libp11-kit0
  • Introduced through: p11-kit/libp11-kit0@0.25.5-3

Detailed paths

  • Introduced through: nginx@mainline › p11-kit/libp11-kit0@0.25.5-3

NVD Description

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

A flaw was found in p11-kit. The RPC message attribute parsing functions p11_rpc_message_get_attribute() and p11_rpc_message_get_attribute_array_value() form a mutually-recursive call chain with no recursion depth limit when processing nested CKA_WRAP_TEMPLATE, CKA_UNWRAP_TEMPLATE, and CKA_DERIVE_TEMPLATE attributes. An unauthenticated attacker with local access to the p11-kit RPC Unix domain socket can send a specially crafted request with deeply nested template attributes, causing stack exhaustion and crashing the p11-kit server process and its dependent services.

Remediation

There is no fixed version for Debian:13 p11-kit.

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: nginx@mainline › shadow/login.defs@1:4.17.4-2
  • Introduced through: nginx@mainline › shadow/passwd@1:4.17.4-2

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 shadow.

References

low severity

Heap-based Buffer Overflow

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

Detailed paths

  • Introduced through: nginx@mainline › coreutils@9.7-3

NVD Description

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

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

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

This issue has been fixed in the commit b60a159fdc5bfcf9988d3a4cb6f53abe8ad5d35d

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: nginx@mainline › coreutils@9.7-3

NVD Description

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

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

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

This issue has been fixed in the commit d64e35a8a4c0e4608321433e0d84d917e4e36371.

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

A flaw was found in libtiff. A heap-buffer overflow vulnerability exists in the tiff2pdf utility due to an integer truncation error when processing crafted BigTIFF files. An attacker can provide a specially crafted BigTIFF file, causing a 64-bit StripByteCounts value to be truncated to a 32-bit integer. This leads to an undersized memory allocation and a subsequent out-of-bounds memory copy, resulting in a crash and severe memory corruption.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Out-of-bounds Read

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.3-1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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

Upgrade Debian:13 util-linux to version 2.41.3-1 or higher.

References

low severity
new

Missing Initialization of Resource

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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 2.7.2 through 2.9.0 contains a denial of service vulnerability because XML_ParserReset zeroes the direct byte count but never offsets tracked heap allocations. Attackers can submit a large XML document so later documents on the same reset parser fail with XML_ERROR_NO_MEMORY until it is recreated.

Remediation

There is no fixed version for Debian:13 expat.

References

low severity
new

Inefficient Regular Expression Complexity

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

Detailed paths

  • Introduced through: nginx@mainline › dash@0.5.12-12

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 dash.

References

low severity

Algorithmic Complexity

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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
new

Resource Exhaustion

  • Vulnerable module: freetype/libfreetype6
  • Introduced through: freetype/libfreetype6@2.13.3+dfsg-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › freetype/libfreetype6@2.13.3+dfsg-1+deb13u1

NVD Description

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

A flaw was found in FreeType, specifically within its CID font loader. A remote attacker could exploit this vulnerability by tricking a user into opening content that embeds or references a specially crafted CID-keyed font. This crafted font can cause repeated allocations and decryptions of subroutine data across multiple font dictionaries, leading to excessive memory and CPU consumption. This can result in a denial of service (DoS) for the application or service processing the font, potentially causing it to hang or terminate.

Remediation

There is no fixed version for Debian:13 freetype.

References

low severity

Buffer Overflow

  • Vulnerable module: libpng1.6/libpng16-16t64
  • Introduced through: libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

Detailed paths

  • Introduced through: nginx@mainline › libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

NVD Description

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

A heap overflow flaw was found in libpngs' pngimage.c program. This flaw allows an attacker with local network access to pass a specially crafted PNG file to the pngimage utility, causing an application to crash, leading to a denial of service.

Remediation

There is no fixed version for Debian:13 libpng1.6.

References

low severity

Expired Pointer Dereference

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.35-1.2+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxslt/libxslt1.1@1.1.35-1.2+deb13u3

NVD Description

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

A use-after-free vulnerability was found in libxslt while parsing xsl nodes that may lead to the dereference of expired pointers and application crash.

Remediation

There is no fixed version for Debian:13 libxslt.

References

low severity

Unrestricted Upload of File with Dangerous Type

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

Detailed paths

  • Introduced through: nginx@mainline › tar@1.35+dfsg-3.1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

NULL Pointer Dereference

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

libtiff up to v4.7.1 was discovered to contain a NULL pointer dereference via the component libtiff/tif_open.c.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/mount@2.41-5
  • Introduced through: nginx@mainline › util-linux/bsdutils@1:2.41-5
  • Introduced through: nginx@mainline › util-linux/login@1:4.16.0-2+really2.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: nginx@mainline › 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

HTTP Request Smuggling

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

Detailed paths

  • Introduced through: nginx@mainline › nghttp2/libnghttp2-14@1.64.0-1.1+deb13u1

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's nghttpx proxy through 1.69.0 forwards an HTTP/1.1 Upgrade request that also carries a Content-Length header and body onto reusable keep-alive backend connections, re-adding the Upgrade and Connection headers while passing Content-Length verbatim. A backend that resolves the resulting ambiguous message in the attacker's favor enables HTTP request/response smuggling and cross-client response-queue poisoning.

Remediation

There is no fixed version for Debian:13 nghttp2.

References

low severity

Information Exposure

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

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+deb13u3 and glibc/libc6@2.41-12+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

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

Out-of-Bounds

  • Vulnerable module: libpng1.6/libpng16-16t64
  • Introduced through: libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

Detailed paths

  • Introduced through: nginx@mainline › libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

NVD Description

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

A flaw has been found in pnggroup libpng up to 1.6.55. Affected by this vulnerability is the function do_pnm2png of the file contrib/pngminus/pnm2png.c of the component pnm2png. This manipulation of the argument width/height causes heap-based buffer overflow. The attack is restricted to local execution. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Remediation

There is no fixed version for Debian:13 libpng1.6.

References

low severity

Use of Insufficiently Random Values

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.35-1.2+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxslt/libxslt1.1@1.1.35-1.2+deb13u3

NVD Description

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

In libxslt 1.1.29 and earlier, the EXSLT math.random function was not initialized with a random seed during startup, which could cause usage of this function to produce predictable outputs.

Remediation

There is no fixed version for Debian:13 libxslt.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Improper Validation of Integrity Check Value

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Authentication Bypass

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

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/mount@2.41-5
  • Introduced through: nginx@mainline › util-linux/bsdutils@1:2.41-5
  • Introduced through: nginx@mainline › util-linux/login@1:4.16.0-2+really2.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. Improper hostname canonicalization in the login(1) utility, when invoked with the -h option, can modify the supplied remote hostname before setting PAM_RHOST. A remote attacker could exploit this by providing a specially crafted hostname, potentially bypassing host-based Pluggable Authentication Modules (PAM) access control rules that rely on fully qualified domain names. This could lead to unauthorized access.

Remediation

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

References

low severity

Integer Underflow

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

Detailed paths

  • Introduced through: nginx@mainline › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libk5crypto3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5-3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5support0@1.21.3-5+deb13u1

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 integer underflow vulnerability was found in MIT krb5 in the berval2tl_data() function in plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c. The function performs an unsigned subtraction (bv_len - 2) without a prior bounds check. When bv_len is 0 or 1, the subtraction wraps to a large value which is then truncated to uint16_t, yielding 0xFFFE (65534) or 0xFFFF (65535). The subsequent malloc succeeds and memcpy reads up to 65534 bytes from a 0-1 byte buffer, resulting in a heap out-of-bounds read. The attack vector involves a malicious or compromised LDAP KDB backend returning a krbExtraData attribute with bv_len < 2, triggering the underflow when the KDC or kadmind reads principal data.

Remediation

There is no fixed version for Debian:13 krb5.

References

low severity

Double Free

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

libtiff up to v4.7.1 was discovered to contain a double free via the component tools/tiffcrop.c.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity
new

NULL Pointer Dereference

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

Detailed paths

  • Introduced through: nginx@mainline › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libk5crypto3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5-3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5support0@1.21.3-5+deb13u1

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.

MIT krb5 through 1.22.2 contains a NULL pointer dereference vulnerability in the KDC's get_pac_princ_with_realm() that returns success while leaving the client principal NULL on malformed names. A malicious or compromised cross-realm trusted KDC can send an S4U2Proxy request with a PAC carrying a malformed client name to crash krb5kdc and deny authentication.

Remediation

There is no fixed version for Debian:13 krb5.

References

low severity

Race Condition

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

Detailed paths

  • Introduced through: nginx@mainline › 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 Initialization

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

Detailed paths

  • Introduced through: nginx@mainline › 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: nginx@mainline › coreutils@9.7-3

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 coreutils.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: nginx@mainline › tar@1.35+dfsg-3.1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

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

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

Detailed paths

  • Introduced through: nginx@mainline › tar@1.35+dfsg-3.1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 tar.

References

low severity

Resource Management Errors

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

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+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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

Memory Leak

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

Detailed paths

  • Introduced through: nginx@mainline › 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: nginx@mainline › 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
new

Out-of-bounds Write

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

Detailed paths

  • Introduced through: nginx@mainline › dash@0.5.12-12

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 dash.

References

low severity

Improper Verification of Cryptographic Signature

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

Detailed paths

  • Introduced through: nginx@mainline › apt@3.0.3
  • Introduced through: nginx@mainline › 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

Out-of-Bounds

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.1-1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

A vulnerability was determined in strukturag libheif up to 1.21.2. This affects the function vvdec_push_data2 of the file libheif/plugins/decoder_vvdec.cc of the component HEIF File Parser. Executing a manipulation of the argument size can lead to out-of-bounds read. The attack needs to be launched locally. The exploit has been publicly disclosed and may be utilized. This patch is called b97c8b5f198b27f375127cd597a35f2113544d03. It is advisable to implement a patch to correct this issue.

Remediation

Upgrade Debian:13 libheif to version 1.23.1-1 or higher.

References

low severity

Unchecked Return Value

  • Vulnerable module: libxml2
  • Introduced through: libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxml2@2.12.7+dfsg+really2.9.14-2.1+deb13u3

NVD Description

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

xmlregexp in libxml2 before 2.15.4 has a NULL pointer dereference in xmlRegNewParserCtxt after a strdup failure, i.e., it does not calculate a string length after NULL checking.

Remediation

There is no fixed version for Debian:13 libxml2.

References

low severity

Out-of-Bounds

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

Detailed paths

  • Introduced through: nginx@mainline › ncurses/libtinfo6@6.5+20250216-2
  • Introduced through: nginx@mainline › ncurses/ncurses-base@6.5+20250216-2
  • Introduced through: nginx@mainline › 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

Incorrect Resource Transfer Between Spheres

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available to the adversary is already unsafe.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

low severity

Link Following

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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

Incorrect Resource Transfer Between Spheres

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

Access of Resource Using Incompatible Type ('Type Confusion')

  • Vulnerable module: libxslt/libxslt1.1
  • Introduced through: libxslt/libxslt1.1@1.1.35-1.2+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › libxslt/libxslt1.1@1.1.35-1.2+deb13u3

NVD Description

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

A flaw was found in the exsltFuncResultComp() function of libxslt, which handles EXSLT <func:result> elements during stylesheet parsing. Due to improper type handling, the function may treat an XML document node as a regular XML element node, resulting in a type confusion. This can cause unexpected memory reads and potential crashes. While difficult to exploit, the flaw could lead to application instability or denial of service.

Remediation

There is no fixed version for Debian:13 libxslt.

References

low severity

Improper Resource Shutdown or Release

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

Note: Versions mentioned in the description apply only to the upstream tiff package and not the tiff 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 libtiff 4.6.0. This vulnerability affects the function PS_Lvl2page of the file tools/tiff2ps.c of the component tiff2ps. The manipulation leads to null pointer dereference. It is possible to launch the attack on the local host. 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 6ba36f159fd396ad11bf6b7874554197736ecc8b. It is recommended to apply a patch to fix this issue. One of the maintainers explains, that "[t]his error only occurs if DEFER_STRILE_LOAD (defer-strile-load:BOOL=ON) or TIFFOpen( .. "rD") option is used."

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: nginx@mainline › bzip2/libbz2-1.0@1.0.8-6

NVD Description

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

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

This issue was fixed in bzip2 patch 35d122a3df8b0cc4082a4d89fdc6ee99f375fe67

Remediation

There is no fixed version for Debian:13 bzip2.

References

low severity

Authentication Bypass

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

Successfully using libcurl to do a transfer to a specific HTTP origin (hostA) with Digest authentication and then changing the origin to a different one (hostB) for a second transfer, reusing the same handle, makes libcurl wrongly pass on the Authorization: header field meant for hostA, to hostB.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Authentication Bypass

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
  • Fixed in: 8.14.1-2+deb13u7

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 reusing a libcurl handle for sequential transfers driven by environment-variable proxy configuration, libcurl fails to clear the proxy authentication state between requests. Specifically, if the initial transfer authenticates against proxyA using Digest auth, a subsequent transfer routed through proxyB erroneously leaks the Proxy-Authorization: header intended solely for proxyA.

Remediation

Upgrade Debian:13 curl to version 8.14.1-2+deb13u7 or higher.

References

low severity

CVE-2025-10966

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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-14017

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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-15079

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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-107928

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 curl is built with GnuTLS, a malicious WebSocket server can make curl send memory past its send buffer. This is due to an out of bounds read following when gnutls_record_send() returns a number of bytes sent greater than the number of bytes it was given to send. GnuTLS does that after a blocked send.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-107929

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 CURLOPT_INTERFACE (or the command line tool's --interface option) is set with one of the documented prefixes (if!, host!, ifhost!), that binding is not part of the connection reuse key, so a later transfer asking for a different source can silently reuse an existing connection and go out from the earlier transfer's source address

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-13608

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A flaw in the libcurl SASL negotiation for LDAP authentication allows an incomplete handshake sequence to be misinterpreted as a successful cryptographic verification. An attacker executing a Man-in-the-Middle (MITM) attack can inject a premature or shortcut response that bypasses complete peer validation.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-18924

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A flaw in libcurl's handling of HTTP/2 Server Push streams, when the parent handle is set to share connections with other handles, can lead to use-after-free in the cleanup process.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-19931

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given hostname using Negotiate authentication, when the initial request is done using empty credentials. This can make user B's request get sent over user A's previously authenticated connection.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-80229

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 performing transfers via libcurl’s multi interface, pooled TLS connections can outlive their originating easy handles. In OpenSSL 3 provider configurations, libcurl attaches an allocated library context to the easy handle's state and passes it to OpenSSL without acquiring an ownership reference; destroying the easy handle prematurely frees this context while the active connection retains a dangling pointer, leading to a heap-use-after-free upon subsequent I/O or post-handshake operations.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-80230

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 CURLOPT_PINNEDPUBLICKEY is configured alongside options that disable standard peer verification (CURLOPT_SSL_VERIFYPEER = 0 and CURLOPT_SSL_VERIFYHOST = 0), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-80255

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A Set-Cookie: header using tab (horizontal tab, ASCII code 9) instead of space (ascii code 32) immediately before the Secure attribute causes curl to store the cookie without its Secure flag. The cookie might then wrongfully be sent over plaintext HTTP on subsequent requests to the same host.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-82208

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

With the wolfSSL backend, when CA caching is enabled and an CURLOPT_SSL_CTX_FUNCTION callback replaces the trust store, libcurl can silently reinstall the cached store after the callback returns. A certificate trusted by the cached store but rejected by the callback-selected store is then incorrectly accepted.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-82209

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 libpsl support is enabled, libcurl fails to enforce the Public Suffix List boundary check when processing a Set-Cookie header where the Domain attribute explicitly matches an origin host that is itself a public suffix (e.g., Domain=co.uk set by co.uk).

Instead of coercing it into a strict host-only cookie, libcurl saves the cookie with wildcard domain scope (.co.uk). Consequently, the cookie is inappropriately included in subsequent outbound requests or HTTP redirects to arbitrary sibling subdomains under the same public suffix (e.g., attacker.co.uk).

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-8458

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 might in some circumstances reuse the wrong connection when asked to do Negotiate-authenticated ones, even when they are set to use different "services".

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 criteria must 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 services.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-86409

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

Setting CURLOPT_AWS_SIGV4 to NULL but does not disable SigV4 authentication, contrary to expectations and documentation. A subsequent transfer on the same handle still sends an Authorization: AWS4-HMAC-SHA256 header to whatever URL isset next, leaking state information.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-86410

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A flaw in the curl command line tool's logic makes it only set SSH host verification options when interacting directly using SFTP or SCP, and not as a result of following a redirect.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-86414

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

An HTTP proxy can trick libcurl into sending the origin's credentials (Basic password, or a Negotiate/Kerberos ticket) to the proxy itself, by answering the CONNECT tunnel request with 401 WWW-Authenticate: instead of the expected 407 Proxy-Authenticate:.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-87862

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

Importing a includeSubDomains parent HSTS entry before a longer-lived child entry, silently drops the child. Consequently, when the parent expires, the child's valid HSTS policy is lost, causing curl to issue unencrypted HTTP requests rather than upgrading to HTTPS.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-87863

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

An authenticated HTTPS origin can supply an HSTS max-age value that the parser accepts, but time serialization later fails to process. On 64-bit systems, extreme max-age values compute an absolute expiry within standard time integer limits that exceeds calendar time structure bounds. During cache saves, the original HSTS file is truncated before writing a temporary replacement; when serialization fails, the temporary file is deleted, leaving an empty or partial cache. Because the save error is silently ignored during cleanup, curl exits successfully despite the data loss.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-87864

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

Enabling CURLOPT_CRLF causes curl to advertise the raw input byte count in the IMAP APPEND {N} literal while transmitting line-ending expanded data. The server reads only $N$ bytes for the payload, causing the remaining overflow bytes to be interpreted and executed as pipelined IMAP commands within the authenticated session.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-87865

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 libcurl uses libssh2 with a hashed known_hosts file, an unrelated initial entry can cause host key validation to report a key mismatch as a missing key to the CURLOPT_SSH_KEYFUNCTION callback.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-87866

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 built with wolfSSL, curl can successfully validate a pinned public key hash against a key the TLS peer does not possess. During the TLS handshake, wolfSSL validates the connection, but curl's subsequent re-parsing of the same certificate - tricked by a manipulated validity length field - extracts and matches a different embedded key, incorrectly authorizing the pinned public key.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-8924

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
  • Fixed in: 8.14.1-2+deb13u7

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public Suffix List check. This enables an attacker-controlled origin to inject cookies that curl subsequently scopes and transmits to unrelated third-party domains.

Remediation

Upgrade Debian:13 curl to version 8.14.1-2+deb13u7 or higher.

References

low severity

CVE-2026-8932

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 would reuse a previously created connection even when some mTLS config related option had been changed that should have prohibited reuse.

libcurl keeps previously used connections in a connection pool for subsequent transfers to reuse if one of them matches the setup. However, some TLS settings related to client certificates were left out from the configuration match checks, making them match too easily. In particular options related to the private key.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92386

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 writing a long cookie name and value to a Netscape cookie jar, a remote HTTP server can make curl write a record that exceeds its line-length parsing limit. Consequently, any subsequent curl invocation reading from that same cookie jar using --cookie silently aborts parsing prematurely upon encountering the too long line, ignoring all subsequent valid cookies in the file.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92387

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

By permanently omitting the final control-response line, a malicious FTP, IMAP, POP3, or SMTP server can exploit libcurl and completely bypass its configured transfer timeout mechanism, indefinitely blocking all concurrent transfers bound to the same multi-handle.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92388

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 FTP wildcard LIST operation fails, libcurl omits the restoration path meant for successful listings, leaving the write callback set to the internal listing parser and the write callback data pointing directly to the easy handle. Subsequent reuse of this handle triggers an immediate crash, and cloning it via curl_easy_duphandle() copies this corrupted state into the duplicate. If the original handle is subsequently freed, executing a transfer on the cloned handle causes a heap use-after-free read against the dangling handle reference; alternatively, reusing the original or cloned handle while changing only CURLOPT_WRITEDATA (and omitting CURLOPT_WRITEFUNCTION) results in type confusion, forcing the internal parser to interpret incoming server response bytes into memory at the application-supplied write data pointer.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92389

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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's TFTP state machine fails to validate state transitions against the requested transfer direction, accepting opening server responses for both reads and writes interchangeably. A malicious TFTP server can respond to a download request in a way that forces the client into transmit mode, prompting libcurl to consume and transmit data from the handle's persistent CURLOPT_READDATA pointer - including data remaining from unrelated prior operations, such as an HTTP POST request executed on a reused handle.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92390

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 invoked with --remote-header-name (-J), curl fails to preserve its documented anti-clobbering protection if an intermediate 103 Early Hints response precedes the final HTTP response, or if an ETag header is processed before Content-Disposition under --etag-save. This flaw allows an HTTP(S) server to overwrite an existing local file specified in the Content-Disposition header despite the presence of the -J non-overwrite constraint.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92391

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A deeply nested multipart MIME structure constructed via the public API causes a stack overflow in libcurl during normal cleanup operations. An excessive recursion depth within curl_mime_free leads to unbounded stack frame allocation during structure traversal, ultimately crashing the host process.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity
new

CVE-2026-92392

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
  • Fixed in: 8.14.1-2+deb13u7

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

During an upload, curl mishandles HTTP/2 RST_STREAM received from the server (with reason HTTP_1_1_REQUIRED or REFUSED_STREAM) leading to a use after free of a struct Curl_easy object.

Remediation

Upgrade Debian:13 curl to version 8.14.1-2+deb13u7 or higher.

References

low severity
new

CVE-2026-94266

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 could accidentally return a URL for curl_easy_getinfo()'s CURLINFO_EFFECTIVE_URL option containing credentials, even though neither the URL provided to libcurl nor the redirected URL did.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-9545

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker's impostor machine - without a valid certificate.

When libcurl returns to the hostname the second time with a cached SSL session (CURLOPT_SSL_SESSIONID_CACHE is not disabled) and early data enabled (the CURLSSLOPT_EARLYDATA bit is set in CURLOPT_SSL_OPTIONS), libcurl might send off the second request's bytes on that new connection before enforcing the certificate verification failure. Potentially leaking sensitive information.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

CVE-2026-9547

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 a libcurl-based application performs transfers via SCP:// or SFTP:// and utilizes the CURLOPT_SSH_KEYFUNCTION callback, it may silently accept an untrusted server. This vulnerability occurs when a server presents a host key type that does not match the specific key type already recorded for that host in the known_hosts file. Instead of rejecting the mismatch, the callback mechanism fails to properly enforce the restriction, allowing the connection to succeed without warning and risking a potential man-in-the-middle attack.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 a user invokes curl using a schemeless URL combined with --proto-default sftp (or scp), a disconnect occurs between the tool layer and libcurl. The tool layer incorrectly infers the URL scheme, which erroneously bypasses the initialization of critical SSH security options like CURLOPT_SSH_HOST_PUBLIC_KEY_SHA256 and CURLOPT_SSH_KNOWNHOSTS. Conversely, the libcurl runtime successfully honors CURLOPT_DEFAULT_PROTOCOL and establishes the connection via SFTP/SCP as specified. Because the tool layer skipped the security configuration, these SSH host verification options are silently omitted, causing curl to connect to an unverified SSH remote host without throwing an error.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Improper Certificate Validation

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4
  • Fixed in: 8.14.1-2+deb13u7

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A vulnerability exists where a new transfer that uses STARTTLS to upgrade the connection might reuse an existing live connection even though the TLS configuration mismatches so it should not.

Remediation

Upgrade Debian:13 curl to version 8.14.1-2+deb13u7 or higher.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 asking curl to use a .netrc file to find credentials and at the same time specifying a URL with a username (without a password), like https://user@example.com/, curl could wrongly get and use the password for another user set in the .netrc file for that host if such a one exists and there is no match for the specified user.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Insufficiently Protected Credentials

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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 had a flaw that when instructed to clear proxy authentication credentials which made it not do so, leaving the old credentials around to get used for subsequent transfers that should not know nor use them.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

A use-after-free vulnerability exists in libcurl when an application configures an HTTP/2 stream-dependency tree via CURLOPT_STREAM_DEPENDS or CURLOPT_STREAM_DEPENDS_E, subsequently invokes curl_easy_reset(), and finally terminates the handle with curl_easy_cleanup(). During this final cleanup phase, libcurl attempts to access and modify an internal structure that was already freed during the reset operation.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Use After Free

  • Vulnerable module: curl
  • Introduced through: curl@8.14.1-2+deb13u4 and curl/libcurl4t64@8.14.1-2+deb13u4

Detailed paths

  • Introduced through: nginx@mainline › curl@8.14.1-2+deb13u4
  • Introduced through: nginx@mainline › curl/libcurl4t64@8.14.1-2+deb13u4

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.

Calling curl_easy_pause() within the event-based CURLMOPT_SOCKETFUNCTION callback triggers a use-after-free vulnerability, where libcurl attempts to store a flag using a dangling struct pointer immediately after that pointer's memory has been freed.

Remediation

There is no fixed version for Debian:13 curl.

References

low severity

Integer Overflow or Wraparound

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

Detailed paths

  • Introduced through: nginx@mainline › diffutils@1:3.10-4

NVD Description

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

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

This issue has been fixed in commit 9ff04d5b84743e331e80b589335a52c5480d1815 

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

Remediation

There is no fixed version for Debian:13 diffutils.

References

low severity

Out-of-bounds Read

  • Vulnerable module: expat/libexpat1
  • Introduced through: expat/libexpat1@2.8.2-1~deb13u1
  • Fixed in: 2.8.3-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › expat/libexpat1@2.8.2-1~deb13u1

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.8.3 has an out-of-bounds read and resultant infinite loop because low surrogates are treated the same as high surrogates during Unicode processing in the *_toUtf16 functions.

Remediation

Upgrade Debian:13 expat to version 2.8.3-1~deb13u1 or higher.

References

low severity

CVE-2026-18374

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-19499

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-19542

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-5435

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-5928

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

Calling the ungetwc function on a FILE stream with wide characters encoded in a character set that has overlaps between its single byte and multi-byte character encodings, in the GNU C Library version 2.43 or earlier, may result in an attempt to read bytes before an allocated buffer, potentially resulting in unintentional disclosure of neighboring data in the heap, or a program crash.

A bug in the wide character pushback implementation (_IO_wdefault_pbackfail in libio/wgenops.c) causes ungetwc() to operate on the regular character buffer (fp->_IO_read_ptr) instead of the actual wide-stream read pointer (fp->_wide_data->_IO_read_ptr). The program crash may happen in cases where fp->_IO_read_ptr is not initialized and hence points to NULL. The buffer under-read requires a special situation where the input character encoding is such that there are overlaps between single byte representations and multibyte representations in that encoding, resulting in spurious matches. The spurious match case is not possible in the standard Unicode character sets.

Remediation

Upgrade Debian:13 glibc to version 2.41-12+deb13u4 or higher.

References

low severity

CVE-2026-6238

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-6368

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-6791

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-77117

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-80489

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-8674

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-86805

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-89092

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-95818

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

CVE-2026-97399

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

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

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

Remediation

There is no fixed version for Debian:13 glibc.

References

low severity

Out-of-bounds Write

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

Detailed paths

  • Introduced through: nginx@mainline › glibc/libc-bin@2.41-12+deb13u3
  • Introduced through: nginx@mainline › glibc/libc6@2.41-12+deb13u3

NVD Description

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

Calling the scanf family of functions with a %mc (malloc'd character match) in the GNU C Library version 2.7 to version 2.43 with a format width specifier with an explicit width greater than 1024 could result in a one byte heap buffer overflow.

Remediation

Upgrade Debian:13 glibc to version 2.41-12+deb13u4 or higher.

References

low severity
new

CVE-2026-67693

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

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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.

An issue in gnutls v.3.8.13 allows an attacker to obtain sensitive information via failing to reject end-entity X.509 certificates that contain a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU)

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity
new

CVE-2026-88647

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

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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.

A hostname verification bypass in GnuTLS v3.8.13 allows attackers to circumvent the Common Name fallback mechanism and eavesdrop on communications via a crafted certificate.

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity
new

CVE-2026-88648

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

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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.

Incomplete X.509 implementation in GnuTLS v3.8.13 allows attackers controlling a subordinate Certificate Authority to bypass cross-domain PKI restrictions and issue unauthorized certificates.

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity
new

CVE-2026-95184

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

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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.

Improper certificate validation in gnutls v3.8.13 causes the application to reject legitimate certificates for valid users, leading to a Denial of Service (DoS).

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity
new

CVE-2026-95209

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

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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.

An issue in gnutls v3.8.13 causes legitimate CA certificates to be rejected, leading to a Denial of Service (DoS).

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity
new

CVE-2026-95210

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

Detailed paths

  • Introduced through: nginx@mainline › gnutls28/libgnutls30t64@3.8.9-3+deb13u4

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.

Improper certificate validation in gnutls v3.8.13 causes the application to accept certificates containing invalid extensions.

Remediation

There is no fixed version for Debian:13 gnutls28.

References

low severity

CVE-2024-26461

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

Detailed paths

  • Introduced through: nginx@mainline › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libk5crypto3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5-3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5support0@1.21.3-5+deb13u1

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+deb13u1, krb5/libk5crypto3@1.21.3-5+deb13u1 and others

Detailed paths

  • Introduced through: nginx@mainline › krb5/libgssapi-krb5-2@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libk5crypto3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5-3@1.21.3-5+deb13u1
  • Introduced through: nginx@mainline › krb5/libkrb5support0@1.21.3-5+deb13u1

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

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.20, a crafted sequence of H.265 NAL units causes decoder_context::read_slice_NAL() (libde265/decctx.cc:481) to attach slice headers to a finished picture object that has no active image unit, resulting in attacker-controlled unbounded heap growth. The retained headers are never freed until the picture is released, which may not happen during continuous streaming. Version 1.0.20 patches the issue.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

CVE-2024-38949

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to display444as420 function at sdl.cc

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

CVE-2024-38950

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

Heap Buffer Overflow vulnerability in Libde265 v1.0.15 allows attackers to crash the application via crafted payload to __interceptor_memcpy function.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

CVE-2025-61147

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

strukturag libde265 commit d9fea9d wa discovered to contain a segmentation fault via the component decoder_context::compute_framedrop_table().

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

CVE-2026-88373

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 commit 4d45a6b contains a NULL pointer dereference vulnerability in the NAL parsing path. When de265_push_NAL() is called with a zero-length NAL unit, the resulting NAL_unit may retain a NULL backing buffer, which is subsequently passed as the destination argument to memcpy() in NAL_unit::set_data(). Although the copy length is zero, this violates the nonnull requirement of memcpy() and results in undefined behavior, causing process termination in UBSan-instrumented builds and denial of service.

Remediation

There is no fixed version for Debian:13 libde265.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Versions prior to 1.1.1 use signed 32-bit arithmetic to calculate the sample adaptive offset input-buffer size, allowing a crafted HEVC stream with large dimensions and 16-bit luma samples to cause an integer overflow, an undersized allocation, and an out-of-bounds heap read that may expose heap data in decoded output or crash the decoder. Version 1.1.1 contains a patch.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.1.0, a crafted H.265 bitstream with large SPS dimensions and 16-bit bit depth causes a signed integer overflow in de265_image_get_buffer() (libde265/image.cc:128). The overflow wraps the plane allocation size to a small value (~1 KB), but the subsequent fill_image() call computes the real size using size_t, writing ~4 GB into the undersized heap buffer. Version 1.1.0 patches the issue.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Versions prior to 1.1.1 use signed 32-bit arithmetic to calculate pixel offsets, allowing a crafted HEVC stream with large image dimensions to trigger an integer overflow and cause out-of-bounds heap reads or writes, potentially disclosing data, corrupting memory, or crashing the decoder. Version 1.1.1 contains a patch.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Versions prior to 1.0.19 have a heap buffer overflow (out-of-bounds READ) exists in decoder_context::decode_slice_unit_WPP() in libde265/decctx.cc. When decoding a WPP (Wavefront Parallel Processing) HEVC slice, ctbAddrRS is computed as ctbRow * ctbsWidth inside the entry-point loop. If the PPS/SPS headers are crafted so that this value exceeds pps.CtbAddrRStoTS.size(), the subsequent array access pps.CtbAddrRStoTS[ctbAddrRS] reads past the end of the allocated vector, triggering a heap-buffer-overflow confirmed by AddressSanitizer. Version 1.0.19 patches the issue.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.19, decoder_context::decode_slice_unit_tiles (libde265/decctx.cc:920) reads pps.CtbAddrRStoTS[ctbAddrRS] at line 966 where ctbAddrRS = ctbY * ctbsWidth + ctbX is computed from PPS-supplied colBd[]/rowBd[] arrays without validating the result against CtbAddrRStoTS.size() == sps-&gt;PicSizeInCtbsY. A malformed PPS that passes set_derived_values but encodes geometry inconsistent with the SPS produces a ctbAddrRS past the allocation, causing a 4-byte heap-buffer-overflow READ. Version 1.0.19 fixes the issue.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libde265/libde265-0
  • Introduced through: libde265/libde265-0@1.0.15-1+b3
  • Fixed in: 1.0.15-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libde265/libde265-0@1.0.15-1+b3

NVD Description

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

libde265 is an open source implementation of the h.265 video codec. Prior to version 1.0.20, a crafted H.265 bitstream can cause an out-of-bounds array write in decoder_context::process_reference_picture_set() (libde265/decctx.cc:1376). The root cause is a missing aggregate bound check on predicted short-term reference picture set entries. Individual list sizes are validated, but the combined count after predicted RPS construction can exceed the 16-entry PocStFoll array, writing at index 16. Version 1.0.20 patches the issue.

Remediation

Upgrade Debian:13 libde265 to version 1.0.15-1+deb13u1 or higher.

References

low severity

Covert Timing Channel

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

Detailed paths

  • Introduced through: nginx@mainline › libgcrypt20@1.11.0-7+deb13u1

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

Allocation of Resources Without Limits or Throttling

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. In 1.23.1 and earlier, crafted grid, iovl, and iden reference graphs can repeatedly decode the same base image because processed_ids is copied per branch and ImageItem::decode_image() has no shared operation budget. This vulnerability is fixed in 1.23.2.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and below contain a heap buffer overflow in MaskImageCodec::decode_mask_image(). When decoding a HEIF file containing a mask image (mski), the function copies the full iloc extent data into a pixel buffer using memcpy(dst, data.data(), data.size()). The copy length data.size() is determined by the iloc extent in the file (attacker-controlled), while the destination buffer is sized based on the declared image dimensions. Because no upper-bound check exists on the data length, a crafted file whose iloc extent exceeds the pixel buffer allocation overflows the heap. The vulnerable single-memcpy branch is reached when the mskC property specifies bits_per_pixel = 8 and the ispe property declares an even width ≥ 64 (so that stride == width), with no changes to default security limits or external codec plugins required. This issue has been fixed in version 1.22.0.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Improper Handling of Highly Compressed Data (Data Amplification)

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.2, crafted HEIF or AVIF mime metadata and unci image data can cause decompress_brotli() and do_inflate() to grow accumulated output without an effective size limit or MemoryHandle accounting. The brotli path has no output bound, while the zlib path checks only a small temporary buffer in a branch that valid streams do not reach, and overlapping icef units can decompress the same payload repeatedly. HeifContext::interpret_heif_file_images() processes multiple compressed metadata items during file opening, allowing a small file to consume unbounded memory and terminate the process. This issue is fixed in version 1.23.2.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

Information Exposure

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Prior to version 1.22.0, two bugs in libheif chain to leak process heap memory as visible pixel values in decoded grid images. An attacker who uploads a crafted AVIF/HEIC file to any server-side image processor (WordPress, Sharp/libvips, ImageMagick, etc.) can recover heap data - including library function pointers sufficient to defeat ASLR, or any other secret - from the publicly-downloadable transcoded JPEG/PNG/WebP output. Local attack vectors are also possible. Version 1.22.0 fixes the issue.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. In versions 1.21.2 and prior, the inline mask parsing code in libheif/region.cc contains an integer overflow. Both width and height are unsigned int (32-bit) values parsed from the HEIF file. Their product can exceed UINT32_MAX, wrapping to a small value before the division by 8. This causes an undersized buffer allocation, leading to out-of-bounds memory access when the mask data is later interpreted as a width x height bitmap. Version 1.22.0 patches the issue.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Integer Underflow

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. In 1.23.0 and earlier, a crafted HEIF or AVIF file containing a clean aperture box can reduce an image dimension to zero and crash or corrupt tiling results when heif_image_handle_get_image_tiling(handle, 1, &tiling) is called. ImageItem::get_heif_image_tiling() returns already transformed dimensions, and process_image_transformations_on_tiling() applies the clean aperture transformation again. The second application passes zero to Box_clap::left_rounded(0), where image_width minus one underflows and constructs Fraction(0xFFFFFFFF, 2). Debug builds reach an assertion and abort, while release builds can return a corrupt crop and zero-width tiling result. The affected implementation spans libheif/image-items/image_item.cc, libheif/context.cc, and libheif/box.cc. This issue is fixed in version 1.23.1.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Loop with Unreachable Exit Condition ('Infinite Loop')

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Prior to 1.23.2, crafted HEIF sequence timing and edit-list data can make Track::init_sample_timing_table() compute a logical m_num_output_samples value that exceeds the uint32_t counters used by Track_Visual::decode_next_image_sample() and Track::get_next_sample_raw_data(). The resulting comparison can never reach the oversized output count, causing non-terminating decode or raw-sample loops and bypassing max_sequence_frames. The same sequence path repeatedly calls Box_stts::get_sample_duration() and allocates Chunk::m_sample_ranges and Track::m_presentation_timeline outside MemoryHandle accounting, allowing severe CPU and memory exhaustion from a small file. This issue is fixed in version 1.23.2.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and prior contain a heap buffer over-read in HeifPixelImage::overlay() in libheif/pixelimage.cc. When compositing an overlay image (iovl) whose child image has a different bit depth for the alpha channel than for the color channels, the function indexes into the alpha plane using the color channel stride (in_stride) instead of the previously retrieved alpha_stride, causing reads past the end of the alpha buffer (up to 3,123 bytes for a 100×50 image with 10-bit color and 8-bit alpha). A crafted HEIF file can exploit this to cause a denial of service (crash) or potentially disclose adjacent heap memory through leaked bytes embedded in the decoded output pixels. This issue has been fixed in versionThis issue has been fixed in version 1.22.0.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Prior to version 1.22.1, the uncompressed HEIF decoder validates explicit icef compressed-unit offsets using unit_offset + unit_size. Because the addition can wrap, a crafted HEIF file can pass the range check and then construct a vector from iterators outside the compressed item buffer, producing an out-of-bounds heap read and crash. Version 1.22.1 patches the issue.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Versions 1.19.0 through 1.21.2 have a heap OOB read in ImageItem_Grid::decode_grid_tile via irot-induced tile-coordinate underflow. Version 1.22.0 fixes the issue.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.1, a crafted uncompressed HEIF image using generic zlib unci full-item compression can crash an application that decodes an advertised tile with heif_image_handle_decode_image_tile(). In libheif/codecs/uncompressed/unc_decoder.cc, unc_decoder::fetch_tile_data() computes a large tile offset and unc_decoder::get_compressed_image_data_uncompressed() validates it with range_start_offset plus range_size. For the last advertised tile (4095, 4095), the addition can wrap to zero, bypass the bounds check, and pass an invalid source pointer and a one-terabyte length to memcpy. The observed result is an out-of-bounds read and process crash; opening the file alone does not trigger the issue because tile decoding is required. This issue is fixed in version 1.23.1.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.3, the no-icef full-item branch of unc_decoder::get_compressed_image_data_uncompressed() in libheif/codecs/uncompressed/unc_decoder.cc retains an addition-based range check that can wrap when a crafted uncompressed tile grid produces a large range_start_offset and range_size. The overflow makes the bounds comparison pass and allows heif_image_handle_decode_image_tile() to call memcpy() with an invalid source pointer and a very large length when decoding a valid high-index advertised tile. This incomplete remediation of CVE-2026-62292 can reliably crash tile-processing applications, while whole-image decoding is not claimed to reach the demonstrated path. This issue is fixed in version 1.23.3.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Prior to 1.23.2, the public heif_region_item_add_region_inline_mask_data() function in libheif/api/libheif/heif_regions.cc accepts mask_data_len without verifying that it equals the byte count required by width and height. A later heif_region_get_mask_image() call derives the read length from the region geometry, so an undersized stored buffer causes heif_region_get_inline_mask_image() to read beyond the heap allocation and copy adjacent bytes into the returned monochrome mask image. This can disclose heap data or crash an application that constructs region metadata through the writer API, while the file-parsing path is not affected because it validates the canonical mask size. This issue is fixed in version 1.23.2.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.19.8-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Versions 1.21.2 and prior contain a heap-buffer-overflow (write) vulnerability in the grid tile compositing, allowing an attacker to write 64 bytes of fully attacker-controlled data past the end of a chroma plane heap allocation by crafting a HEIF/AVIF file with a 1×4 grid of odd-height tiles. The overflow is triggered during normal image decoding with default build configuration. The written bytes are chroma (Cb/Cr) pixel values from the attacking tile, giving the attacker full control over the overflow content. This issue has been fixed in version 1.22.0.

Remediation

Upgrade Debian:13 libheif to version 1.19.8-1+deb13u1 or higher.

References

low severity

Out-of-bounds Write

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. Prior to 1.23.2, when WITH_UNCOMPRESSED_CODEC is enabled, heif_context_add_image_tile() accepts an independently constructed tile whose component-plane dimensions do not match the tile geometry established by the prototype image. ImageItem_uncompressed::add_image_tile() passes that tile directly to unc_encoder::encode_tile(), which lacked the check_component_sizes() gate and sizes its output from the configured tile geometry while copying the tile's actual component-plane dimensions. An oversized component plane can therefore make unc_encoder_component_interleave::encode_tile() copy attacker-controlled data beyond the heap output buffer. This issue is fixed in version 1.23.2.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

Reachable Assertion

  • Vulnerable module: libheif/libheif-plugin-dav1d
  • Introduced through: libheif/libheif-plugin-dav1d@1.19.8-1, libheif/libheif-plugin-libde265@1.19.8-1 and others
  • Fixed in: 1.23.4-1~deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libheif/libheif-plugin-dav1d@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif-plugin-libde265@1.19.8-1
  • Introduced through: nginx@mainline › libheif/libheif1@1.19.8-1

NVD Description

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

libheif is a HEIF and AVIF file format decoder and encoder. From 1.19.0 until 1.23.3, a crafted image item containing a clap property and an ispe width or height greater than INT32_MAX + 1 can reach crop calculations through heif_image_handle_get_image_tiling(). Box_clap::left_rounded() or Box_clap::top_rounded() passes the image dimension minus one to Fraction::Fraction(), whose uint32_t constructor uses an assertion as input validation, causing assert-enabled builds to abort. Release builds can instead compute invalid crop geometry, and the tiling API returns dimensions that the normal decode security limits reject. This issue is fixed in version 1.23.3.

Remediation

Upgrade Debian:13 libheif to version 1.23.4-1~deb13u1 or higher.

References

low severity

CVE-2026-46675

  • Vulnerable module: libpng1.6/libpng16-16t64
  • Introduced through: libpng1.6/libpng16-16t64@1.6.48-1+deb13u5
  • Fixed in: 1.6.48-1+deb13u6

Detailed paths

  • Introduced through: nginx@mainline › libpng1.6/libpng16-16t64@1.6.48-1+deb13u5

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

Upgrade Debian:13 libpng1.6 to version 1.6.48-1+deb13u6 or higher.

References

low severity

Heap-based Buffer Overflow

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.8.12-1 and libx11/libx11-data@2:1.8.12-1

Detailed paths

  • Introduced through: nginx@mainline › libx11/libx11-6@2:1.8.12-1
  • Introduced through: nginx@mainline › libx11/libx11-data@2:1.8.12-1

NVD Description

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

A malicious X server could exploit a buffer overflow in libX11 before 1.8.14 during handling of XkbGetMap overflowing the key_sym_map.

Remediation

There is no fixed version for Debian:13 libx11.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.8.12-1 and libx11/libx11-data@2:1.8.12-1

Detailed paths

  • Introduced through: nginx@mainline › libx11/libx11-6@2:1.8.12-1
  • Introduced through: nginx@mainline › libx11/libx11-data@2:1.8.12-1

NVD Description

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

An out-of-bounds read vulnerability in libX11's XIM trigger-key registration parser in libX11 before 1.8.14 could be used by malicious X servers to crash attached X clients.

Remediation

There is no fixed version for Debian:13 libx11.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.8.12-1 and libx11/libx11-data@2:1.8.12-1

Detailed paths

  • Introduced through: nginx@mainline › libx11/libx11-6@2:1.8.12-1
  • Introduced through: nginx@mainline › libx11/libx11-data@2:1.8.12-1

NVD Description

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

An out-of-bounds read vulnerability in libX11's XIM (X Input Method) attribute parser in libX11 before 1.8.14 could be used by malicious X servers to crash attached X clients.

Remediation

There is no fixed version for Debian:13 libx11.

References

low severity

Out-of-bounds Read

  • Vulnerable module: libx11/libx11-6
  • Introduced through: libx11/libx11-6@2:1.8.12-1 and libx11/libx11-data@2:1.8.12-1

Detailed paths

  • Introduced through: nginx@mainline › libx11/libx11-6@2:1.8.12-1
  • Introduced through: nginx@mainline › libx11/libx11-data@2:1.8.12-1

NVD Description

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

An out-of-bounds read in libX11's byte-oriented codeset parser in libX11 before 1.8.14 could be used by malicious X servers to crash attached X clients.

Remediation

There is no fixed version for Debian:13 libx11.

References

low severity

Excessive Platform Resource Consumption within a Loop

  • Vulnerable module: libxpm/libxpm4
  • Introduced through: libxpm/libxpm4@1:3.5.17-1+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › libxpm/libxpm4@1:3.5.17-1+deb13u1

NVD Description

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

A denial of service via unsigned underflow in libXpm's write path in libXpm before 3.5.19 could be used by local attackers to cause unbounded CPU usage and memory exhaustion.

Remediation

There is no fixed version for Debian:13 libxpm.

References

low severity

Out-of-bounds Read

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

Detailed paths

  • Introduced through: nginx@mainline › 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 0.9.14 before 0.9.34, 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

CVE-2026-14456

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: When an OpenSSL QUIC server (Listener SSL object) processes valid QUIC Initial packets for unknown destination connection IDs, it can allocate and queue new incoming channels without enforcing any limit.

Impact summary: A remote peer that can make many Initial packets reach the server listener faster than the application accepts connections, can cause the memory allocated to store the per-channel state to grow without any limits, potentially making the QUIC listener unavailable and causing Denial of Service.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: The function that handles inbound QUIC packets uses Connection-Id from the packet header to find an existing connection (QUIC channel). If no existing connection is found and the packet type is INITIAL, the function treats the packet as a new connection. It allocates a new channel object and inserts it into a queue where it waits to be accepted by the local application with SSL_accept(3ossl). The memory occupied by these initial channel objects may grow without bounds if the application is not able to call SSL_accept() frequently enough to serve these inbound connection requests.

The issue is present since OpenSSL 3.5 when the QUIC server implementation was added.

The fix introduces a limit for pending connections. The default limit is set to 256 pending connections (waiting to be accepted by the local application). Applications may change the default by calling SSL_set_value_uint(3ossl).

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-14457

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: In a server or client configuration with RFC7250 Raw Public Keys (RPKs) enabled, and only the private key (with no associated certificate) configured locally, a NULL pointer dereference may occur when the remote peer solicits raw public keys and also sends the typically omitted "signature_algorithms_cert" TLS extension.

Impact summary: The impact is limited to a possible Denial of Service as a result of an application abort, no data disclosure or remote command execution are possible.

CWE: CWE-476: NULL Pointer Dereference

Description: While a passing comment in sample code in the documentation suggests that key-only RPK configurations are supported, the best-practice RPK configuration is to always configure a corresponding certificate (possibly self-signed or signed by any convenient CA).

When the private key is configured along with a matching certificate, the "signature_algorithms_cert" extension is handled reliably even without the fix, and peer clients or servers that don't support raw public keys may be able to complete a TLS connection by pinning or verifying the corresponding certificate or its public key.

Deployments that prefer to configure just a private key with no certificate need to upgrade to an updated release as noted below.

FIPS impact: no

No FIPS modules are affected by this issue, as the SSL protocol implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-18798

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: QUIC server may double free QRX (QUIC record layer RX) object when channel creation fails for initial packet.

Impact summary: Double free leads to heap corruption, which typically results in termination of QUIC server process, leading to Denial of Service. There is so far no evidence that this double free is exploitable for remote code execution, thus it is considered highly improbable.

CWE: CWE-415: Double Free

Description: In order to validate initial packet, OpenSSL QUIC stack default packet handler (port_default_packet_handler()) creates a so-called QRX object. If the initial packet validates successfully with QRX object, the default packet handler proceeds to channel (connection object) creation. The QRX object used for packet validation is passed to port_bind_channel(), so it becomes part of the newly created connection. If port_bind_channel() fails, then it also frees the QRX object. Once port_bind_channel() returns, the port_default_packet_handler() detects the failure and proceeds to the error branch, where the same QRX object is freed for the second time.

The failure in port_bind_channel() function can be induced with a relatively low effort by a malformed (non RFC 9000 compliant) INITIAL packet. If the packet carries DCID (destination connection ID) which is shorter than 8 bytes, then port_bind_channel() jumps to the error path after ossl_quic_lcidm_enrol_odcid() detects that the DCID has invalid length.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-35189

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: A certificate with many nameRelativeToCRLIssuer CRL distribution points causes disproportionate heap growth when OpenSSL caches X.509 extensions.

Impact summary: Receiving a crafted certificate from a malicious peer can lead to significant memory pressure and possible Denial of Service in clients or in servers that solicit client certificates.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: A certificate or a set of certificates that fits under the limit for size of certificates accepted from the peer (~100 KiB) can result in allocation of several hundred MiB of resident memory on the receiving side during a normal TLS handshake. This may be enough to crash the client or server, if multiple concurrent connections lead to similarly large memory allocations.

The fix postpones processing of the CRL distribution points extensions in certificates to the time when the processed value is required for CRL processing. This avoids keeping large memory allocations for a long time when such certificates are received.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-35191

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: The OpenSSL QUIC server, when configured to not preform address validation, can be forced to count incoming packets multiple times in its unvalidated credit computation, leading to a violation of the RFC 9000 unvalidated connection amplification limit of 3 times the amount of data received.

Impact summary: A remote attacker able to spoof packets to a server using the OpenSSL QUIC implementation might use the server for an amplification of a DDoS attack.

CWE: CWE-440: Expected Behavior Violation

Description: OpenSSL's QUIC stack, when operating as a server, enforces client address validation (RFC 9000, Section 8), to confirm the peer address is not used for a traffic amplification attack. If this feature is disabled on the server, the QUIC stack limits the amount of server data that can be sent to 3 times the amount of data received from the peer address, until such time as the TLS handshake is completed.

The OpenSSL QUIC server, when operating in non-validation mode, adds the length of the whole datagram received to the unvalidated credit limit when processing each QUIC packet in the datagram. A remote peer may, after establishing a connection with an initial client hello frame, send a subsequent datagram containing multiple QUIC packets, leading the server to account the entire datagram length for each packet in the datagram, resulting in the server believing that the peer has sent more data than it actually has, thereby violating the 3x amplification limit mandated by the RFC.

FIPS impact: no As the QUIC stack lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-42772

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: The QUIC stream reassembly algorithm performance deteriorates progressively as packets are arriving out of order. The worst case has a quadratic complexity proportional to the number of stream frames kept in the buffer for the received stream data.

Impact summary: A remote QUIC peer that completes the handshake can create a connection-scoped CPU pressure and potentially a Denial of Service using compliant STREAM frames inside the advertised receive window, with low attacker bandwidth.

CWE: CWE-407: Inefficient Algorithmic Complexity

Description: OpenSSL manages received QUIC stream fragments using a doubly-linked list. While it optimizes for append operations (at the end of the list), it falls back to a head-to-tail linear search for any fragment that does not immediately follow the current tail.

By manipulating the sequence of offsets, an attacker can force the server to perform O(n^2) operations, consuming excessive CPU time for the QUIC process.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-54872

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: The generic elliptic-curve scalar multiplication used for ECDSA and SM2 signature operations with curves that do not have a dedicated implementation leaks information about the secret nonce through timing.

Impact summary: An attacker able to measure signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.

CWE: CWE-208: Observable Timing Discrepancy

Description: The generic elliptic-curve scalar multiplication used for curves that do not have a dedicated constant-time implementation pads the secret scalar with non-constant-time BIGNUM operations, so the time taken depends on the value of the secret scalar derived from the ECDSA and SM2 nonce.

The leak is very small; observing it requires a large number of measurements. The effect is largest for curves whose group order lies on a machine-word boundary, such as brainpoolP384r1.

Applications using ECDSA signing over the Brainpool and other generic prime curves, and SM2 signing on platforms that use the generic implementation, are vulnerable to this issue.

The NIST curves P-256, P-384 and P-521 use dedicated constant-time implementations and are not affected.

FIPS Impact: no The FIPS modules are not affected: the approved NIST curves used in the FIPS provider have dedicated constant-time implementations and do not use the affected code path.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-54873

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: QUIC process may keep memory for QUIC packet buffer for much longer period than necessary.

Impact summary: Remote peer can exploit this vulnerability by sending maliciously crafted packets, making the local QUIC stack to keep the memory for packet buffers allocated. The time for which the memory remains allocated is entirely under the control of the potentially malicious remote peer.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: To save copy operation from the packet buffer to the stream reassemble buffer the QUIC stack leaves the stream data on the packet buffer waiting to be copied to a buffer provided by the local receiving application. The QUIC stack releases a reference to the packet buffer only after the data are copied to the application buffer. This design is more efficient for legitimate data transfers but enables an attacker to allocate a lot more memory than actually required by the data kept in the receiving stream buffer.

To mitigate the vulnerability, the QUIC stack now calculates and monitors memory overhead for every stream. The memory overhead for a single stream frame is calculated as a difference between the size of the whole packet that carries the stream frame and the size of the stream frame itself. The memory overhead for a single stream frame is added to the total (cumulative) memory overhead QUIC stack keeps for each stream. Once the cumulative memory overhead exceeds 64kB, the QUIC stack moves the stream frame data from the packet buffer to the stream buffer, starting with the next packet received.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-54874

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: Receiving a DTLS record for a future epoch while a handshake is in progress causes OpenSSL to buffer far more memory than the record itself requires.

Impact summary: A peer can use a small amount of network traffic to make an OpenSSL DTLS endpoint retain a disproportionately large amount of memory, which may lead to a Denial of Service.

CWE: CWE-405: Asymmetric Resource Consumption (Amplification)

Description: While a DTLS handshake is in progress, a peer may legitimately have already moved on to the next epoch (for example, having sent its ChangeCipherSpec and Finished messages) before the local endpoint has processed the same transition, typically because of reordering on the underlying UDP transport. OpenSSL buffers such early records so that they can be processed once the local endpoint catches up.

Buffering a record currently retains the entire read buffer it arrived in, which is sized to hold the largest possible DTLS record (around 16 kilobytes), rather than just the bytes that make up the record itself. Up to 100 such records may be buffered per connection. As a result, a peer that sends a stream of small forged records claiming to belong to the next epoch can cause an OpenSSL DTLS endpoint to retain around 1.7 megabytes of memory, despite sending only a small fraction of that amount of data over the network.

An attacker therefore gains a memory amplification factor of around 1200, and can multiply the effect across as many associations as it is able to open, making this a remote memory exhaustion Denial of Service risk for DTLS servers. Since the memory retained per connection remains bounded, and any limit an application already places on the number of concurrent associations also bounds the total exposure, this issue has been assessed as Low severity.

FIPS impact: no

No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

OpenSSL 4.0, 3.6, 3.5, 3.4, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.2. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.4. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.8. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.7. OpenSSL 3.0 users should upgrade to OpenSSL 3.0.22.

Premium support customers only: OpenSSL 1.1.1 users should upgrade to OpenSSL 1.1.1zi OpenSSL 1.0.2 users should upgrade to OpenSSL 1.0.2zr

This issue was reported on 18 May 2026 by Amazon Web Services. The fix has been developed by Matt Caswell.

-- cut (non-publishing metadata for internal use) -- Reported by: Amazon Web Services Fixed by: Matt Caswell

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-54875

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: A non-constant-time optimized implementation of scalar point multiplication is used for SM2 private key operations on ARM64 and RISC-V platforms.

Impact summary: An attacker able to measure the time taken by, or to observe the cache-line access pattern of SM2 signing or decryption on an affected platform can learn information about the secret scalar.

CWE: CWE-208: Observable Timing Discrepancy

Description: On ARM64 and RISC-V processors, the SM2 curve uses an optimized scalar multiplication implementation whose conditional branches and table look ups are chosen according to the bits of the secret scalar. The execution time and the cache-access pattern therefore depend on the long-term private key (during SM2 decryption) or the per-signature nonce (during SM2 signature generation), forming a timing and cache side-channel.

FIPS Impact: no SM2 is not a FIPS algorithm and the optimized SM2 implementation is not part of the FIPS module.

OpenSSL 4.0, 3.6, 3.5 and 3.4 are vulnerable to this issue on AArch64 and RISC-V.

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

OpenSSL 4.0 users should upgrade to OpenSSL 4.0.3. OpenSSL 3.6 users should upgrade to OpenSSL 3.6.5. OpenSSL 3.5 users should upgrade to OpenSSL 3.5.9. OpenSSL 3.4 users should upgrade to OpenSSL 3.4.8.

This issue was reported on 2 May 2026 by Abhinav Agarwal. It was independently reported on 6 June 2026 by Feng Xue. The fix was developed by Igor Ustinov.

-- cut (non-publishing metadata for internal use) -- Reported by: Abhinav Agarwal, Feng Xue Fixed by: Igor Ustinov

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-63072

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: OpenSSL CMS decryption sizes the key-unwrap output buffer based on querying the unwrapped key size, but the AES-WRAP-PAD unwrap primitive can write and cleanse more bytes than that query reports, causing an 8-byte out-of-bounds heap write.

Impact summary: An attacker who supplies a crafted CMS message can trigger a deterministic 8-byte out-of-bounds heap write when the victim decrypts it with CMS_decrypt(), corrupting the heap and typically resulting in a Denial of Service.

CWE: CWE-787: Out-of-bounds Write

Description: The key-wrap OID is potentially attacker-controlled on the wire. CMS unwrapping allows both id-aesNNN-wrap-pad and id-aesNNN-wrap ciphers. An attacker can take a legitimate message and change a single OID byte to select the padded variant while leaving the message otherwise valid. Since the unwrap key is derived from the recipient's private operation (ECDH key agreement or ML-KEM decapsulation), the RFC 5649 integrity check cannot pass, and the decryption fails with integrity failure.

The write is a fixed-size (8-byte), fixed-value (zero) heap overflow immediately past the allocation, requires no special configuration, and is reachable from the public CMS_decrypt() function. The consequence is a heap corruption leading to a Denial of Service. The fix in the CMS code sizes the unwrap output buffer for the worst case so a failed unwrap cannot write past the allocation.

FIPS impact: no

As the CMS code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-63073

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: OpenSSL CMP response validation passed an unexpected response sender distinguished name directly as the format string to ERR_raise_data().

Impact summary: A malicious or intercepted CMP endpoint can crash a CMP client that enforces an expected sender or uses a pinned server certificate whose subject becomes the default expected sender.

CWE: CWE-134 (Use of Externally-Controlled Format String)

Description: When validating a received CMP message, ossl_cmp_msg_check_update() converts the peer-supplied sender distinguished name with X509_NAME_oneline() and passes it directly as the format argument to ERR_raise_data(). Percent characters survive the conversion, so a sender DN such as "CN=%s%n" reaches BIO_vsnprintf() as an attacker-controlled format string with no matching variadic arguments. This path is only reached when the caller configures an expected sender or pins a server certificate, which is the normal configuration for a CMP client validating server responses.

Since the attacker controls the format string but none of the variadic arguments, such specifiers as %s and %n dereference or write through unrelated stack contents and crash the client. The reliable consequence is a denial of service, when the response comes from a malicious or intercepted CMP endpoint. There is no controlled memory write, arbitrary-address read, or reliable path to remote code execution.

FIPS impact: no

No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-63074

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: The OpenSSL Certificate Management Protocol (CMP) caches additional certificates (extraCerts) sent in a CMP message, but never expunges them (for instance if they are invalid). If a server reuses an OSSL_CMP_CTX frequently, this cache of extraCerts may grow unboundedly, and a malicious client may flood a CMP server with requests driving this growth.

Impact summary: Users utilizing a CMP server that reuses a single OSSL_CMP_CTX for the lifetime of a server process may observe unbounded memory growth in the event a malicious client repeatedly sends requests containing unique extra certificates, which may lead to OOM conditions.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: If a remote user sends CMP messages to a server with a list of extraCerts and the message is rejected, the extraCerts from the message remains in the server contexts untrusted certificate stack. This exposes servers with long lived ctx objects to Denial of Service attacks in which an attacker sends messages intending to be rejected with a large list of additional certificates repeatedly, forcing the server to store them indefinitely.

The issue was fixed by removing the added extra certs if the message is rejected, using the same method as when the context is configured to not do caching at all.

FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-63075

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: When OpenSSL processes QUIC traffic from a peer that repeatedly sends ack-eliciting packets while not acknowledging ACK-only responses, the QUIC stack can retain ACK-only packet metadata for the lifetime of the connection.

Impact summary: A remote peer that can complete a QUIC handshake can cause connection-scoped memory growth which may lead to Denial of Service through memory exhaustion, especially with sustained traffic or many concurrent QUIC connections.

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: When the OpenSSL QUIC stack sends an ACK-only packet, there is no requirement by the QUIC protocol that the peer will acknowledge that ACK-only packet (i.e. it is itself not ack-eliciting). However, the OpenSSL implementation stores the metadata about the ACK frames regardless. In and of itself that's ok, but if a malicious peer establishes a connection, and then drives the connection such that ACK-only packets are forced from the OpenSSL implementation peer (i.e., by sending numerous PING frames), and then withholding any subsequent acks for ack-eliciting data, like legitimate data, said malicious peer can force inappropriate memory growth on the OpenSSL peer, potentially leading to a Denial of Service.

The fix is to ensure that we account for the transmission of the ACK-only packet in the packet histories high and low watermark without actually storing the ACK-only packet metadata itself.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-63076

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: OpenSSL CMP password based protection verification only checks whether the protectionAlg parameter was not NULL and not its ASN.1 type, before treating it as a PBMParameter. A crafted message can contain a parameter of a different type, which is then dereferenced as an invalid pointer.

Impact summary: A remote, unauthenticated attacker can crash an application acting as a CMP server that accepts PBM-protected messages, or a CMP client talking to a malicious or intercepted CMP server, resulting in a Denial of Service.

CWE: CWE-476: NULL Pointer Dereference

Description: When verifying the password-based MAC protection of a CMP message, OpenSSL library reads the protectionAlg algorithm parameter with X509_ALGOR_get0(), which returns both the parameter type and its value pointer. The value is then cast to an ASN1_STRING and treated as the expected PBMParameter after only checking that pointer is not NULL. The parameter type returned by X509_ALGOR_get0() was never consulted.

This happens during protection verification, before any MAC is computed, so no knowledge of the PBM shared secret is required; the only precondition is that PBM verification is reachable. On the server side this is reached from OSSL_CMP_SRV_process_request() for any application that stands up a CMP server accepting PBM-protected messages, and on the client side from CMP response validation against a malicious or on-path (MITM) server. The reliable consequence is a denial of service; there is no memory disclosure, no controlled memory write, and no path to code execution. CMP is a specialized feature that an application must explicitly enable.

FIPS impact: no As the CMP code lives outside the FIPS module boundary, no FIPS modules are affected by this CVE.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-72897

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: A TLS server that calls SSL_set_SSL_CTX() to switch a connection to a different SSL_CTX part way through a handshake may access memory beyond the end of an internal array if the replacement context knows about more provider signature algorithms than the context the connection was created from. Applications which never call SSL_set_SSL_CTX() are not affected.

Impact summary: A remote peer may be able to cause a small out-of-bounds read, and in some circumstances a fixed-value out-of-bounds write, on the server heap. This may lead to a Denial of Service.

CWE: CWE-787: Out-of-bounds Write

Description: A TLS connection records how many certificate slots it has when it is created, taken from the SSL_CTX that created it: the built-in certificate types plus one slot for each provider TLS-SIGALG entry that context was aware of. That count sizes an internal array of per-slot certificate validity flags.

An application may replace a connection's SSL_CTX part way through the handshake by calling SSL_set_SSL_CTX(), most commonly from a servername callback in order to serve a different virtual host. Doing so did not refresh the recorded count. A provider signature algorithm's slot index is its position in the list of whichever context resolves it, so if the replacement context is aware of more of them than the original, an algorithm offered by the peer can resolve to an index beyond the end of the array. Processing the peer's signature algorithms then reads one four byte word past the end for each such algorithm and, where the word read is zero, writes a fixed value over it. A peer offering many of them can corrupt heap metadata and abort the process.

Only provider signature algorithms which occupy one of the excess slots, and which the server also has configured, have this effect. Codepoints the replacement context does not recognise are discarded without being resolved to a slot, and provider signature algorithms are usable only from TLS 1.3.

The two contexts must therefore be aware of different numbers of provider signature algorithms, which requires separate library contexts, a provider loaded between the two being created, or providers which differ in what they advertise - in 4.0, for example, the default provider advertises SM2 where the FIPS provider does not. A deployment meeting the condition is also unable to negotiate the affected algorithms with legitimate clients, since the same stale count hides the corresponding certificates, so the misconfiguration is likely to be noticed. For that reason, and because the configuration is not the default, this issue has been assessed as Low severity.

FIPS impact: no No FIPS modules are affected by this issue as the affected code is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-75803

  • Vulnerable module: openssl
  • Introduced through: openssl@3.5.6-1~deb13u2, openssl/libssl3t64@3.5.6-1~deb13u2 and others
  • Fixed in: 3.5.7-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: ChaCha20-Poly1305 and AES-OCB decryption with an empty ciphertext can report success without verifying the supplied authentication tag when the operation is finalized by calling the EVP_Cipher() function.

Impact summary: Applications calling EVP_Cipher() on an empty ciphertext and expecting the call to check the AEAD tag may accept forged messages.

CWE: CWE-354 (Improper Validation of Integrity Check Value)

Description: The EVP_Cipher() API call for AEAD ciphers behaves like a one shot encryption and decryption call. It also verifies the AEAD tag after the decryption operation. However for AES-OCB and ChaCha20-Poly1305 ciphers it skipped the AEAD tag verification when an empty ciphertext was passed to the function. The callers of this function might believe that a successful return indicates a valid AEAD tag for these ciphers, even when that has not truly been validated in this case.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u2 or higher.

References

low severity

CVE-2026-75804

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: OpenSSL QUIC stack does not enforce connection level flow control for streams. Remote peers may send more bytes as long as they fit within the stream flow control limits.

Impact summary: A malicious remote peer may exploit the lack of connection flow control for streams to make the QUIC stack receive ~100MB of memory instead of 768 KiB (default flow control window size).

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: The local QUIC stack advertises two flow control limits to its remote peer: stream flow control limit and connection flow control limit. The remote peer must follow both limits when transmitting stream data.

Whenever the local QUIC stack receives a stream frame, it validates that the size of the received stream frame stays within flow control limits. If either limit is exceeded (stream level or connection level), then the QUIC stack must close the connection with a flow control error.

The vulnerable OpenSSL QUIC stack enforces the stream-level but not the connection-level limit. To exploit the issue, three conditions must be met:

  • the remote peer opens several streams
  • each stream must stay within the stream-level flow control limit
  • there must be no zero-offset byte sent on any of the streams (to prevent the vulnerable QUIC stack from consuming data). By meeting the conditions above, the remote peer may make the local stack allocate 2 x MAX_STREAMS x (stream flow control limit) bytes of memory. MAX_STREAMS defaults to 100, and the limit applies to both bidirectional and unidirectional streams, making it 200 in total. The default flow control window for a stream is 512kB. The remote peer may force the vulnerable QUIC stack to allocate 100MB of heap per connection.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-75805

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: A CMP client that requests certificate revocation on the basis of a PKCS#10 CSR may dereference a NULL pointer and terminate abnormally when processing a crafted revocation response.

Impact summary: The NULL pointer dereference happens on a read which leads to a crash and a Denial of Service for the affected client application.

CWE: CWE-476: NULL-pointer dereference

Description: A CMP client revoking a certificate has to tell the server which certificate to revoke, and may do so by supplying a PKCS#10 CSR instead of the certificate itself or its issuer name and serial number. This is 'openssl cmp -cmd rr -csr <file>' on the command line, or OSSL_CMP_exec_RR_ses() with the certificate supplied via OSSL_CMP_CTX_set1_p10CSR() through the API.

A CSR does not contain the issuer name and serial number of the certificate, so the client does not send them. A server may optionally name the certificate it revoked in its response, and the client then compares that name against what it sent. Having sent neither an issuer name nor a serial number, it has nothing to compare against, and a server returning a specially crafted name causes the client to read from a NULL pointer and crash.

The revocation response is checked for valid message protection before the affected code is reached, so an attacker must be a malicious or compromised CMP server, or a man-in-the-middle in possession of the secret used for message protection. Clients that identify the certificate to be revoked by a certificate or by issuer and serial number rather than by a PKCS#10 CSR are not affected.

FIPS impact: no No FIPS modules are affected by this issue, as the CMP protocol implementation is outside the OpenSSL FIPS module boundary.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-75806

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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 established DTLS 1.2 association using an AEAD cipher suite can be terminated by a single unauthenticated datagram whose encrypted fragment is shorter than the mandatory explicit IV and authentication tag overhead.

Impact summary: An attacker who can send a datagram that is routed to an existing DTLS 1.2 association can tear that association down without knowing any key material. This is a Denial of Service limited to the targeted association. There is no memory safety or confidentiality impact.

CWE: CWE-1284: Improper Validation of Specified Quantity in Input

Description: In TLS 1.2 and DTLS 1.2 every record protected by an AEAD cipher suite carries an explicit IV followed by the ciphertext and an authentication tag. When decrypting such a record the record layer passed the record length to the cipher implementation before checking that the record was long enough to contain the explicit IV and the tag. For a record shorter than that overhead the cipher implementation rejected the impossible length, and the record layer treated this as an internal failure and raised a fatal internal_error alert instead of treating the record as one that failed authentication.

In TLS 1.2 the same record causes a fatal internal_error alert instead of the expected bad_record_mac alert. Since any undecryptable record already terminates a TLS connection, this is a protocol conformance issue rather than a security issue in TLS.

The fix validates the record length against the explicit IV and tag length before any AEAD processing, so that TLS reports bad_record_mac and DTLS silently discards the record.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-77696

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

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: SM2 signature generation uses non-constant-time arithmetic on secret values, forming a timing side-channel.

Impact summary: An attacker able to measure SM2 signing times may learn information about the per-signature secret nonce, which over many signatures can, via a lattice / Hidden Number Problem attack, lead to recovery of the private key.

CWE: CWE-208: Observable Timing Discrepancy

Description: SM2 signature generation computes the signature value using variable-time BIGNUM operations on the secret nonce and the private key, so the time taken to produce an SM2 signature depends on these secret values, forming a timing side-channel.

Applications performing SM2 signature generation are affected on all platforms.

FIPS Impact: no SM2 is not a FIPS algorithm.

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-84782

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: The DTLS retransmission logic does not correctly handle a handshake message write that is suspended part-way through. The retransmitted message can be read past the message buffer and the retransmission overwrites the internal state the suspended write needs to resume correctly.

Impact summary: The retransmitted message can disclose a heap memory to the peer as plaintext handshake data or cause a crash and a Denial of Service when the read reaches an unmapped memory region.

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

Description: DTLS handshake messages can be written out in multiple fragments, and a write can suspend mid-message (returning WANT_WRITE) if the underlying transport temporarily cannot accept more data. While such a write is suspended, the DTLS retransmission timer may independently fire and ask the retransmission logic to resend an earlier, already-acknowledged-as-sent message from its retransmit queue.

The retransmission logic reused the same internal buffer and position tracking as the message that was still being written, without resetting the position back to the start of the message being retransmitted. As a result the retransmission was read starting from wherever the suspended write had left off, producing a mislabelled message whose body was leftover bytes from the other, larger message still in flight - content that was never meant to be sent at that point, and which could run past the end of the allocated buffer.

Separately, even when the retransmission is positioned correctly, allowing it to run to completion while another write is suspended overwrites the same shared bookkeeping that the suspended write depends on to resume. When the application later resumes the suspended write (via a subsequent SSL_read(), SSL_write(), SSL_accept(), or SSL_connect() call), it finds that bookkeeping in a state inconsistent with the message and aborts the process in a debugging build.

The fix resets the retransmission's read position to the start of the message before resending, and skips retransmission entirely whenever a handshake write is still suspended, deferring to the next call that resumes it instead.

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-84784

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

Detailed paths

  • Introduced through: nginx@mainline › openssl@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/libssl3t64@3.5.6-1~deb13u2
  • Introduced through: nginx@mainline › openssl/openssl-provider-legacy@3.5.6-1~deb13u2

NVD Description

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

Issue summary: A malicious remote peer may flood the local QUIC stack with NEW_CONNECTION_ID frames by avoiding a limit check on how many connection IDs the remote QUIC stack can use.

Impact summary: The local QUIC stack sends a RETIRE_CONN_ID frame for every NEW_CONNECTION_ID frame it receives. The RETIRE_CONN_ID frame is dispatched via the Control Frame Queue (CFQ). If the remote peer also withholds ACKs, then it can force the local stack to allocate ~400MB (depending on ACK delay).

CWE: CWE-770: Allocation of Resources Without Limits or Throttling

Description: RFC 9000 sections 5.1.1 and 5.1.2 [1] describe the mechanism by which a remote peer can notify the local QUIC stack to change the destination connection ID (a.k.a. CID) the local stack uses to identify the connection at the remote peer. Each CID is associated with a sequence number. The sequence number is transmitted in NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames to identify the CID which is being either associated with a connection or retired.

The remote peer sends a NEW_CONNECTION_ID frame to let the local stack know a new CID is being associated with an existing connection. The NEW_CONNECTION_ID frame carries the new CID, its sequence number, and the retire-prior-to number. The retire-prior-to identifies existing CIDs that are to be retired. The local QUIC stack must send a RETIRE_CONNECTION_ID for every destination CID whose sequence number is less than retire-prior-to. The CID becomes retired after the local stack receives an ACK for its RETIRE_CONNECTION_ID frame.

Although the OpenSSL QUIC stack supports at most one destination CID for every connection, it can be tricked into processing more than one RETIRE_CONNECTION_ID frame per connection. The OpenSSL QUIC stack currently retires the destination CID as soon as it receives the NEW_CONNECTION_ID, while in fact the destination CID must be retired after an ACK for the RETIRE_CONNECTION_ID frame is received. Correcting the flawed logic also fixes the backlog growth.

[1] https://datatracker.ietf.org/doc/html/rfc9000#name-issuing-connection-ids

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

Remediation

Upgrade Debian:13 openssl to version 3.5.7-1~deb13u3 or higher.

References

low severity

CVE-2026-54411

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

Detailed paths

  • Introduced through: nginx@mainline › pam/libpam-modules@1.7.0-5
  • Introduced through: nginx@mainline › pam/libpam-modules-bin@1.7.0-5
  • Introduced through: nginx@mainline › pam/libpam-runtime@1.7.0-5
  • Introduced through: nginx@mainline › pam/libpam0g@1.7.0-5

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 pam.

References

low severity

Improper Protection of Alternate Path

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u2

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

PCRE2 before 10.48 allows a pcre2_dfa_match out-of-bounds write because reuse of a cached workspace block, in a recursive DFA matching workspace, lacks a size check (even though a newly allocated block, for the same purpose, does have a size check). This outcome requires an attacker-controlled regular expression, or a recursive pattern in conjunction with a small heap limit (this can be set through the API).

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u2 or higher.

References

low severity
new

Out-of-bounds Write

  • Vulnerable module: pcre2/libpcre2-8-0
  • Introduced through: pcre2/libpcre2-8-0@10.46-1~deb13u1
  • Fixed in: 10.46-1~deb13u3

Detailed paths

  • Introduced through: nginx@mainline › pcre2/libpcre2-8-0@10.46-1~deb13u1

NVD Description

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

PCRE2 before 10.49, when there is an attacker-controlled regular expression and certain JIT API usage, allows an out-of-bounds write with arbitrary data.

Remediation

Upgrade Debian:13 pcre2 to version 10.46-1~deb13u3 or higher.

References

low severity

CVE-2025-15649

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

IO::Uncompress::Unzip versions before 2.215 for Perl propagate uncaught exception when parsing zip header with malformed DOS date.

_dosToUnixTime() decodes the local-file-header last-modification date field and calls Time::Local::timelocal() without an eval guard. A header whose date field decodes to an out-of-range month, day, or hour causes timelocal() to die.

The exception propagates out of IO::Uncompress::Unzip->new($file) where callers expect undef plus $UnzipError.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-12087

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Socket versions before 2.041 for Perl have an out-of-bounds heap read.

In Socket.xs, pack_ip_mreq_source() checks the length of its source argument before the argument is read, so the check tests the byte length carried over from the preceding multiaddr argument instead. Both addresses occupy a 4-byte field, so a valid multiaddr lets a source of any length pass the check, and the source is then copied into the 4-byte imr_sourceaddr field with a fixed-size copy. A source shorter than 4 bytes is not rejected, and the copy reads up to 3 bytes past the end of its buffer.

Calling pack_ip_mreq_source() with a source value shorter than 4 bytes copies adjacent heap memory into the returned packed structure.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-15534

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

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

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

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

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

CVE-2026-19487

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Perl versions from 5.9.4 before 5.41.9 produce incorrect regular expression match results when a stale failure flag ends the Aho-Corasick prescan early in S_find_byclass.

The prescan walks the subject for positions where the full pattern could match, and the engine tries it from the leftmost one recorded. A failing transition sets the failed flag, and a later successful transition does not clear it, so the prescan reads the stale flag as a failure and stops before it can record a candidate that starts earlier. It takes a subject where one candidate is recorded and a later character then forces a fallback through a fail link that succeeds.

Example:

"ABCDE" =~ m/ABCF|BCDE|C/; # matches C at offset 2, not BCDE "ABCDE" =~ m/ABCF|BCDE|C(G)/; # no match, BCDE missed

An alternation like this can miss input it should match, or match it on the wrong branch, so an access or filtering decision made from the result can be wrong.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-48959

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

IO::Uncompress::Unzip versions before 2.220 for Perl allow CPU exhaustion via per-byte read loop in fastForward.

fastForward() compares length $offset (the digit count of the offset, 1 to 19) against the chunk size $c instead of $offset itself, so $c shrinks from 16 KiB to 1-19 bytes per iteration.

Extracting a named entry from an attacker supplied zip via IO::Uncompress::Unzip->new($zip, Name => $target) drives a per-byte read loop scaling with the entry's compressed size, up to the non-Zip64 4 GiB cap.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-48961

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

IO::Compress versions from 2.207 before 2.220 for Perl ship a zipdetails CLI tool that crashes with undefined subroutine on Info-ZIP Unix Extra Field with 8-byte UID or GID.

When decode_ux() in bin/zipdetails handles an Info-ZIP Unix Extra Field (tag 0x7875) with UID Size or GID Size set to 8, causing zipdetails to decode an 8-byte UID or GID value, it dispatches through decodeLitteEndian(), which calls a misnamed helper unpackValueQ. The actual function defined in the same file is unpackValue_Q (with underscore); the call raises 'Undefined subroutine &main::unpackValueQ' and the script exits with status 255.

Library callers of IO::Compress and IO::Uncompress are not affected; the defect is in the bundled CLI tool.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-48962

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

IO::Compress versions before 2.220 for Perl can execute arbitrary code in File::GlobMapper via an attacker-controlled output glob.

_parseOutputGlob() wraps the caller-supplied output glob string in double quotes and stores it in the parser state; _getFiles() then runs the stored expression through eval STRING. A literal double quote in the output glob closes the dquote wrapper, and the characters that follow are evaluated as Perl.

Arbitrary Perl in the output glob executes at the calling process's privilege.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-57433

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

Storable versions before 3.41 for Perl have a signed integer overflow when deserializing a crafted SX_HOOK record.

retrieve_hook_common reads a signed 32-bit item count from an SX_HOOK record and calls av_extend with that count plus one. A count of I32_MAX wraps the addition to a negative value.

A crafted blob passed to thaw or retrieve triggers the overflow; av_extend receives the negative count and dies with a panic, terminating the deserialization.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-7010

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

HTTP::Tiny versions before 0.093 for Perl do not validate CRLF in HTTP request lines or control field header values.

The unvalidated inputs are the method and URI in the request line, the URL host that becomes the Host: header, and HTTP/1.1 control data field values.

An attacker who controls one of these inputs, for example a user supplied URL passed to a webhook or URL fetch endpoint, can inject additional headers and smuggle requests to the upstream server.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-7017

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

HTTP::Tiny versions before 0.095 for Perl forward credential headers to cross-origin redirect targets.

When the server returns a 3xx redirect, _maybe_redirect follows the Location: header and _prepare_headers_and_cb re-merges the caller's headers argument into the new request, without checking whether the redirect target shares an origin with the original URL. Caller-supplied Authorization, Cookie and Proxy-Authorization headers are therefore re-sent to whatever host the redirect names, across scheme, host or port boundaries, and including https to http downgrades that expose them in plaintext on the wire.

The HTTP::Tiny POD note that "Authorization headers will not be included in a redirected request" applied only to the URL-userinfo Basic-auth path, not to headers passed explicitly by the caller.

Remediation

Upgrade Debian:13 perl to version 5.40.1-6+deb13u1 or higher.

References

low severity

CVE-2026-82560

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

Detailed paths

  • Introduced through: nginx@mainline › perl/perl-base@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.

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

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

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

Remediation

There is no fixed version for Debian:13 perl.

References

low severity

CVE-2024-56433

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

Detailed paths

  • Introduced through: nginx@mainline › shadow/login.defs@1:4.17.4-2
  • Introduced through: nginx@mainline › shadow/passwd@1:4.17.4-2

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 shadow.

References

low severity

CVE-2025-70873

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

Detailed paths

  • Introduced through: nginx@mainline › 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

CVE-2026-50812

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

Detailed paths

  • Introduced through: nginx@mainline › 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 NULL pointer dereference in the SQLite Session Extension in SQLite 3.53.1 and SQLite trunk builds before check-in e807d4e3798efd53 allows an attacker who can supply a malformed changeset blob to cause a denial of service. The issue occurs when sqlite3changeset_apply_v3() applies a corrupt changeset and reaches sqlite3_value_type() with a NULL sqlite3_value pointer.

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

CVE-2026-50813

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

Detailed paths

  • Introduced through: nginx@mainline › 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 issue in SQLite before Fossil check-in 869a51ae84df allows a local attacker to obtain sensitive information via the Session Extension changeset concat/changegroup merge path

Remediation

There is no fixed version for Debian:13 sqlite3.

References

low severity

CVE-2026-15059

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

CVE-2026-16742

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

Detailed paths

  • Introduced through: nginx@mainline › systemd/libsystemd0@257.13-1~deb13u1
  • Introduced through: nginx@mainline › systemd/libudev1@257.13-1~deb13u1

NVD Description

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

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

Remediation

There is no fixed version for Debian:13 systemd.

References

low severity

CVE-2026-36849

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

This vulnerability has not been analyzed by NVD yet.

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

CVE-2026-52490

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the process_command_opts() function in tools/tiffcrop.c

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

CVE-2026-52491

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

An issue in libtiff 85f2ac8e0b01cb7db2bbecf4a3b891bdbef67938 allows an attacker to execute arbitrary code via the libtiff/tools/thumbnail.c: main() component

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

CVE-2026-52492

  • Vulnerable module: tiff/libtiff6
  • Introduced through: tiff/libtiff6@4.7.0-3+deb13u3

Detailed paths

  • Introduced through: nginx@mainline › tiff/libtiff6@4.7.0-3+deb13u3

NVD Description

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

An integer overflow in the libtiff rgb2ycbcr utility's cvtRaster() function when computing strip buffer sizes can result in an undersized heap allocation and subsequent heap-based buffer overflow during YCbCr conversion of a crafted TIFF image

Remediation

There is no fixed version for Debian:13 tiff.

References

low severity

Improper Privilege Management

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.5-0+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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.

util-linux is a random collection of Linux utilities. In util-linux 2.39.1 through 2.41.4 and 2.42 through 2.42.1, the SUID mount utility reads the attacker-controlled LIBMOUNT_FORCE_MOUNT2 environment variable with getenv(), allowing a local low-privileged user to force the non-atomic legacy bind-mount path. With an /etc/fstab bind mount authorized by user or users and protected by nosuid, noexec, or nodev, an attacker can race the window between the initial bind mount and the remount that applies those security flags and execute a SUID program from the temporarily unprotected mount, potentially gaining root privileges. This issue is fixed in 2.41.5 and 2.42.2.

Remediation

Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.

References

low severity

Integer Overflow or Wraparound

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.5-0+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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.

util-linux is a random collection of Linux utilities. Before util-linux 2.41.4, parse_dos_extended() in libblkid/src/partitions/dos.c computes an extended-partition start sector with 32-bit addition and does not apply the extended-area bounds checks to the first two EBR entries. A local attacker who causes a crafted DOS extended-partition disk image or removable medium to be probed can wrap cur_start + start to sector zero and cause libblkid to report a false partition overlapping the MBR. This directly compromises the integrity of the reported partition metadata; disk modification or availability loss requires a separate downstream consumer to act on that metadata. This issue is fixed in 2.41.4.

Remediation

Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.

References

low severity

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

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.5-0+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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.

util-linux is a random collection of Linux utilities. Prior to version 2.41.4, a TOCTOU (Time-of-Check-Time-of-Use) vulnerability has been identified in the SUID binary /usr/bin/mount from util-linux. The mount binary, when setting up loop devices, validates the source file path with user privileges via fork() + setuid() + realpath(), but subsequently re-canonicalizes and opens it with root privileges (euid=0) without verifying that the path has not been replaced between both operations. Neither O_NOFOLLOW, nor inode comparison, nor post-open fstat() are employed. This allows a local unprivileged user to replace the source file with a symlink pointing to any root-owned file or device during the race window, causing the SUID binary to open and mount it as root. Exploitation requires an /etc/fstab entry with user,loop options whose path points to a directory where the attacker has write permission, and that /usr/bin/mount has the SUID bit set (the default configuration on virtually all Linux distributions). The impact is unauthorized read access to root-protected files and block devices, including backup images, disk volumes, and any file containing a valid filesystem. This issue has been patched in version 2.41.4.

Remediation

Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.

References

low severity

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

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.5-0+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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.

util-linux is a random collection of Linux utilities. In util-linux 2.39 through 2.41.4 and 2.42 through 2.42.1, the SUID mount utility's hook_owner.c post-mount hook performs path-based chmod() and lchown() operations on a previously validated mount target. A local low-privileged user authorized by an /etc/fstab entry with user or users and an X-mount.mode, X-mount.owner, or X-mount.group option can use renameat2(RENAME_EXCHANGE) to race a writable ancestor of the target and redirect the privileged ownership or mode change to a root-owned path, potentially gaining root privileges. This issue is fixed in 2.41.5 and 2.42.2.

Remediation

Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.

References

low severity

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

  • Vulnerable module: util-linux
  • Introduced through: util-linux@2.41-5, util-linux/libblkid1@2.41-5 and others
  • Fixed in: 2.41.5-0+deb13u1

Detailed paths

  • Introduced through: nginx@mainline › util-linux@2.41-5
  • Introduced through: nginx@mainline › util-linux/libblkid1@2.41-5
  • Introduced through: nginx@mainline › util-linux/liblastlog2-2@2.41-5
  • Introduced through: nginx@mainline › util-linux/libmount1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libsmartcols1@2.41-5
  • Introduced through: nginx@mainline › util-linux/libuuid1@2.41-5
  • Introduced through: nginx@mainline › 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.

util-linux is a random collection of Linux utilities. In util-linux 2.17 through 2.41.6 and 2.42 through 2.42.3, and in 2.42.4 when the legacy mount(2) path is used without /proc, restricted non-root mount requests validate an /etc/fstab target before the mount operation re-resolves that pathname. A local low-privileged user authorized by an fstab user or users entry whose target has an attacker-writable ancestor can use renameat2(RENAME_EXCHANGE) to swap a path component and redirect an authorized mount to a root-owned location, such as mounting attacker-controlled content over /etc/sudoers.d, and thereby gain root privileges. Versions 2.41.5 and 2.42.2 pin targets for the new mount API, and 2.42.4 pins legacy targets through /proc/self/fd; the documented legacy fallback without /proc remains affected.

Remediation

Upgrade Debian:13 util-linux to version 2.41.5-0+deb13u1 or higher.

References