Vulnerabilities |
315 via 596 paths |
|---|---|
Dependencies |
106 |
Source |
Docker |
Target OS |
debian:12 |
critical severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. Servers configured with RSA-PSK (Rivest–Shamir–Adleman – Pre-Shared Key) wrongfully matched usernames containing a NUL character with truncated usernames. A remote attacker could exploit this by sending a specially crafted username, leading to an authentication bypass. This vulnerability allows an attacker to gain unauthorized access by circumventing the authentication process.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42010
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-4
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42010.json
- https://access.redhat.com/errata/RHSA-2026:67857
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34764
- https://access.redhat.com/errata/RHSA-2026:34788
- https://access.redhat.com/errata/RHSA-2026:34790
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:62409
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-42010
- https://bugzilla.redhat.com/show_bug.cgi?id=2467289
critical severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms.
Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior.
If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow.
Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-31789
- https://github.com/openssl/openssl/commit/364f095b80601db632b0def6a33316967f863bde
- https://github.com/openssl/openssl/commit/7a9087efd769f362ad9c0e30c7baaa6bbfa65ecf
- https://github.com/openssl/openssl/commit/945b935ac66cc7f1a41f1b849c7c25adb5351f49
- https://github.com/openssl/openssl/commit/a24216018e1ede8ff01a4ff5afff7dfbd443e2f9
- https://github.com/openssl/openssl/commit/a91e537d16d74050dbde50bb0dfb1fe9930f0521
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
critical severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
critical severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: python@3.8-slim › zlib/zlib1g@1:1.2.13.dfsg-1
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:12 relevant fixed versions and status.
MiniZip in zlib through 1.3 has an integer overflow and resultant heap-based buffer overflow in zipOpenNewFileInZip4_64 via a long filename, comment, or extra field. NOTE: MiniZip is not a supported part of the zlib product. NOTE: pyminizip through 0.2.6 is also vulnerable because it bundles an affected zlib version, and exposes the applicable MiniZip code through its compress API.
Remediation
There is no fixed version for Debian:12 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2023-45853
- http://www.openwall.com/lists/oss-security/2023/10/20/9
- http://www.openwall.com/lists/oss-security/2024/01/24/10
- https://chromium.googlesource.com/chromium/src/+/d709fb23806858847131027da95ef4c548813356
- https://chromium.googlesource.com/chromium/src/+/de29dd6c7151d3cd37cb4cf0036800ddfb1d8b61
- https://github.com/madler/zlib/blob/ac8f12c97d1afd9bafa9c710f827d40a407d3266/contrib/README.contrib#L1-L4
- https://github.com/madler/zlib/pull/843
- https://lists.debian.org/debian-lts-announce/2023/11/msg00026.html
- https://pypi.org/project/pyminizip/#history
- https://security.gentoo.org/glsa/202401-18
- https://security.netapp.com/advisory/ntap-20231130-0009/
- https://www.winimage.com/zLibDll/minizip.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-470355.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
critical severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw in GnuTLS DTLS handshake parsing allows malformed fragments with zero length and non-zero offset, leading to an integer underflow during reassembly and resulting in an out-of-bounds read. This issue is remotely exploitable and may cause information disclosure or denial of service.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33845
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33845.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34372
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:57402
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-33845
- https://bugzilla.redhat.com/show_bug.cgi?id=2450624
critical severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13221
- https://github.com/Perl/perl5/commit/03f74bbbd3a68350d926ee93d56ee4808c28c4c7.patch
- https://github.com/Perl/perl5/issues/23388
- http://www.openwall.com/lists/oss-security/2026/07/13/5
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
critical severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42496
- https://github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158.patch
- https://metacpan.org/release/BINGOS/Archive-Tar-3.08/changes
- https://www.cve.org/CVERecord?id=CVE-2026-42497
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30852
- https://access.redhat.com/errata/RHSA-2026:30856
- https://access.redhat.com/errata/RHSA-2026:30857
- https://access.redhat.com/security/cve/CVE-2026-42496
- https://bugzilla.redhat.com/show_bug.cgi?id=2481314
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42496.json
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-57432
- https://github.com/Perl/perl5/commit/40754edc72dd3e513d758153c0e2f0215897740e.patch
- https://github.com/Perl/perl5/commit/5f7eb6bbbe0510964e3fb1d6bb691e5445913e55.patch
- http://www.openwall.com/lists/oss-security/2026/07/13/6
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-118370
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/a76b1174c1ea52abb639a4c69d52b630a8a106a2/expat/lib/xmlparse.c#L4138-L4140
- https://github.com/libexpat/libexpat/commit/1bac53c4fc460a03cd9860f39501c7979f6750ae
- https://github.com/libexpat/libexpat/commit/621cb2c78b253ee023a86bc91d6ddb048481c04c
- https://github.com/libexpat/libexpat/pull/1450
- https://www.vulncheck.com/advisories/libexpat-through-2.9.0-integer-overflow-in-storeatts-via-attindex-and-nprefixes
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat to version 2.5.0-1+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-77214
- https://github.com/libexpat/libexpat/commit/13c5f63a7f1c52c2feee3b16a1134d4fb68e9ea0
- https://github.com/libexpat/libexpat/pull/1393
- https://www.vulncheck.com/advisories/libexpat-heap-buffer-over-read-in-xmlparse-c-via-xml-parsebuffer
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in GnuTLS. A double-free vulnerability exists in GnuTLS due to incorrect ownership handling in the export logic of Subject Alternative Name (SAN) entries containing an otherName. If the type-id OID is invalid or malformed, GnuTLS will call asn1_delete_structure() on an ASN.1 node it does not own, leading to a double-free condition when the parent function or caller later attempts to free the same structure.
This vulnerability can be triggered using only public GnuTLS APIs and may result in denial of service or memory corruption, depending on allocator behavior.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32988
- https://access.redhat.com/security/cve/CVE-2025-32988
- https://bugzilla.redhat.com/show_bug.cgi?id=2359622
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A heap-buffer-overflow (off-by-one) flaw was found in the GnuTLS software in the template parsing logic within the certtool utility. When it reads certain settings from a template file, it allows an attacker to cause an out-of-bounds (OOB) NULL pointer write, resulting in memory corruption and a denial-of-service (DoS) that could potentially crash the system.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32990
- https://access.redhat.com/security/cve/CVE-2025-32990
- https://bugzilla.redhat.com/show_bug.cgi?id=2359620
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. When validating certificates, an oversized Subject Alternative Name (SAN) could cause the validation process to incorrectly fall back to checking the Common Name (CN) field. This could allow a remote attacker to bypass proper certificate validation, potentially leading to spoofing or man-in-the-middle attacks.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42013
- https://access.redhat.com/security/cve/CVE-2026-42013
- https://bugzilla.redhat.com/show_bug.cgi?id=2467448
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-8
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:89197
- https://access.redhat.com/errata/RHSA-2026:89232
- https://access.redhat.com/errata/RHSA-2026:89333
- https://access.redhat.com/errata/RHSA-2026:95508
- https://access.redhat.com/errata/RHSA-2026:95745
- https://access.redhat.com/errata/RHSA-2026:95755
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in libgnutls. A remote attacker, by sending an extremely short premaster secret during an RSA key exchange to a server using an RSA key backed by a PKCS#11 token, could trigger a short heap overread. This memory corruption vulnerability could lead to information disclosure.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5260
- https://access.redhat.com/security/cve/CVE-2026-5260
- https://bugzilla.redhat.com/show_bug.cgi?id=2467450
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-10
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:67837
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:77320
- https://access.redhat.com/errata/RHSA-2026:82811
- https://access.redhat.com/errata/RHSA-2026:89197
- https://access.redhat.com/errata/RHSA-2026:89232
- https://access.redhat.com/errata/RHSA-2026:89333
- https://access.redhat.com/errata/RHSA-2026:89651
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side.
Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code.
However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage.
By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.
The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records.
No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28387
- https://github.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b
- https://github.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe
- https://github.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3
- https://github.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7
- https://github.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 relevant fixed versions and status.
CPAN.pm before 2.35 does not verify TLS certificates when downloading distributions over HTTPS.
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31484
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/andk/cpanpm/pull/175
- https://lists.debian.org/debian-lts-announce/2024/10/msg00017.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/BM6UW55CNFUTNGD5ZRKGUKKKFDJGMFHL/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LEGCEOKFJVBJ2QQ6S2H4NAEWTUERC7SB/
- https://metacpan.org/dist/CPAN/changes
- https://security.netapp.com/advisory/ntap-20240621-0007/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
In libexpat before 2.7.4, the doContent function does not properly determine the buffer size bufSize because there is no integer overflow check for tag buffer reallocation.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-25210
- https://github.com/libexpat/libexpat/pull/1075
- https://github.com/libexpat/libexpat/pull/1075/commits/9c2d990389e6abe2e44527eeaa8b39f16fe859c7
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat to version 2.5.0-1+deb12u3 or higher.
References
high severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam0g@1.5.2-6+deb12u1
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:12 relevant fixed versions and status.
A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.
Remediation
There is no fixed version for Debian:12 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6020
- https://access.redhat.com/security/cve/CVE-2025-6020
- https://bugzilla.redhat.com/show_bug.cgi?id=2372512
- http://www.openwall.com/lists/oss-security/2025/06/17/1
- https://access.redhat.com/errata/RHSA-2025:9526
- https://access.redhat.com/errata/RHSA-2025:10024
- https://access.redhat.com/errata/RHSA-2025:10027
- https://access.redhat.com/errata/RHSA-2025:10180
- https://access.redhat.com/errata/RHSA-2025:10354
- https://access.redhat.com/errata/RHSA-2025:10357
- https://access.redhat.com/errata/RHSA-2025:10358
- https://access.redhat.com/errata/RHSA-2025:10359
- https://access.redhat.com/errata/RHSA-2025:10361
- https://access.redhat.com/errata/RHSA-2025:10362
- https://access.redhat.com/errata/RHSA-2025:10735
- https://access.redhat.com/errata/RHSA-2025:10823
- https://access.redhat.com/errata/RHSA-2025:11386
- https://access.redhat.com/errata/RHSA-2025:11487
- https://access.redhat.com/errata/RHSA-2025:14557
- https://access.redhat.com/errata/RHSA-2025:15099
- https://access.redhat.com/errata/RHSA-2025:15709
- https://access.redhat.com/errata/RHSA-2025:15828
- https://access.redhat.com/errata/RHSA-2025:15827
- https://access.redhat.com/errata/RHSA-2025:16524
- https://access.redhat.com/errata/RHSA-2025:18219
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:20181
- https://access.redhat.com/errata/RHSA-2025:21885
- https://access.redhat.com/errata/RHSA-2025:22019
- https://access.redhat.com/errata/RHSA-2026:0934
- https://github.com/linux-pam/linux-pam/security/advisories/GHSA-f9p8-gjr4-j9gx
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
high severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u1 or higher.
References
high severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5DoSecureDelete() that allows attackers to write past the leaf page buffer via crafted footer key offsets. Attackers can supply a database file with a corrupted FTS5 index that, when deleted from with secure-delete enabled, corrupts heap memory and crashes the application.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119374
- https://abraxaslabs.tech/research/sqlite-fts5-securedel
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/ext/fts5/fts5_index.c#L5525
- https://github.com/sqlite/sqlite/commit/d9de6eedbe918c074c7556400fa21df5960704d9
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/9cd4f9e920
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-heap-buffer-overflow-via-fts5-fts5dosecuredelete
high severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 built with FTS5 contains a heap buffer overflow in fts5MergeRowidLists() that undersizes the output buffer when merging detail=none prefix doclists. Attackers who can populate a detail=none FTS5 table with negative rowids and run a prefix MATCH query can write past the allocation, corrupting heap memory and crashing the process.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119373
- https://abraxaslabs.tech/research/sqlite-fts5-rowidmerge
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/ext/fts5/fts5_index.c#L6107
- https://github.com/sqlite/sqlite/commit/e1c9934f9f11a499029abb020ea715a08970da80
- https://sqlite.org/bugs/info/2026-08-04T08:49:27Z
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/a7f8c92f62
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-fts5-heap-buffer-overflow-via-fts5mergerowidlists
high severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 built with the session extension contains a heap buffer overflow vulnerability in sqlite3changeset_apply() that allows attackers to corrupt heap memory by supplying crafted changesets. Attackers can repeat a table name in a second changeset block with a larger column count, causing sessionUpdateFind() to memset past the undersized aUpdateMask allocation.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119379
- https://abraxaslabs.tech/research/sqlite-session-ncol
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/ext/session/sqlite3session.c#L5619
- https://github.com/sqlite/sqlite/commit/64459c87cc702d600704fb77ee40ca1782398a52
- https://sqlite.org/bugs/info/2026-08-16T10:15:25Z
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/3f57024aecea0f3b
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-heap-buffer-overflow-via-session-extension-sessionupdatefind
high severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-78410
- https://access.redhat.com/security/cve/CVE-2026-78410
- https://bugzilla.redhat.com/show_bug.cgi?id=2522684
- https://access.redhat.com/errata/RHSA-2026:63162
- https://access.redhat.com/errata/RHSA-2026:93461
- https://access.redhat.com/errata/RHSA-2026:95365
- https://github.com/util-linux/util-linux/security/advisories/GHSA-rh77-686x-2f2m
high severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
- Fixed in: 3.40.1-2+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
There exists a vulnerability in SQLite versions before 3.50.2 where the number of aggregate terms could exceed the number of columns available. This could lead to a memory corruption issue. We recommend upgrading to version 3.50.2 or above.
Remediation
Upgrade Debian:12 sqlite3 to version 3.40.1-2+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6965
- https://www.sqlite.org/src/info/5508b56fd24016c13981ec280ecdd833007c9d8dd595edb295b984c2b487b5c8
- http://seclists.org/fulldisclosure/2025/Sep/49
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/56
- http://seclists.org/fulldisclosure/2025/Sep/57
- http://seclists.org/fulldisclosure/2025/Sep/58
- http://www.openwall.com/lists/oss-security/2025/09/06/1
- https://cert-portal.siemens.com/productcert/html/ssa-225816.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-765416.html
- https://www.exploit-db.com/exploits/52499
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
In libexpat before 2.8.1, the computational complexity of attribute name collision checks allows a denial of service via moderately sized crafted XML input.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-45186
- https://github.com/libexpat/libexpat/pull/1216
- http://www.openwall.com/lists/oss-security/2026/05/11/16
- https://access.redhat.com/errata/RHSA-2026:22715
- https://access.redhat.com/errata/RHSA-2026:22721
- https://access.redhat.com/errata/RHSA-2026:23230
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:27201
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/security/cve/CVE-2026-45186
- https://bugzilla.redhat.com/show_bug.cgi?id=2468575
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45186.json
- https://access.redhat.com/errata/RHSA-2026:58981
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat to version 2.5.0-1+deb12u4 or higher.
References
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat to version 2.5.0-1+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-93990
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/commit/ff6e1d7e750bbe245178f51a47a965dc8342861a
- https://github.com/libexpat/libexpat/pull/1282
- https://www.vulncheck.com/advisories/expat-through-2.8.4-malformed-utf-16-acceptance-via-unchecked-surrogate
- https://blog.hartwork.org/posts/expat-2-8-5-released/
- https://github.com/libexpat/libexpat/releases/tag/R_2_8_5
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat through 2.6.1 allows an XML Entity Expansion attack when there is isolated use of external parsers (created via XML_ExternalEntityParserCreate).
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-28757
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
- http://www.openwall.com/lists/oss-security/2024/03/15/1
- https://github.com/libexpat/libexpat/issues/839
- https://github.com/libexpat/libexpat/pull/842
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FPLC6WDSRDUYS7F7JWAOVOHFNOUQ43DD/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LKJ7V5F6LJCEQJXDBWGT27J7NAP3E3N7/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VK2O34GH43NTHBZBN7G5Y6YKJKPUCTBE/
- https://security.netapp.com/advisory/ntap-20240322-0001/
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-117610
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/a76b1174c1ea52abb639a4c69d52b630a8a106a2/expat/lib/xmlparse.c#L3468-L3510
- https://github.com/libexpat/libexpat/commit/7b0d50e4b1d16fafd55876260701e04279a7489d
- https://github.com/libexpat/libexpat/pull/1444
- https://www.vulncheck.com/advisories/libexpat-through-2.9.0-null-pointer-dereference-via-external-entity-subparser
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat through 2.5.0 allows a denial of service (resource consumption) because many full reparsings are required in the case of a large token for which multiple buffer fills are needed.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52425
- https://lists.debian.org/debian-lts-announce/2024/09/msg00036.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- http://www.openwall.com/lists/oss-security/2024/03/20/5
- https://github.com/libexpat/libexpat/pull/789
- https://lists.debian.org/debian-lts-announce/2024/04/msg00006.html
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://security.netapp.com/advisory/ntap-20240614-0003/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
high severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
A stack overflow vulnerability exists in the libexpat library due to the way it handles recursive entity expansion in XML documents. When parsing an XML document with deeply nested entity references, libexpat can be forced to recurse indefinitely, exhausting the stack space and causing a crash. This issue could lead to denial of service (DoS) or, in some cases, exploitable memory corruption, depending on the environment and library usage.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-8176
- https://access.redhat.com/security/cve/CVE-2024-8176
- https://bugzilla.redhat.com/show_bug.cgi?id=2310137
- https://github.com/libexpat/libexpat/issues/893
- http://www.openwall.com/lists/oss-security/2025/03/15/1
- https://blog.hartwork.org/posts/expat-2-7-0-released/
- https://bugzilla.suse.com/show_bug.cgi?id=1239618
- https://github.com/libexpat/libexpat/blob/R_2_7_0/expat/Changes#L40-L52
- https://gitlab.alpinelinux.org/alpine/aports/-/commit/d068c3ff36fc6f4789988a09c69b434db757db53
- https://ubuntu.com/security/CVE-2024-8176
- https://security.netapp.com/advisory/ntap-20250328-0009/
- https://access.redhat.com/errata/RHSA-2025:3531
- https://access.redhat.com/errata/RHSA-2025:3734
- https://access.redhat.com/errata/RHSA-2025:3913
- https://access.redhat.com/errata/RHSA-2025:4048
- https://access.redhat.com/errata/RHSA-2025:4447
- https://access.redhat.com/errata/RHSA-2025:4446
- https://access.redhat.com/errata/RHSA-2025:4448
- https://access.redhat.com/errata/RHSA-2025:4449
- https://www.kb.cert.org/vuls/id/760160
- https://access.redhat.com/errata/RHSA-2025:7444
- https://access.redhat.com/errata/RHSA-2025:7512
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:13681
- http://seclists.org/fulldisclosure/2025/May/10
- http://seclists.org/fulldisclosure/2025/May/11
- http://seclists.org/fulldisclosure/2025/May/12
- http://seclists.org/fulldisclosure/2025/May/6
- http://seclists.org/fulldisclosure/2025/May/7
- http://seclists.org/fulldisclosure/2025/May/8
- http://www.openwall.com/lists/oss-security/2025/09/24/11
- https://access.redhat.com/errata/RHSA-2025:22033
- https://access.redhat.com/errata/RHSA-2025:22035
- https://access.redhat.com/errata/RHSA-2025:22034
- https://access.redhat.com/errata/RHSA-2025:22607
- https://access.redhat.com/errata/RHSA-2025:22785
- https://access.redhat.com/errata/RHSA-2025:22842
- https://access.redhat.com/errata/RHSA-2025:22871
- https://github.com/libexpat/libexpat/pull/973
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A heap buffer overflow vulnerability exists in the DTLS handshake fragment reassembly logic of GnuTLS. The issue arises in merge_handshake_packet() where incoming handshake fragments are matched and merged based solely on handshake type, without validating that the message_length field remains consistent across all fragments of the same logical message. An attacker can exploit this by sending crafted DTLS fragments with conflicting message_length values, causing the implementation to allocate a buffer based on a smaller initial fragment and subsequently write beyond its bounds using larger, inconsistent fragments. Because the merge operation does not enforce proper bounds checking against the allocated buffer size, this results in an out-of-bounds write on the heap. The vulnerability is remotely exploitable without authentication via the DTLS handshake path and can lead to application crashes or potential memory corruption.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-33846
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-33846.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34372
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:57402
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-33846
- https://bugzilla.redhat.com/show_bug.cgi?id=2450625
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. A remote attacker could exploit an issue in the Datagram Transport Layer Security (DTLS) packet reordering logic. The comparator function, responsible for ordering DTLS packets by sequence numbers, did not correctly handle packets with duplicate sequence numbers. This could lead to unstable packet ordering or undefined behavior, resulting in a denial of service.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42009
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-2
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-42009.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:29794
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:34372
- https://access.redhat.com/errata/RHSA-2026:34764
- https://access.redhat.com/errata/RHSA-2026:34788
- https://access.redhat.com/errata/RHSA-2026:36004
- https://access.redhat.com/errata/RHSA-2026:36005
- https://access.redhat.com/errata/RHSA-2026:36006
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:56786
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:56911
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/security/cve/CVE-2026-42009
- https://bugzilla.redhat.com/show_bug.cgi?id=2467279
high severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
clean_client() in lib/rpc/svc_auth_gssapi.c in MIT Kerberos 5 (aka krb5) restarts its scan from the head of the client list after each removal, resulting in quadratic CPU cost. Remote attackers can cause a denial of service (CPU consumption in kadmind) by accumulating a large number of AUTH_GSSAPI client entries.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112322
- https://access.redhat.com/security/cve/CVE-2026-112322
- https://bugzilla.redhat.com/show_bug.cgi?id=2478445
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
high severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
decode_sequence_of() in lib/krb5/asn.1/asn1_encode.c in MIT Kerberos 5 (aka krb5) 1.11 and later grows the decoded element array one entry at a time, which allows remote attackers to cause a denial of service (CPU consumption in the KDC) by sending an unauthenticated AS-REQ or TGS-REQ with a large number of elements in a SEQUENCE OF field over TCP.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119079
- https://access.redhat.com/security/cve/CVE-2026-119079
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
- https://bugzilla.redhat.com/show_bug.cgi?id=2479231
high severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22.3, there is an integer underflow and resultant out-of-bounds read if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, possibly causing the process to terminate in parse_message.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u5 or higher.
References
high severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
The AUTH_GSSAPI handler in lib/rpc/svc_auth_gssapi.c in MIT Kerberos 5 (aka krb5) does not free decoded arguments on certain error paths, which allows remote attackers to cause a denial of service (memory exhaustion in kadmind) via crafted AUTH_GSSAPI_INIT requests that trigger authentication failures.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112321
- https://access.redhat.com/security/cve/CVE-2026-112321
- https://bugzilla.redhat.com/show_bug.cgi?id=2478448
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
high severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
The AUTH_GSSAPI handler in lib/rpc/svc_auth_gssapi.c in MIT Kerberos 5 (aka krb5) 1.5.2 and later allows remote attackers to cause a denial of service (memory exhaustion in kadmind) by sending repeated failed AUTH_GSSAPI_INIT requests. Each failed request allocates client state that is only freed after a 15-minute expiration timeout, allowing an attacker to accumulate memory faster than it is reclaimed.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112323
- https://access.redhat.com/security/cve/CVE-2026-112323
- https://bugzilla.redhat.com/show_bug.cgi?id=2478440
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
high severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
clnttcp_call() in lib/rpc/clnt_tcp.c in MIT Kerberos 5 (aka krb5) does not free the RPC reply verifier between retries, which allows remote attackers to cause a denial of service (memory leak in GSS-RPC client programs) by injecting RPC replies with mismatched XIDs or by triggering authentication retries.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112314
- https://access.redhat.com/security/cve/CVE-2026-112314
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
- https://bugzilla.redhat.com/show_bug.cgi?id=2478446
high severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
The GSS-RPC transport layer in MIT Kerberos 5 (aka krb5) 1.4 and later does not release the previous authentication context when a client switches from an RPCSEC_GSS or AUTH_GSSAPI flavor to a non-GSS flavor on the same TCP connection. This allows remote attackers to cause a denial of service (memory exhaustion in kadmind) by repeatedly establishing and abandoning GSS authentication contexts.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112320
- https://access.redhat.com/security/cve/CVE-2026-112320
- https://bugzilla.redhat.com/show_bug.cgi?id=2478449
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
high severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22.3, there is a NULL pointer dereference if an application calls gss_accept_sec_context() on a system with a NegoEx mechanism registered in /etc/gss/mech. An unauthenticated remote attacker can trigger this, causing the process to terminate in parse_nego_message.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-40355
- https://github.com/krb5/krb5/commit/2e75f0d9362fb979f5fc92829431a590a130929f
- https://web.mit.edu/kerberos/advisories/
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
- https://cems.fun/2026/04/27/krb5-two-unauthenticated-network-vulnerabilities.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69421
- https://github.com/openssl/openssl/commit/3524a29271f8191b8fd8a5257eb05173982a097b
- https://github.com/openssl/openssl/commit/36ecb4960872a4ce04bf6f1e1f4e78d75ec0c0c7
- https://github.com/openssl/openssl/commit/4bbc8d41a72c842ce4077a8a3eccd1109aaf74bd
- https://github.com/openssl/openssl/commit/643986985cd1c21221f941129d76fe0c2785aeb3
- https://github.com/openssl/openssl/commit/a2dbc539f0f9cc63832709fa5aa33ad9495eb19c
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing.
Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application.
When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference.
Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it.
The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28388
- https://github.com/openssl/openssl/commit/59c3b3158553ab53275bbbccca5cb305d591cf2e
- https://github.com/openssl/openssl/commit/5a0b4930779cd2408880979db765db919da55139
- https://github.com/openssl/openssl/commit/602542f2c0c2d5edb47128f93eac10b62aeeefb3
- https://github.com/openssl/openssl/commit/a9d187dd1000130100fa7ab915f8513532cb3bb8
- https://github.com/openssl/openssl/commit/d3a901e8d9f021f3e67d6cfbc12e768129862726
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28389
- https://github.com/openssl/openssl/commit/16cea4188e0ea567deb4f93f85902247e67384f5
- https://github.com/openssl/openssl/commit/785cbf7ea3b5a6f5adf0c1ccb92b79d89c35c616
- https://github.com/openssl/openssl/commit/7b5274e812400cacb6f3be4c2df5340923fa807f
- https://github.com/openssl/openssl/commit/c6725634e089eb2b634b10ede33944be7248172a
- https://github.com/openssl/openssl/commit/f80f83bc5fd036bc47d773e8b15a001e2b4ce686
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen.
Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.
When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.
Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-28390
- https://github.com/openssl/openssl/commit/01194a8f1941115cd0383bfa91c736dd3993c8bc
- https://github.com/openssl/openssl/commit/2e39b7a6993be445fddb9fbce316fa756e0397b6
- https://github.com/openssl/openssl/commit/af2a5fecd3e71a29e7568f9c1453dec5cebbaff4
- https://github.com/openssl/openssl/commit/ea7b4ea4f9f853521ba34830cbcadc970d2e0788
- https://github.com/openssl/openssl/commit/fd2f1a6cf53b9ceeca723a001aa4b825d7c7ee75
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
high severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42497
- https://github.com/jib/archive-tar-new/commit/17c873492a05eddc0de18c1485e0b2cccd5a9158.patch
- https://metacpan.org/release/BINGOS/Archive-Tar-3.08/changes
- https://www.cve.org/CVERecord?id=CVE-2026-42496
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. This vulnerability occurs because permitted name constraints were incorrectly ignored when previous Certificate Authorities (CAs) only had excluded name constraints. A remote attacker could exploit this to bypass critical name constraint checks during certificate validation. This bypass could lead to the acceptance of invalid certificates, potentially enabling spoofing or man-in-the-middle attacks against affected systems.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42011
- https://access.redhat.com/security/cve/CVE-2026-42011
- https://bugzilla.redhat.com/show_bug.cgi?id=2467437
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:40762
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-6
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57483
- https://access.redhat.com/errata/RHSA-2026:56853
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:89197
- https://access.redhat.com/errata/RHSA-2026:89232
- https://access.redhat.com/errata/RHSA-2026:89333
- https://access.redhat.com/errata/RHSA-2026:95508
- https://access.redhat.com/errata/RHSA-2026:95745
- https://access.redhat.com/errata/RHSA-2026:95755
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. This vulnerability occurs because gnutls performs case-sensitive comparisons of nameConstraints labels, specifically for dNSName (DNS) or rfc822Name (email) constraints within excludedSubtrees or permittedSubtrees. A remote attacker can exploit this by crafting a leaf certificate with casing differences in the Subject Alternative Name (SAN), leading to a policy bypass where a certificate that should be rejected is instead accepted. This could result in unauthorized access or information disclosure.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-3833
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/security/cve/CVE-2026-3833
- https://bugzilla.redhat.com/show_bug.cgi?id=2445763
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:57402
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:60019
- https://access.redhat.com/errata/RHSA-2026:62549
- https://access.redhat.com/errata/RHSA-2026:62409
- https://access.redhat.com/errata/RHSA-2026:65851
- https://access.redhat.com/errata/RHSA-2026:65839
- https://access.redhat.com/errata/RHSA-2026:67857
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://gitlab.com/gnutls/gnutls/-/issues/1803
high severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u1 or higher.
References
high severity
new
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: python@3.8-slim › zlib/zlib1g@1:1.2.13.dfsg-1
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:12 relevant fixed versions and status.
webpack-dev-middleware 5.3.4, 6.1.2 through 6.1.3, 7.1.0 before 7.4.6, and 8.0.0 before 8.3.0 contains a path traversal vulnerability in getFilenameFromUrl that bypasses the fix for CVE-2024-29180: a publicPath without a trailing slash is matched by string prefix, and the '..' guard runs before that prefix is stripped. Unauthenticated attackers can request a path such as /assets../secret to read files one directory above the output directory when the middleware serves from the physical filesystem through writeToDisk or a custom outputFileSystem.
Remediation
There is no fixed version for Debian:12 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2026-76844
- https://github.com/advisories/GHSA-wr3j-pwj9-hqq6
- https://github.com/webpack/webpack-dev-middleware
- https://github.com/webpack/webpack-dev-middleware/blob/v8.1.1/src/middleware.js
- https://www.vulncheck.com/advisories/webpack-dev-middleware-path-traversal-via-offset-slice-on-a-non-slash-terminated-publicpath
- https://github.com/webpack/webpack-dev-middleware/commit/13344e78b26d88fe9b7c8381a3860e248a52359b
- https://github.com/webpack/webpack-dev-middleware/commit/cefccbac330c29052fc6dffe85fd292ea2ac782b
- https://github.com/webpack/webpack-dev-middleware/releases/tag/v7.4.6
- https://github.com/webpack/webpack-dev-middleware/releases/tag/v8.3.0
- https://github.com/webpack/webpack-dev-middleware/security/advisories/GHSA-g84c-rxfj-3j2c
- https://gist.github.com/thesmartshadow/e0b9481792afb7c31e86fee1ff084490
- https://github.com/madler/zlib
- https://github.com/madler/zlib/blob/v1.3.2/gzwrite.c#L393
- https://github.com/madler/zlib/commit/df84af25dc1942490e1d1c899a07619152a46148
- https://www.vulncheck.com/advisories/zlib-1.3.1.2-through-1.3.2-heap-buffer-overflow-via-gz-vacate
high severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: python@3.8-slim › zlib/zlib1g@1:1.2.13.dfsg-1
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:12 relevant fixed versions and status.
zlib 1.2.11 through 1.3.2 contains a heap buffer overflow: after an underlying write() fails, gz_write() returns without resetting strm.next_in, leaving it pointed at the caller's buffer. A later gz* write call then derives a position from the stale pointer and writes past a heap allocation; any write() failure reaches it, including EPIPE on a blocking descriptor, and in versions before 1.3.1.2 the failed write must be followed by a gzclearerr() call.
Remediation
There is no fixed version for Debian:12 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2026-85091
- https://gist.github.com/thesmartshadow/e0b9481792afb7c31e86fee1ff084490
- https://github.com/madler/zlib
- https://github.com/madler/zlib/blob/v1.3.2/gzwrite.c#L393
- https://www.vulncheck.com/advisories/zlib-1.3.1.2-through-1.3.2-heap-buffer-overflow-via-gz-vacate
- https://github.com/madler/zlib/commit/df84af25dc1942490e1d1c899a07619152a46148
high severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
- Fixed in: 3.40.1-2+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
A vulnerability was found in SQLite SQLite3 up to 3.43.0 and classified as critical. This issue affects the function sessionReadRecord of the file ext/session/sqlite3session.c of the component make alltest Handler. The manipulation leads to heap-based buffer overflow. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248999.
Remediation
Upgrade Debian:12 sqlite3 to version 3.40.1-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-7104
- https://lists.debian.org/debian-lts-announce/2024/09/msg00050.html
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/AYONA2XSNFMXLAW4IHLFI5UVV3QRNG5K/
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/D6C2HN4T2S6GYNTAUXLH45LQZHK7QPHP/
- https://security.netapp.com/advisory/ntap-20240112-0008/
- https://sqlite.org/forum/forumpost/5bcbf4571c
- https://sqlite.org/src/info/0e4e7a05c4204b47
- https://vuldb.com/?ctiid.248999
- https://vuldb.com/?id.248999
- https://cert-portal.siemens.com/productcert/html/ssa-000297.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
high severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. A remote attacker could exploit this vulnerability by presenting a specially crafted certificate that contains Uniform Resource Identifier (URI) or Service (SRV) Subject Alternative Names (SANs). This could cause the certificate validation process to incorrectly fall back to checking DNS hostnames against the Common Name (CN), potentially allowing the attacker to spoof legitimate services or intercept sensitive information.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42012
- https://access.redhat.com/security/cve/CVE-2026-42012
- https://bugzilla.redhat.com/show_bug.cgi?id=2467441
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-7
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:89197
- https://access.redhat.com/errata/RHSA-2026:89232
- https://access.redhat.com/errata/RHSA-2026:89333
- https://access.redhat.com/errata/RHSA-2026:94442
high severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.40-1.1
- Fixed in: 2.2.40-1.1+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
Remediation
Upgrade Debian:12 gnupg2 to version 2.2.40-1.1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68973
- https://github.com/gpg/gnupg/blob/ff30683418695f5d2cc9e6cf8c9418e09378ebe4/g10/armor.c#L1305-L1306
- https://github.com/gpg/gnupg/commit/115d138ba599328005c5321c0ef9f00355838ca9
- https://github.com/gpg/gnupg/compare/gnupg-2.2.50...gnupg-2.2.51
- https://media.ccc.de/v/39c3-to-sign-or-not-to-sign-practical-vulnerabilities-i
- https://news.ycombinator.com/item?id=46403200
- https://www.openwall.com/lists/oss-security/2025/12/28/5
- http://www.openwall.com/lists/oss-security/2025/12/29/11
- https://lists.debian.org/debian-lts-announce/2026/01/msg00008.html
- https://gpg.fail/memcpy
high severity
- Vulnerable module: libcap2
- Introduced through: libcap2@1:2.66-4
- Fixed in: 1:2.66-4+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › libcap2@1:2.66-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream libcap2 package and not the libcap2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in libcap. A local unprivileged user can exploit a Time-of-check-to-time-of-use (TOCTOU) race condition in the cap_set_file() function. This allows an attacker with write access to a parent directory to redirect file capability updates to an attacker-controlled file. By doing so, capabilities can be injected into or stripped from unintended executables, leading to privilege escalation.
Remediation
Upgrade Debian:12 libcap2 to version 1:2.66-4+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4878
- https://bugzilla.redhat.com/show_bug.cgi?id=2447554
- http://www.openwall.com/lists/oss-security/2026/04/07/14
- http://www.openwall.com/lists/oss-security/2026/04/07/4
- http://www.openwall.com/lists/oss-security/2026/04/08/9
- http://www.openwall.com/lists/oss-security/2026/04/09/5
- http://www.openwall.com/lists/oss-security/2026/04/09/6
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4878.json
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://access.redhat.com/errata/RHSA-2026:12423
- https://access.redhat.com/errata/RHSA-2026:12441
- https://access.redhat.com/errata/RHSA-2026:13285
- https://access.redhat.com/errata/RHSA-2026:14162
- https://access.redhat.com/errata/RHSA-2026:14937
- https://access.redhat.com/errata/RHSA-2026:19130
- https://access.redhat.com/errata/RHSA-2026:19346
- https://access.redhat.com/errata/RHSA-2026:19456
- https://access.redhat.com/errata/RHSA-2026:19458
- https://access.redhat.com/errata/RHSA-2026:20595
- https://access.redhat.com/errata/RHSA-2026:21254
- https://access.redhat.com/errata/RHSA-2026:21275
- https://access.redhat.com/errata/RHSA-2026:22634
- https://access.redhat.com/errata/RHSA-2026:22957
- https://access.redhat.com/errata/RHSA-2026:23233
- https://access.redhat.com/errata/RHSA-2026:23245
- https://access.redhat.com/errata/RHSA-2026:24346
- https://access.redhat.com/errata/RHSA-2026:25044
- https://access.redhat.com/errata/RHSA-2026:25096
- https://access.redhat.com/errata/RHSA-2026:25181
- https://access.redhat.com/errata/RHSA-2026:26542
- https://access.redhat.com/errata/RHSA-2026:27998
- https://access.redhat.com/errata/RHSA-2026:28887
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30078
- https://access.redhat.com/errata/RHSA-2026:30087
- https://access.redhat.com/errata/RHSA-2026:30088
- https://access.redhat.com/errata/RHSA-2026:30089
- https://access.redhat.com/errata/RHSA-2026:34098
- https://access.redhat.com/errata/RHSA-2026:39981
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:7473
- https://access.redhat.com/security/cve/CVE-2026-4878
- https://bugzilla.redhat.com/show_bug.cgi?id=2451615
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
In libexpat before 2.8.2, there is a heap-based buffer overflow in doProlog in xmlparse.c because scaffold backing array reallocation is mishandled when there is data-structure sharing across parsers.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u5 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in getAttributeId.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in addBinding.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in storeAtts.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 relevant fixed versions and status.
A flaw was found in systemd. The systemd-machined service contains an Improper Access Control vulnerability due to insufficient validation of the class parameter in the RegisterMachine D-Bus (Desktop Bus) method. A local unprivileged user can exploit this by attempting to register a machine with a specific class value, which may leave behind a usable, attacker-controlled machine object. This allows the attacker to invoke methods on the privileged object, leading to the execution of arbitrary commands with root privileges on the host system.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in GnuTLS. The gnutls_pkcs11_token_set_pin function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42014
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/security/cve/CVE-2026-42014
- https://bugzilla.redhat.com/show_bug.cgi?id=2467451
- https://gitlab.com/gnutls/gnutls/-/issues/1766
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-9
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A NULL pointer dereference flaw was found in the GnuTLS software in _gnutls_figure_common_ciphersuite().
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6395
- https://access.redhat.com/security/cve/CVE-2025-6395
- https://bugzilla.redhat.com/show_bug.cgi?id=2376755
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:17415
- https://access.redhat.com/errata/RHSA-2025:19088
- https://lists.debian.org/debian-lts-announce/2025/08/msg00005.html
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://gitlab.com/gnutls/gnutls/-/issues/1718
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
medium severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
The GSS-RPC layer in MIT Kerberos 5 (aka krb5) does not enforce size limits on XDR-decoded data, which allows remote authenticated users to cause a denial of service (memory exhaustion or excessive CPU consumption in kadmind) via crafted RPC requests that trigger unbounded memory allocations during XDR decoding.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112319
- https://access.redhat.com/security/cve/CVE-2026-112319
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
- https://bugzilla.redhat.com/show_bug.cgi?id=2478684
medium severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
xdr_krb5_tl_data() in lib/kadm5/kadm_rpc_xdr.c in MIT Kerberos 5 (aka krb5) does not free partially decoded data on failure, which allows remote authenticated users to cause a denial of service (memory leak in kadmind) via crafted RPC requests that trigger a decode failure.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112316
- https://access.redhat.com/security/cve/CVE-2026-112316
- https://bugzilla.redhat.com/show_bug.cgi?id=2479331
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
medium severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
The policy RPC stubs in kadmin/server/server_stubs.c in MIT Kerberos 5 (aka krb5) 1.5.3 and later do not reject a NULL policy name decoded by xdr_nullstring(), which allows remote authenticated users to cause a denial of service (kadmind crash via NULL pointer dereference) by sending a policy request with an empty policy name that reaches authorization checks or logging code.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112318
- https://access.redhat.com/security/cve/CVE-2026-112318
- https://bugzilla.redhat.com/show_bug.cgi?id=2478792
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
medium severity
- Vulnerable module: libtirpc/libtirpc-common
- Introduced through: libtirpc/libtirpc-common@1.3.3+ds-1 and libtirpc/libtirpc3@1.3.3+ds-1
Detailed paths
-
Introduced through: python@3.8-slim › libtirpc/libtirpc-common@1.3.3+ds-1
-
Introduced through: python@3.8-slim › libtirpc/libtirpc3@1.3.3+ds-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtirpc package and not the libtirpc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in libtirpc. An authenticated remote attacker could exploit this vulnerability by sending oversized wrapped data requests to an RPC (Remote Procedure Call) service configured with RPCSEC_GSS (Remote Procedure Call Security-Generic Security Service) integrity or privacy. This can lead to unbounded memory allocation, resulting in a Denial of Service (DoS) by exhausting system resources and causing the service to become unstable or terminate.
Remediation
There is no fixed version for Debian:12 libtirpc.
References
medium severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u1 or higher.
References
medium severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u1 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat to version 2.5.0-1+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-102633
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/R_2_8_5/expat/lib/xmlparse.c#L1003
- https://github.com/libexpat/libexpat/commit/209801d7fbaf07ab74bae8cb32dd2ab9e5846118
- https://github.com/libexpat/libexpat/pull/1392
- https://www.vulncheck.com/advisories/libexpat-2.7.2-through-2.8.5-integer-overflow-in-expat-realloc
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_GetBuffer, XML_Parse, XML_ParseBuffer, XML_ParserFree, or XML_ParserReset from within handlers in cases of a policy violation. Thus, a use-after-free can occur,
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 does not consider XML_TOK_DATA_CHARS in doCdataSection and thus lacks handler call depth tracking for various calls from within handlers in cases of a policy violation. Thus, a use-after-free can occur. NOTE: this issue exists because of an incomplete fix for CVE-2026-50219.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
A vulnerability in the MIT Kerberos implementation allows GSSAPI-protected messages using RC4-HMAC-MD5 to be spoofed due to weaknesses in the MD5 checksum design. If RC4 is preferred over stronger encryption types, an attacker could exploit MD5 collisions to forge message integrity codes. This may lead to unauthorized message tampering.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-3576
- https://access.redhat.com/security/cve/CVE-2025-3576
- https://bugzilla.redhat.com/show_bug.cgi?id=2359465
- https://lists.debian.org/debian-lts-announce/2025/05/msg00047.html
- https://access.redhat.com/errata/RHSA-2025:8411
- https://access.redhat.com/errata/RHSA-2025:9418
- https://access.redhat.com/errata/RHSA-2025:9430
- https://access.redhat.com/errata/RHSA-2025:11487
- https://web.mit.edu/kerberos/krb5-1.22/krb5-1.22.html
- https://access.redhat.com/errata/RHSA-2025:13664
- https://access.redhat.com/errata/RHSA-2025:13777
- https://access.redhat.com/errata/RHSA-2025:15000
- https://access.redhat.com/errata/RHSA-2025:15002
- https://access.redhat.com/errata/RHSA-2025:15004
- https://access.redhat.com/errata/RHSA-2025:15001
- https://access.redhat.com/errata/RHSA-2025:15003
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
medium severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u1 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.7.5 allows an infinite loop while parsing DTD content.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-32777
- https://github.com/libexpat/libexpat/issues/1161
- https://github.com/libexpat/libexpat/pull/1159
- https://github.com/libexpat/libexpat/pull/1162
- https://issues.oss-fuzz.com/issues/486993411
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.7.5 allows a NULL pointer dereference in the function setContext on retry after an earlier ouf-of-memory condition.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
medium severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.7.5 allows a NULL pointer dereference with empty external parameter entity content.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
medium severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/kdc/ndr.c.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u3 or higher.
References
medium severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
- Fixed in: 1.5.2-6+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam0g@1.5.2-6+deb12u1
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:12 relevant fixed versions and status.
linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.
Remediation
Upgrade Debian:12 pam to version 1.5.2-6+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-22365
- https://lists.debian.org/debian-lts-announce/2025/09/msg00021.html
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
- http://www.openwall.com/lists/oss-security/2024/01/18/3
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/commit/031bb5a5d0d950253b68138b498dc93be69a64cb
- https://github.com/linux-pam/linux-pam/releases/tag/v1.6.0
medium severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
- Fixed in: 1:4.13+dfsg1-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@3.8-slim › shadow/passwd@1:4.13+dfsg1-1+b1
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:12 relevant fixed versions and status.
A flaw was found in shadow-utils. When asking for a new password, shadow-utils asks the password twice. If the password fails on the second attempt, shadow-utils fails in cleaning the buffer used to store the first entry. This may allow an attacker with enough access to retrieve the password from the memory.
Remediation
Upgrade Debian:12 shadow to version 1:4.13+dfsg1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4641
- https://access.redhat.com/errata/RHSA-2023:6632
- https://access.redhat.com/errata/RHSA-2023:7112
- https://access.redhat.com/errata/RHSA-2024:0417
- https://access.redhat.com/errata/RHSA-2024:2577
- https://access.redhat.com/security/cve/CVE-2023-4641
- https://bugzilla.redhat.com/show_bug.cgi?id=2215945
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
medium severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH limit by chaining COLLATE postfix operators. Attackers can supply roughly 175,000 chained COLLATE operators in SQL or an untrusted database view to trigger unbounded recursion in sqlite3WalkExprNN() and crash the process.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119376
- https://abraxaslabs.tech/research/sqlite-collate-depth
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/src/expr.c#L175
- https://github.com/sqlite/sqlite/commit/d54522a5b832422ab893a1e9fa7a99ab314ea4e2
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/252c0b7bf5a727d2
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-stack-exhaustion-via-collate-operator-chain
- https://sqlite.org/bugs/info/2026-10-04T04:50:56Z
medium severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 contains a stack exhaustion vulnerability that allows attackers to bypass the SQLITE_LIMIT_EXPR_DEPTH nesting limit because common table expressions are not counted against it. Attackers can supply a WITH clause chaining tens of thousands of CTEs, via plain SQL or a view in an untrusted database file, causing unbounded selectExpander() recursion that crashes the process.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119371
- https://abraxaslabs.tech/research/sqlite-cte-nest
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/src/select.c#L5754
- https://github.com/sqlite/sqlite/commit/e6ff280c839fdfc7418fd5add12e8f32702a17fb
- https://sqlite.org/bugs/info/2026-10-04T04:58:58Z
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/f54730871303e655
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-stack-exhaustion-via-cte-chain-in-selectexpander
medium severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 contains a stack exhaustion vulnerability in countOfViewOptimization() that allows attackers to crash the host process via count(*) over a large multi-row VALUES clause. Attackers supplying SQL or a database file with a crafted view can trigger deeply nested TK_PLUS expressions whose recursive freeing in sqlite3ExprDeleteNN() exhausts the C stack, causing denial of service.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119591
- https://abraxaslabs.tech/research/sqlite-values-union
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/src/select.c#L7199
- https://github.com/sqlite/sqlite/commit/eff50a067c55f972909e7780e506e91382d08de2
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/ab621a3e11ee4acc
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-stack-exhaustion-via-countofviewoptimization-in-values-clause
- https://sqlite.org/bugs/info/2026-10-04T05:34:47Z
medium severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 built with FTS3/FTS4 and SQLITE_ENABLE_FTS3_PARENTHESIS contains a use-after-free vulnerability in fts3BestSnippet() caused by dangling cached position-list pointers. Attackers can run a full-text MATCH query combining OR and NEAR operators with snippet() to read freed heap memory and crash the process.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119372
- https://abraxaslabs.tech/research/sqlite-fts3-snippet
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/ext/fts3/fts3_snippet.c#L561
- https://github.com/sqlite/sqlite/commit/a87bd2471a9c0606e78d3c3678bcd9cecaa0e731
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/e4635c4153
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-use-after-free-in-fts3-fts3bestsnippet-via-snippet
- https://sqlite.org/bugs/info/2026-08-17T09:18:24Z
medium severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 contains a use-after-free vulnerability in the R-Tree extension that allows attackers to make applications use freed heap memory by manipulating the %_node shadow table. Attackers can supply a database declaring %_node WITHOUT ROWID or with a RAISE(IGNORE) trigger so nodeWrite() hashes nodes as 0, crashing the process after node splits.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119378
- https://abraxaslabs.tech/research/sqlite-rtree-rowid0
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/ext/rtree/rtree.c#L905
- https://github.com/sqlite/sqlite/commit/d21bd37c7cfc1b85b17a6703555f0926b6236e04
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/6a9e1415659f9e75
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-use-after-free-in-r-tree-nodewrite
medium severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 contains an information disclosure vulnerability that allows attackers to read uninitialized page-cache memory by supplying a WAL file with an undersized page size. Attackers can craft a database and WAL file whose oversized record payload makes queries like substr() return stale bytes, disclosing other table rows and internal pointers.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119375
- https://abraxaslabs.tech/research/sqlite-wal-pagesize
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/src/wal.c#L3672
- https://github.com/sqlite/sqlite/commit/e5bf119821f25be1d7f10ef0a2edbe175289166e
- https://sqlite.org/bugs/info/2026-08-17T15:54:41Z
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/f9b4ee369557c36c
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-information-disclosure-via-wal-page-size-mismatch
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u6
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in GnuTLS. This vulnerability allows a denial of service (DoS) by excessive CPU (Central Processing Unit) and memory consumption via specially crafted malicious certificates containing a large number of name constraints and subject alternative names (SANs).
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14831
- https://access.redhat.com/security/cve/CVE-2025-14831
- https://bugzilla.redhat.com/show_bug.cgi?id=2423177
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://gitlab.com/gnutls/gnutls/-/issues/1773
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:6630
- https://access.redhat.com/errata/RHSA-2026:6618
- https://access.redhat.com/errata/RHSA-2026:6737
- https://access.redhat.com/errata/RHSA-2026:6738
- https://access.redhat.com/errata/RHSA-2026:7329
- https://access.redhat.com/errata/RHSA-2026:7335
- https://access.redhat.com/errata/RHSA-2026:8747
- https://access.redhat.com/errata/RHSA-2026:8746
- https://access.redhat.com/errata/RHSA-2026:8748
- https://access.redhat.com/errata/RHSA-2026:7477
- https://access.redhat.com/errata/RHSA-2026:13812
- https://access.redhat.com/errata/RHSA-2026:16174
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://access.redhat.com/errata/RHSA-2026:16008
- https://access.redhat.com/errata/RHSA-2026:16009
- https://access.redhat.com/errata/RHSA-2026:25096
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in GnuTLS, which relies on libtasn1 for ASN.1 data processing. Due to an inefficient algorithm in libtasn1, decoding certain DER-encoded certificate data can take excessive time, leading to increased resource consumption. This flaw allows a remote attacker to send a specially crafted certificate, causing GnuTLS to become unresponsive or slow, resulting in a denial-of-service condition.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12243
- https://access.redhat.com/security/cve/CVE-2024-12243
- https://bugzilla.redhat.com/show_bug.cgi?id=2344615
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- https://lists.debian.org/debian-lts-announce/2025/02/msg00027.html
- https://access.redhat.com/errata/RHSA-2025:4051
- https://access.redhat.com/errata/RHSA-2025:7076
- https://access.redhat.com/errata/RHSA-2025:8020
- https://security.netapp.com/advisory/ntap-20250523-0002/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17361
- https://gitlab.com/gnutls/gnutls/-/issues/1553
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A heap-buffer-overread vulnerability was found in GnuTLS in how it handles the Certificate Transparency (CT) Signed Certificate Timestamp (SCT) extension during X.509 certificate parsing. This flaw allows a malicious user to create a certificate containing a malformed SCT extension (OID 1.3.6.1.4.1.11129.2.4.2) that contains sensitive data. This issue leads to the exposure of confidential information when GnuTLS verifies certificates from certain websites when the certificate (SCT) is not checked correctly.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-32989
- https://access.redhat.com/security/cve/CVE-2025-32989
- https://bugzilla.redhat.com/show_bug.cgi?id=2359621
- https://access.redhat.com/errata/RHSA-2025:16115
- https://access.redhat.com/errata/RHSA-2025:16116
- https://access.redhat.com/errata/RHSA-2025:17348
- https://access.redhat.com/errata/RHSA-2025:17361
- https://access.redhat.com/errata/RHSA-2025:19088
- http://www.openwall.com/lists/oss-security/2025/07/11/3
- https://access.redhat.com/errata/RHSA-2025:17181
- https://access.redhat.com/errata/RHSA-2025:22529
- https://lists.gnupg.org/pipermail/gnutls-help/2025-July/004883.html
- https://access.redhat.com/errata/RHSA-2026:7477
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. An off-by-one error exists in the PKCS#12 bag element bounds check. This vulnerability allows an remote attacker to write past the internal array of a PKCS#12 bag when appending to a bag that already contains 32 elements. This memory corruption could lead to a denial of service (DoS) or potentially other unspecified impacts.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42015
- https://access.redhat.com/security/cve/CVE-2026-42015
- https://bugzilla.redhat.com/show_bug.cgi?id=2467678
- https://access.redhat.com/errata/RHSA-2026:20611
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:32962
- https://access.redhat.com/errata/RHSA-2026:33125
- https://access.redhat.com/errata/RHSA-2026:41921
- https://access.redhat.com/errata/RHSA-2026:43575
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-11
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
medium severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
The RPCSEC_GSS authentication routines in lib/rpc/authgss_prot.c in MIT Kerberos 5 (aka krb5) 1.4 and later do not free partially decoded buffers on failure, which allows remote attackers to cause a denial of service (memory leak in kadmind) via crafted RPCSEC_GSS messages.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112315
- https://access.redhat.com/security/cve/CVE-2026-112315
- https://bugzilla.redhat.com/show_bug.cgi?id=2479403
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
medium severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
krb5_ktkdb_get_entry() in lib/kdb/keytab.c in MIT Kerberos 5 (aka krb5) 1.2.8 and later does not free decrypted key material when a post-decryption check fails, which allows remote attackers to cause a denial of service (memory leak in the KDC or kadmind) via requests that repeatedly trigger key decryption failures.
Remediation
There is no fixed version for Debian:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-112317
- https://access.redhat.com/security/cve/CVE-2026-112317
- https://bugzilla.redhat.com/show_bug.cgi?id=2479209
- https://access.redhat.com/errata/RHSA-2026:99624
- https://access.redhat.com/errata/RHSA-2026:99625
- https://access.redhat.com/errata/RHSA-2026:99715
- https://access.redhat.com/errata/RHSA-2026:99716
- https://access.redhat.com/errata/RHSA-2026:97811
medium severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2
- Fixed in: 4.19.0-2+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › libtasn1-6@4.19.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw in libtasn1 causes inefficient handling of specific certificate data. When processing a large number of elements in a certificate, libtasn1 takes much longer than expected, which can slow down or even crash the system. This flaw allows an attacker to send a specially crafted certificate, causing a denial of service attack.
Remediation
Upgrade Debian:12 libtasn1-6 to version 4.19.0-2+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-12133
- https://access.redhat.com/security/cve/CVE-2024-12133
- https://bugzilla.redhat.com/show_bug.cgi?id=2344611
- https://gitlab.com/gnutls/libtasn1/-/issues/52
- http://www.openwall.com/lists/oss-security/2025/02/06/6
- https://lists.debian.org/debian-lts-announce/2025/02/msg00025.html
- https://access.redhat.com/errata/RHSA-2025:4049
- https://access.redhat.com/errata/RHSA-2025:7077
- https://access.redhat.com/errata/RHSA-2025:8021
- https://security.netapp.com/advisory/ntap-20250523-0003/
- https://access.redhat.com/errata/RHSA-2025:8385
- https://access.redhat.com/errata/RHSA-2025:17347
- https://gitlab.com/gnutls/libtasn1/-/blob/master/doc/security/CVE-2024-12133.md
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://access.redhat.com/errata/RHSA-2026:30849
- https://access.redhat.com/errata/RHSA-2026:30850
- https://access.redhat.com/errata/RHSA-2026:33125
medium severity
- Vulnerable module: libtirpc/libtirpc-common
- Introduced through: libtirpc/libtirpc-common@1.3.3+ds-1 and libtirpc/libtirpc3@1.3.3+ds-1
Detailed paths
-
Introduced through: python@3.8-slim › libtirpc/libtirpc-common@1.3.3+ds-1
-
Introduced through: python@3.8-slim › libtirpc/libtirpc3@1.3.3+ds-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtirpc package and not the libtirpc package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in libtirpc. A remote attacker can exploit this vulnerability by sending specially crafted PMAPPROC_DUMP replies to a client application that uses the pmap_getmaps() function against an attacker-controlled host. This unbounded decoding can lead to excessive memory and CPU allocation, causing the client process to experience a Denial of Service (DoS) due to resource exhaustion.
Remediation
There is no fixed version for Debian:12 libtirpc.
References
medium severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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:12 util-linux.
References
medium severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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
There is no fixed version for Debian:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13595
- https://access.redhat.com/errata/RHSA-2026:26573
- https://access.redhat.com/security/cve/CVE-2026-13595
- https://bugzilla.redhat.com/show_bug.cgi?id=2494101
- https://github.com/util-linux/util-linux/commit/c0186f14fbdb02f64c8e0ba701ce727ea764ff4c
- https://access.redhat.com/errata/RHSA-2026:93461
- https://access.redhat.com/errata/RHSA-2026:95365
- https://access.redhat.com/errata/RHSA-2026:96212
- https://access.redhat.com/errata/RHSA-2026:97522
- https://access.redhat.com/errata/RHSA-2026:99119
medium severity
- Vulnerable module: xz-utils/liblzma5
- Introduced through: xz-utils/liblzma5@5.4.1-0.2
- Fixed in: 5.4.1-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › xz-utils/liblzma5@5.4.1-0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
XZ Utils provide a general-purpose data-compression library plus command-line tools. Prior to version 5.8.3, if lzma_index_decoder() was used to decode an Index that contained no Records, the resulting lzma_index was left in a state where where a subsequent lzma_index_append() would allocate too little memory, and a buffer overflow would occur. This issue has been patched in version 5.8.3.
Remediation
Upgrade Debian:12 xz-utils to version 5.4.1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34743
- https://github.com/tukaani-project/xz/commit/c8c22869e780ff57c96b46939c3d79ff99395f87
- https://github.com/tukaani-project/xz/releases/tag/v5.8.3
- https://github.com/tukaani-project/xz/security/advisories/GHSA-x872-m794-cxhv
- http://www.openwall.com/lists/oss-security/2026/03/31/13
- https://lists.debian.org/debian-lts-announce/2026/07/msg00034.html
medium severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat through 2.10.0 contains an out-of-bounds read vulnerability in unknown_toUtf8() and unknown_toUtf16() in xmltok.c when handling application-registered unknown encodings. Attackers can supply a document ending in a truncated multibyte sequence so the convert callback reads past the parse buffer, leaking adjacent memory or crashing applications.
Remediation
There is no fixed version for Debian:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-124317
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/a70841d9ffa64ddde29ab824ed6305035ebe4c47/expat/lib/xmltok.c#L1274-L1322
- https://github.com/libexpat/libexpat/pull/1492
- https://www.vulncheck.com/advisories/libexpat-through-2.10.0-out-of-bounds-read-via-unknown-toutf8-and-unknown-toutf16
medium severity
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
- Fixed in: 12.2.0-14+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
DISPUTEDA failure in the -fstack-protector feature in GCC-based toolchains that target AArch64 allows an attacker to exploit an existing buffer overflow in dynamically-sized local variables in your application without this being detected. This stack-protector failure only applies to C99-style dynamically-sized local variables or those created using alloca(). The stack-protector operates as intended for statically-sized local variables.
The default behavior when the stack-protector detects an overflow is to terminate your application, resulting in controlled loss of availability. An attacker who can exploit a buffer overflow without triggering the stack-protector might be able to change program flow control to cause an uncontrolled loss of availability or to go further and affect confidentiality or integrity. NOTE: The GCC project argues that this is a missed hardening bug and not a vulnerability by itself.
Remediation
Upgrade Debian:12 gcc-12 to version 12.2.0-14+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-4039
- https://developer.arm.com/Arm%20Security%20Center/GCC%20Stack%20Protector%20Vulnerability%20AArch64
- https://github.com/metaredteam/external-disclosures/security/advisories/GHSA-x7ch-h5rf-w2mf
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
medium severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
- Fixed in: 252.38-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 relevant fixed versions and status.
A vulnerability was found in systemd-coredump. This flaw allows an attacker to force a SUID process to crash and replace it with a non-SUID binary to access the original's privileged process coredump, allowing the attacker to read sensitive data, such as /etc/shadow content, loaded by the original process.
A SUID binary or process has a special type of permission, which allows the process to run with the file owner's permissions, regardless of the user executing the binary. This allows the process to access more restricted data than unprivileged users or processes would be able to. An attacker can leverage this flaw by forcing a SUID process to crash and force the Linux kernel to recycle the process PID before systemd-coredump can analyze the /proc/pid/auxv file. If the attacker wins the race condition, they gain access to the original's SUID process coredump file. They can read sensitive content loaded into memory by the original binary, affecting data confidentiality.
Remediation
Upgrade Debian:12 systemd to version 252.38-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4598
- https://access.redhat.com/security/cve/CVE-2025-4598
- https://bugzilla.redhat.com/show_bug.cgi?id=2369242
- https://www.openwall.com/lists/oss-security/2025/05/29/3
- http://www.openwall.com/lists/oss-security/2025/06/05/1
- http://www.openwall.com/lists/oss-security/2025/06/05/3
- https://blogs.oracle.com/linux/post/analysis-of-cve-2025-4598
- https://ciq.com/blog/the-real-danger-of-systemd-coredump-cve-2025-4598/
- https://www.openwall.com/lists/oss-security/2025/08/18/3
- http://seclists.org/fulldisclosure/2025/Jun/9
- https://lists.debian.org/debian-lts-announce/2025/07/msg00022.html
- http://www.openwall.com/lists/oss-security/2025/08/18/3
- https://access.redhat.com/errata/RHSA-2025:22660
- https://access.redhat.com/errata/RHSA-2025:22868
- https://access.redhat.com/errata/RHSA-2025:23234
- https://access.redhat.com/errata/RHSA-2025:23227
- https://access.redhat.com/errata/RHSA-2026:0414
- https://access.redhat.com/errata/RHSA-2026:1652
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://access.redhat.com/errata/RHSA-2026:18153
medium severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
The xmlwf tool in libexpat through 2.10.0 contains a symlink following vulnerability because -d output mode opens files with fopen("wb"), which follows symbolic links. Local attackers with write access to the output directory can plant a symlink at the expected output name to truncate or overwrite files writable by the xmlwf user.
Remediation
There is no fixed version for Debian:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-128241
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/R_2_10_0/expat/xmlwf/xmlwf.c#L1272-L1275
- https://github.com/libexpat/libexpat/blob/R_2_10_0/expat/xmlwf/xmlwf.c#L1338-L1347
- https://github.com/libexpat/libexpat/pull/1502
- https://www.vulncheck.com/advisories/libexpat-xmlwf-through-2.10.0-symlink-following-via-d-output-directory
medium severity
new
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in libstdc++. When a byte-by-byte write operation fails during file stream processing, the library may still append data into the internal memory buffer. An attacker capable of inducing repeated write failures in an affected service can trigger a buffer overflow, potentially resulting in a Denial of Service (DoS) or memory corruption.
Remediation
There is no fixed version for Debian:12 gcc-12.
References
medium severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u6
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in the GnuTLS library, specifically in the gnutls_pkcs11_token_init() function that handles PKCS#11 token initialization. When a token label longer than expected is processed, the function writes past the end of a fixed-size stack buffer. This programming error can cause the application using GnuTLS to crash or, in certain conditions, be exploited for code execution. As a result, systems or applications relying on GnuTLS may be vulnerable to a denial of service or local privilege escalation attacks.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u6 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9820
- https://access.redhat.com/security/cve/CVE-2025-9820
- https://bugzilla.redhat.com/show_bug.cgi?id=2392528
- https://gitlab.com/gnutls/gnutls/-/commit/1d56f96f6ab5034d677136b9d50b5a75dff0faf5
- https://gitlab.com/gnutls/gnutls/-/issues/1732
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2025-11-18
- http://www.openwall.com/lists/oss-security/2025/11/20/2
- https://access.redhat.com/errata/RHSA-2026:3477
- https://access.redhat.com/errata/RHSA-2026:4188
- https://access.redhat.com/errata/RHSA-2026:4655
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:5585
- https://access.redhat.com/errata/RHSA-2026:5606
- https://access.redhat.com/errata/RHSA-2026:7329
- https://access.redhat.com/errata/RHSA-2026:7477
- https://access.redhat.com/errata/RHSA-2026:13812
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › tar@1.34+dfsg-1.2+deb12u1
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:12 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:12 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2005-2541
- http://marc.info/?l=bugtraq&m=112327628230258&w=2
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c@%3Cissues.guacamole.apache.org%3E
- https://lists.apache.org/thread.html/rc713534b10f9daeee2e0990239fa407e2118e4aa9e88a7041177497c%40%3Cissues.guacamole.apache.org%3E
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
An integer overflow in the sqlite3KeyInfoFromExprList function in SQLite versions 3.39.2 through 3.41.1 allows an attacker with the ability to execute arbitrary SQL statements to cause a denial of service or disclose sensitive information from process memory via a crafted SELECT statement with a large number of expressions in the ORDER BY clause.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22851
- http://www.securityfocus.com/bid/109167
- https://ubuntu.com/security/CVE-2019-1010023
- https://support.f5.com/csp/article/K11932200?utm_source=f5support&%3Butm_medium=RSS
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 relevant fixed versions and status.
HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.
Remediation
There is no fixed version for Debian:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2023-31486
- https://security.netapp.com/advisory/ntap-20241129-0011/
- http://www.openwall.com/lists/oss-security/2023/04/29/1
- http://www.openwall.com/lists/oss-security/2023/05/03/3
- http://www.openwall.com/lists/oss-security/2023/05/03/5
- http://www.openwall.com/lists/oss-security/2023/05/07/2
- https://blog.hackeriet.no/perl-http-tiny-insecure-tls-default-affects-cpan-modules/
- https://github.com/chansen/p5-http-tiny/pull/153
- https://hackeriet.github.io/cpan-http-tiny-overview/
- https://www.openwall.com/lists/oss-security/2023/04/18/14
- https://www.openwall.com/lists/oss-security/2023/05/03/4
- https://www.reddit.com/r/perl/comments/111tadi/psa_httptiny_disabled_ssl_verification_by_default/
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: python@3.8-slim › ncurses/libncursesw6@6.4-4
-
Introduced through: python@3.8-slim › ncurses/libtinfo6@6.4-4
-
Introduced through: python@3.8-slim › ncurses/ncurses-base@6.4-4
-
Introduced through: python@3.8-slim › ncurses/ncurses-bin@6.4-4
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:12 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:12 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69720
- https://github.com/Cao-Wuhui/CVE-2025-69720
- https://invisible-island.net/archives/ncurses/6.5/
- https://invisible-island.net/ncurses/
- https://marc.info/?l=ncurses-bug&m=176539968328570&w=2
- https://marc.info/?l=ncurses-bug&m=176540731801330&w=2
- https://marc.info/?l=ncurses-bug&m=176545557728083&w=2
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 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
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-11824
- https://sqlite.org/releaselog/3_53_2.html
- https://sqlite.org/src/info/061febcf41ca
- https://sqlite.org/src/info/4a5ad516ea93
- https://www.vulncheck.com/advisories/sqlite-before-heap-buffer-overflow-via-fts5-fts5chunkiterate
- https://cert-portal.siemens.com/productcert/html/ssa-765416.html
low severity
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 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:12 gcc-12.
References
- https://security-tracker.debian.org/tracker/CVE-2026-95619
- https://access.redhat.com/security/cve/CVE-2026-95619
- https://bugzilla.redhat.com/show_bug.cgi?id=2537811
- https://access.redhat.com/errata/RHSA-2026:58503
- https://access.redhat.com/errata/RHSA-2026:67275
- https://access.redhat.com/errata/RHSA-2026:89830
- https://access.redhat.com/errata/RHSA-2026:98475
- https://access.redhat.com/errata/RHSA-2026:99032
low severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-115506
- https://github.com/hannob/lololol
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/issues/1160
- https://github.com/libexpat/libexpat/pull/1433
- https://www.vulncheck.com/advisories/libexpat-through-2.9.0-denial-of-service-via-billion-laughs-detection-delay
low severity
new
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-113351
- https://github.com/libexpat/libexpat
- https://github.com/libexpat/libexpat/blob/a76b1174c1ea52abb639a4c69d52b630a8a106a2/expat/lib/xmlparse.c#L1560
- https://github.com/libexpat/libexpat/blob/a76b1174c1ea52abb639a4c69d52b630a8a106a2/expat/lib/xmlparse.c#L860-L884
- https://github.com/libexpat/libexpat/pull/1431
- https://www.vulncheck.com/advisories/libexpat-2.7.2-through-2.9.0-denial-of-service-via-xml-parserreset
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=34141
- https://lists.gnu.org/archive/html/bug-gnulib/2019-01/msg00108.html
- https://security.netapp.com/advisory/ntap-20190315-0002/
- http://www.securityfocus.com/bid/107160
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-20796
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=24269
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2019-9192
- https://support.f5.com/csp/article/K26346590?utm_source=f5support&%3Butm_medium=RSS
low severity
- Vulnerable module: gzip
- Introduced through: gzip@1.12-1
Detailed paths
-
Introduced through: python@3.8-slim › gzip@1.12-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:12 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
There is no fixed version for Debian:12 gzip.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41992
- https://cert.pl/en/posts/2026/04/CVE-2026-41991/
- https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=63dbf6b3b9e6e781df1a6a64e609b10e23969681
- https://www.gnu.org/software/gzip/
- http://www.openwall.com/lists/oss-security/2026/08/23/1
- http://www.openwall.com/lists/oss-security/2026/08/25/1
- http://www.openwall.com/lists/oss-security/2026/08/27/2
- https://cgit.git.savannah.gnu.org/cgit/gzip.git/commit/?id=e7378c2d421be6a286922374425680bbe9ad8b7d
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 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:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2018-5709
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-5709
- https://github.com/poojamnit/Kerberos-V5-1.16-Vulnerabilities/tree/master/Integer%20Overflow
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2018-5709
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: python@3.8-slim › libgcrypt20@1.10.1-3
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:12 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:12 libgcrypt20.
References
- https://security-tracker.debian.org/tracker/CVE-2018-6829
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal
- https://github.com/weikengchen/attack-on-libgcrypt-elgamal/wiki
- https://lists.gnupg.org/pipermail/gcrypt-devel/2018-February/004394.html
- https://www.oracle.com/security-alerts/cpujan2020.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl.
References
low severity
- Vulnerable module: acl/libacl1
- Introduced through: acl/libacl1@2.3.1-3
Detailed paths
-
Introduced through: python@3.8-slim › acl/libacl1@2.3.1-3
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:12 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:12 acl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54369
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
- https://www.vulncheck.com/advisories/acl-symlink-traversal-privilege-escalation-via-libacl-functions
- https://access.redhat.com/errata/RHSA-2026:34351
- https://access.redhat.com/errata/RHSA-2026:42736
- https://access.redhat.com/errata/RHSA-2026:42739
- https://access.redhat.com/errata/RHSA-2026:43420
- https://access.redhat.com/security/cve/CVE-2026-54369
- https://bugzilla.redhat.com/show_bug.cgi?id=2490277
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54369.json
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:50205
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54769
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:64805
- https://access.redhat.com/errata/RHSA-2026:67140
- https://access.redhat.com/errata/RHSA-2026:67142
- https://access.redhat.com/errata/RHSA-2026:67144
low severity
- Vulnerable module: attr/libattr1
- Introduced through: attr/libattr1@1:2.5.1-4
Detailed paths
-
Introduced through: python@3.8-slim › attr/libattr1@1:2.5.1-4
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:12 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:12 attr.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54371
- https://cgit.git.savannah.nongnu.org/cgit/attr.git/commit/?id=49f79e947270f06940b9100fa638f85dddc4aa7f
- https://cgit.git.savannah.nongnu.org/cgit/attr.git/commit/?id=c440855d6b33446edf4b5eb1a2d892281f15a99b
- https://www.vulncheck.com/advisories/attr-symlink-traversal-privilege-escalation-via-getfattr-setfattr
- https://access.redhat.com/security/cve/CVE-2026-54371
- https://bugzilla.redhat.com/show_bug.cgi?id=2490283
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-54371.json
- https://access.redhat.com/errata/RHSA-2026:34889
- https://access.redhat.com/errata/RHSA-2026:56133
- https://access.redhat.com/errata/RHSA-2026:59380
- https://access.redhat.com/errata/RHSA-2026:60226
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:63135
- https://access.redhat.com/errata/RHSA-2026:63138
- https://access.redhat.com/errata/RHSA-2026:66018
low severity
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 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:12 gcc-12.
References
- https://security-tracker.debian.org/tracker/CVE-2026-102010
- https://access.redhat.com/security/cve/CVE-2026-102010
- https://bugzilla.redhat.com/show_bug.cgi?id=2478395
- https://access.redhat.com/errata/RHSA-2026:73642
- https://access.redhat.com/errata/RHSA-2026:74569
- https://access.redhat.com/errata/RHSA-2026:89830
- https://access.redhat.com/errata/RHSA-2026:89891
- https://access.redhat.com/errata/RHSA-2026:90915
- https://access.redhat.com/errata/RHSA-2026:95581
- https://access.redhat.com/errata/RHSA-2026:98474
- https://access.redhat.com/errata/RHSA-2026:98475
- https://access.redhat.com/errata/RHSA-2026:98483
- https://access.redhat.com/errata/RHSA-2026:98576
- https://access.redhat.com/errata/RHSA-2026:98577
- https://access.redhat.com/errata/RHSA-2026:98580
- https://access.redhat.com/errata/RHSA-2026:99032
- https://access.redhat.com/errata/RHSA-2026:99041
- https://access.redhat.com/errata/RHSA-2026:99089
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@3.8-slim › coreutils@9.1-1
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:12 relevant fixed versions and status.
chroot in GNU coreutils, when used with --userspec, allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer.
Remediation
There is no fixed version for Debian:12 coreutils.
References
- https://security-tracker.debian.org/tracker/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772@%3Cdev.mina.apache.org%3E
- http://www.openwall.com/lists/oss-security/2016/02/28/2
- http://www.openwall.com/lists/oss-security/2016/02/28/3
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2016-2781
- https://lists.apache.org/thread.html/rf9fa47ab66495c78bb4120b0754dd9531ca2ff0430f6685ac9b07772%40%3Cdev.mina.apache.org%3E
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 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:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-107778
- https://github.com/krb5/krb5
- https://github.com/krb5/krb5/blob/krb5-1.22.2-final/src/lib/krb5/krb/rd_cred.c#L77-L112
- https://github.com/krb5/krb5/commit/48afa9abb89ab2176bb20624d87d010b9984fc08
- https://github.com/krb5/krb5/commit/62196e2b269159a5465f5b8d0ed7cf6f29c3282a
- https://github.com/krb5/krb5/pull/1511
- https://www.vulncheck.com/advisories/mit-krb5-through-1.22.2-null-pointer-dereference-via-krb5-rd-cred
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: python@3.8-slim › ncurses/libncursesw6@6.4-4
-
Introduced through: python@3.8-slim › ncurses/libtinfo6@6.4-4
-
Introduced through: python@3.8-slim › ncurses/ncurses-base@6.4-4
-
Introduced through: python@3.8-slim › ncurses/ncurses-bin@6.4-4
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:12 relevant fixed versions and status.
NCurse v6.4-20230418 was discovered to contain a segmentation fault via the component _nc_wrap_entry().
Remediation
There is no fixed version for Debian:12 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2023-50495
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/LU4MYMKFEZQ5VSCVLRIZGDQOUW3T44GT/
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00020.html
- https://lists.gnu.org/archive/html/bug-ncurses/2023-04/msg00029.html
- https://security.netapp.com/advisory/ntap-20240119-0008/
- https://cert-portal.siemens.com/productcert/html/ssa-794697.html
low severity
- Vulnerable module: acl/libacl1
- Introduced through: acl/libacl1@2.3.1-3
Detailed paths
-
Introduced through: python@3.8-slim › acl/libacl1@2.3.1-3
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:12 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:12 acl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54370
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=24a227d0ab8576612194f8a56c2314389adc74a5
- https://cgit.git.savannah.nongnu.org/cgit/acl.git/commit/?id=3589787cd589b34bdd9265936e17190b6d3f17d1
- https://www.vulncheck.com/advisories/acl-toctou-symlink-traversal-via-getfacl-setfacl-chacl
low severity
new
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in GCC. An out-of-bounds memory access vulnerability exists in the libstdc++ parallel search implementation due to an undersized internal buffer. A local attacker can exploit this flaw by providing crafted search data to an application compiled with parallel mode, causing the process to crash and leading to a Denial of Service (DoS).
Remediation
There is no fixed version for Debian:12 gcc-12.
References
- https://security-tracker.debian.org/tracker/CVE-2026-114690
- https://access.redhat.com/security/cve/CVE-2026-114690
- https://bugzilla.redhat.com/show_bug.cgi?id=2478652
- https://access.redhat.com/errata/RHSA-2026:98115
- https://access.redhat.com/errata/RHSA-2026:98648
- https://access.redhat.com/errata/RHSA-2026:98524
- https://access.redhat.com/errata/RHSA-2026:98534
- https://access.redhat.com/errata/RHSA-2026:98633
- https://access.redhat.com/errata/RHSA-2026:98640
- https://access.redhat.com/errata/RHSA-2026:98526
- https://access.redhat.com/errata/RHSA-2026:99632
- https://access.redhat.com/errata/RHSA-2026:95581
- https://access.redhat.com/errata/RHSA-2026:95981
low severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.24.1-2
Detailed paths
-
Introduced through: python@3.8-slim › p11-kit/libp11-kit0@0.24.1-2
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:12 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:12 p11-kit.
References
low severity
- Vulnerable module: p11-kit/libp11-kit0
- Introduced through: p11-kit/libp11-kit0@0.24.1-2
Detailed paths
-
Introduced through: python@3.8-slim › p11-kit/libp11-kit0@0.24.1-2
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:12 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:12 p11-kit.
References
- https://security-tracker.debian.org/tracker/CVE-2026-13757
- https://access.redhat.com/errata/RHSA-2026:37469
- https://access.redhat.com/errata/RHSA-2026:38342
- https://access.redhat.com/errata/RHSA-2026:49668
- https://access.redhat.com/security/cve/CVE-2026-13757
- https://bugzilla.redhat.com/show_bug.cgi?id=2494556
- https://github.com/advisories/GHSA-p2wm-69qx-x25w
- https://access.redhat.com/errata/RHSA-2026:49667
- https://access.redhat.com/errata/RHSA-2026:53371
- https://access.redhat.com/errata/RHSA-2026:54387
- https://access.redhat.com/errata/RHSA-2026:54760
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72394
- https://access.redhat.com/errata/RHSA-2026:72395
- https://access.redhat.com/errata/RHSA-2026:72399
- https://access.redhat.com/errata/RHSA-2026:72470
- https://access.redhat.com/errata/RHSA-2026:72475
- https://access.redhat.com/errata/RHSA-2026:72476
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:81201
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82336
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: python@3.8-slim › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@3.8-slim › shadow/passwd@1:4.13+dfsg1-1+b1
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:12 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:12 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2007-5686
- http://www.securityfocus.com/archive/1/482129/100/100/threaded
- http://www.securityfocus.com/archive/1/482857/100/0/threaded
- https://issues.rpath.com/browse/RPL-1825
- http://secunia.com/advisories/27215
- http://www.securityfocus.com/bid/26048
- http://www.vupen.com/english/advisories/2007/3474
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@3.8-slim › coreutils@9.1-1
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:12 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:12 coreutils.
References
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@3.8-slim › coreutils@9.1-1
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:12 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:12 coreutils.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 relevant fixed versions and status.
A flaw was found in util-linux. This vulnerability allows a heap buffer overread when processing 256-byte usernames, specifically within the setpwnam() function, affecting SUID (Set User ID) login-utils utilities writing to the password database.
Remediation
There is no fixed version for Debian:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2025-14104
- https://access.redhat.com/security/cve/CVE-2025-14104
- https://bugzilla.redhat.com/show_bug.cgi?id=2419369
- https://access.redhat.com/errata/RHSA-2026:1696
- https://access.redhat.com/errata/RHSA-2026:1852
- https://access.redhat.com/errata/RHSA-2026:1913
- https://access.redhat.com/errata/RHSA-2026:2485
- https://access.redhat.com/errata/RHSA-2026:2563
- https://access.redhat.com/errata/RHSA-2026:2737
- https://access.redhat.com/errata/RHSA-2026:2800
- https://access.redhat.com/errata/RHSA-2026:3406
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:7180
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
low severity
new
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in the libstdc++ component of GCC. An attacker who can provide an excessively large element count to a boolean vector (std::vector<bool>) constructor can trigger an integer wrap during internal memory calculations. This issue leaves the container in an inconsistent state, leading to out-of-bounds memory access and resulting in an application crash or a Denial of Service (DoS) during subsequent operations.
Remediation
There is no fixed version for Debian:12 gcc-12.
References
- https://security-tracker.debian.org/tracker/CVE-2026-114691
- https://access.redhat.com/security/cve/CVE-2026-114691
- https://bugzilla.redhat.com/show_bug.cgi?id=2478508
- https://access.redhat.com/errata/RHSA-2026:98115
- https://access.redhat.com/errata/RHSA-2026:98648
- https://access.redhat.com/errata/RHSA-2026:98524
- https://access.redhat.com/errata/RHSA-2026:98534
- https://access.redhat.com/errata/RHSA-2026:98633
- https://access.redhat.com/errata/RHSA-2026:98640
- https://access.redhat.com/errata/RHSA-2026:98526
- https://access.redhat.com/errata/RHSA-2026:99632
- https://access.redhat.com/errata/RHSA-2026:95581
- https://access.redhat.com/errata/RHSA-2026:95981
low severity
- Vulnerable module: dash
- Introduced through: dash@0.5.12-2
Detailed paths
-
Introduced through: python@3.8-slim › dash@0.5.12-2
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:12 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:12 dash.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat through 2.5.0 allows recursive XML Entity Expansion if XML_DTD is undefined at compile time.
Remediation
There is no fixed version for Debian:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2023-52426
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://cwe.mitre.org/data/definitions/776.html
- https://github.com/libexpat/libexpat/commit/0f075ec8ecb5e43f8fdca5182f8cca4703da0404
- https://github.com/libexpat/libexpat/pull/777
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/PNRIHC7DVVRAIWFRGV23Y6UZXFBXSQDB/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WNUBSGZFEZOBHJFTAD42SAN4ATW2VEMV/
- https://security.netapp.com/advisory/ntap-20240307-0005/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-784301.html
low severity
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.
Remediation
There is no fixed version for Debian:12 gcc-12.
References
- https://security-tracker.debian.org/tracker/CVE-2022-27943
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
- https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/H424YXGW7OKXS2NCAP35OP6Y4P4AW6VG/
- https://sourceware.org/bugzilla/show_bug.cgi?id=28995
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
In SQLite 3.49.0 before 3.49.1, certain argument values to sqlite3_db_config (in the C-language API) can cause a denial of service (application crash). An sz*nBig multiplication is not cast to a 64-bit integer, and consequently some memory allocations may be incorrect.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2025-29088
- https://gist.github.com/ylwango613/d3883fb9f6ba8a78086356779ce88248
- https://github.com/sqlite/sqlite/commit/56d2fd008b108109f489339f5fd55212bb50afd4
- https://sqlite.org/forum/forumpost/48f365daec
- https://sqlite.org/releaselog/3_49_1.html
- https://www.sqlite.org/cves.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-994087.html
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.53.2 contains an out-of-bounds read vulnerability in the FTS5 full-text search extension that allows attackers to crash the process by supplying a crafted database with a malformed FTS5 leaf page. Attackers can set an oversized term length in the leaf page so that fts5LeafSeek() reads past the end of the page buffer while comparing terms during an FTS5 MATCH query, in applications compiled with SQLITE_ENABLE_FTS5.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-11822
- https://sqlite.org/releaselog/3_53_2.html
- https://sqlite.org/src/info/061febcf41ca
- https://sqlite.org/src/info/4a5ad516ea93
- https://www.vulncheck.com/advisories/sqlite-before-memory-corruption-in-fts5-extension
- https://cert-portal.siemens.com/productcert/html/ssa-765416.html
- https://sqlite.org/src/info/87b653731171
- https://sqlite.org/src/info/fad98805b7d7
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › tar@1.34+dfsg-1.2+deb12u1
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:12 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:12 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5704
- https://access.redhat.com/security/cve/CVE-2026-5704
- https://bugzilla.redhat.com/show_bug.cgi?id=2455360
- http://www.openwall.com/lists/oss-security/2026/04/11/10
- http://www.openwall.com/lists/oss-security/2026/04/11/11
- http://www.openwall.com/lists/oss-security/2026/04/12/2
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:66514
- https://access.redhat.com/errata/RHSA-2026:70390
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2022-0563
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w@ws.net.home/T/#u
- https://lore.kernel.org/util-linux/20220214110609.msiwlm457ngoic6w%40ws.net.home/T/#u
- https://security.gentoo.org/glsa/202401-08
- https://security.netapp.com/advisory/ntap-20220331-0002/
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: zlib/zlib1g
- Introduced through: zlib/zlib1g@1:1.2.13.dfsg-1
Detailed paths
-
Introduced through: python@3.8-slim › zlib/zlib1g@1:1.2.13.dfsg-1
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:12 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:12 zlib.
References
- https://security-tracker.debian.org/tracker/CVE-2026-27171
- https://7asecurity.com/blog/2026/02/zlib-7asecurity-audit/
- https://github.com/madler/zlib/releases/tag/v1.3.2
- https://ostif.org/zlib-audit-complete/
- https://github.com/madler/zlib/issues/904
- https://7asecurity.com/reports/pentest-report-zlib-RC1.1.pdf
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22852
- http://www.securityfocus.com/bid/109162
- https://ubuntu.com/security/CVE-2019-1010024
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&utm_medium=RSS
- https://sourceware.org/bugzilla/show_bug.cgi?id=22853
- https://ubuntu.com/security/CVE-2019-1010025
- https://support.f5.com/csp/article/K06046097?utm_source=f5support&%3Butm_medium=RSS
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 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:12 krb5.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 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:12 krb5.
References
- https://security-tracker.debian.org/tracker/CVE-2026-107708
- https://github.com/krb5/krb5
- https://github.com/krb5/krb5/blob/krb5-1.22.2-final/src/kdc/kdc_util.c#L639-L676
- https://github.com/krb5/krb5/commit/a88a18cafa1040a0c4f9c8d08288fc98831ec86d
- https://github.com/krb5/krb5/commit/f6e2c397ceda6467ebbaab8ed66d4895c9f1d6a7
- https://github.com/krb5/krb5/pull/1510
- https://www.vulncheck.com/advisories/mit-krb5-through-1.22.2-kdc-null-pointer-dereference-via-s4u2proxy-pac
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@3.8-slim › coreutils@9.1-1
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:12 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:12 coreutils.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.40-1.1
Detailed paths
-
Introduced through: python@3.8-slim › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GnuPG before 2.5.5, if a user chooses to import a certificate with certain crafted subkey data that lacks a valid backsig or that has incorrect usage flags, the user loses the ability to verify signatures made from certain other signing keys, aka a "verification DoS."
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.40-1.1
Detailed paths
-
Introduced through: python@3.8-slim › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
In GnuPG through 2.4.8, if a signed message has \f at the end of a plaintext line, an adversary can construct a modified message that places additional text after the signed material, such that signature verification of the modified message succeeds (although an "invalid armor" message is printed during verification). This is related to use of \f as a marker to denote truncation of a long plaintext line.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- Vulnerable module: gzip
- Introduced through: gzip@1.12-1
Detailed paths
-
Introduced through: python@3.8-slim › gzip@1.12-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:12 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
There is no fixed version for Debian:12 gzip.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam0g@1.5.2-6+deb12u1
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:12 relevant fixed versions and status.
A vulnerability was found in PAM. The secret information is stored in memory, where the attacker can trigger the victim program to execute by sending characters to its standard input (stdin). As this occurs, the attacker can train the branch predictor to execute an ROP chain speculatively. This flaw could result in leaked passwords, such as those found in /etc/shadow while performing authentications.
Remediation
There is no fixed version for Debian:12 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2024-10041
- https://access.redhat.com/security/cve/CVE-2024-10041
- https://bugzilla.redhat.com/show_bug.cgi?id=2319212
- https://access.redhat.com/errata/RHSA-2024:9941
- https://access.redhat.com/errata/RHSA-2024:10379
- https://access.redhat.com/errata/RHSA-2024:11250
low severity
- Vulnerable module: coreutils
- Introduced through: coreutils@9.1-1
Detailed paths
-
Introduced through: python@3.8-slim › coreutils@9.1-1
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:12 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:12 coreutils.
References
- https://security-tracker.debian.org/tracker/CVE-2025-5278
- https://access.redhat.com/security/cve/CVE-2025-5278
- https://bugzilla.redhat.com/show_bug.cgi?id=2368764
- http://www.openwall.com/lists/oss-security/2025/05/27/2
- http://www.openwall.com/lists/oss-security/2025/05/29/1
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/tree/NEWS?id=8c9602e3a145e9596dc1a63c6ed67865814b6633#n14
- http://www.openwall.com/lists/oss-security/2025/05/29/2
- https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78507
- https://access.redhat.com/errata/RHSA-2026:28911
- https://access.redhat.com/errata/RHSA-2026:33124
- https://access.redhat.com/errata/RHSA-2026:33313
- https://access.redhat.com/errata/RHSA-2026:33612
- https://access.redhat.com/errata/RHSA-2026:34102
- https://access.redhat.com/errata/RHSA-2026:39981
- https://access.redhat.com/errata/RHSA-2026:44481
- https://access.redhat.com/errata/RHSA-2026:46836
- https://access.redhat.com/errata/RHSA-2026:50205
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:69964
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
- https://cgit.git.savannah.gnu.org/cgit/coreutils.git/commit/?id=8c9602e3a145e9596dc1a63c6ed67865814b6633
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › tar@1.34+dfsg-1.2+deb12u1
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:12 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:12 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18508
- https://access.redhat.com/errata/RHSA-2026:50807
- https://access.redhat.com/security/cve/CVE-2026-18508
- https://bugzilla.redhat.com/show_bug.cgi?id=2509843
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:70390
low severity
- Vulnerable module: tar
- Introduced through: tar@1.34+dfsg-1.2+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › tar@1.34+dfsg-1.2+deb12u1
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:12 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:12 tar.
References
- https://security-tracker.debian.org/tracker/CVE-2026-18477
- https://access.redhat.com/errata/RHSA-2026:49361
- https://access.redhat.com/security/cve/CVE-2026-18477
- https://bugzilla.redhat.com/show_bug.cgi?id=2509735
- https://access.redhat.com/errata/RHSA-2026:61581
- https://access.redhat.com/errata/RHSA-2026:61783
- https://access.redhat.com/errata/RHSA-2026:61586
- https://access.redhat.com/errata/RHSA-2026:66018
- https://access.redhat.com/errata/RHSA-2026:70390
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2010-4756
- http://cxib.net/stuff/glob-0day.c
- http://securityreason.com/achievement_securityalert/89
- http://securityreason.com/exploitalert/9223
- https://bugzilla.redhat.com/show_bug.cgi?id=681681
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2010-4756
- https://security.netapp.com/advisory/ntap-20241108-0002/
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 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:12 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2011-3389
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00001.html
- http://lists.apple.com/archives/Security-announce/2011//Oct/msg00002.html
- http://support.apple.com/kb/HT4999
- http://support.apple.com/kb/HT5001
- http://support.apple.com/kb/HT5130
- http://support.apple.com/kb/HT5281
- http://support.apple.com/kb/HT5501
- http://support.apple.com/kb/HT6150
- http://lists.apple.com/archives/security-announce/2012/Feb/msg00000.html
- http://lists.apple.com/archives/security-announce/2012/Jul/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/May/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Sep/msg00004.html
- http://lists.apple.com/archives/security-announce/2013/Oct/msg00004.html
- http://www.us-cert.gov/cas/techalerts/TA12-010A.html
- http://www.kb.cert.org/vuls/id/864643
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://blog.mozilla.com/security/2011/09/27/attack-against-tls-protected-communications/
- http://blogs.technet.com/b/msrc/archive/2011/09/26/microsoft-releases-security-advisory-2588513.aspx
- http://blogs.technet.com/b/srd/archive/2011/09/26/is-ssl-broken-more-about-security-advisory-2588513.aspx
- http://curl.haxx.se/docs/adv_20120124B.html
- http://downloads.asterisk.org/pub/security/AST-2016-001.html
- http://my.opera.com/securitygroup/blog/2011/09/28/the-beast-ssl-tls-issue
- https://blogs.oracle.com/sunsecurity/entry/multiple_vulnerabilities_in_fetchmail
- https://bugzilla.novell.com/show_bug.cgi?id=719047
- https://cert-portal.siemens.com/productcert/pdf/ssa-556833.pdf
- http://technet.microsoft.com/security/advisory/2588513
- http://www.apcmedia.com/salestools/SJHN-7RKGNM/SJHN-7RKGNM_R4_EN.pdf
- http://www.ibm.com/developerworks/java/jdk/alerts/
- http://www.imperialviolet.org/2011/09/23/chromeandbeast.html
- http://www.opera.com/docs/changelogs/mac/1151/
- http://www.opera.com/docs/changelogs/mac/1160/
- http://www.opera.com/docs/changelogs/unix/1151/
- http://www.opera.com/docs/changelogs/unix/1160/
- http://www.opera.com/docs/changelogs/windows/1151/
- http://www.opera.com/docs/changelogs/windows/1160/
- http://www.opera.com/support/kb/view/1004/
- http://www.debian.org/security/2012/dsa-2398
- http://security.gentoo.org/glsa/glsa-201203-02.xml
- http://security.gentoo.org/glsa/glsa-201406-32.xml
- https://h20564.www2.hp.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c03839862
- http://marc.info/?l=bugtraq&m=132750579901589&w=2
- http://marc.info/?l=bugtraq&m=132872385320240&w=2
- http://marc.info/?l=bugtraq&m=133365109612558&w=2
- http://marc.info/?l=bugtraq&m=133728004526190&w=2
- http://marc.info/?l=bugtraq&m=134254866602253&w=2
- http://marc.info/?l=bugtraq&m=134254957702612&w=2
- http://ekoparty.org/2011/juliano-rizzo.php
- http://eprint.iacr.org/2004/111
- http://eprint.iacr.org/2006/136
- http://isc.sans.edu/diary/SSL+TLS+part+3+/11635
- https://ics-cert.us-cert.gov/advisories/ICSMA-18-058-02
- http://vnhacker.blogspot.com/2011/09/beast.html
- http://www.educatedguesswork.org/2011/09/security_impact_of_the_rizzodu.html
- http://www.insecure.cl/Beast-SSL.rar
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2012/ms12-006
- http://technet.microsoft.com/security/bulletin/MS12-006
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00049.html
- http://lists.opensuse.org/opensuse-security-announce/2012-01/msg00051.html
- http://lists.opensuse.org/opensuse-security-announce/2012-05/msg00009.html
- http://www.oracle.com/technetwork/topics/security/cpujan2015-1972971.html
- http://www.oracle.com/technetwork/topics/security/cpujul2015-2367936.html
- http://www.oracle.com/technetwork/topics/security/javacpuoct2011-443431.html
- http://osvdb.org/74829
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14752
- https://bugzilla.redhat.com/show_bug.cgi?id=737506
- http://rhn.redhat.com/errata/RHSA-2012-0508.html
- http://rhn.redhat.com/errata/RHSA-2013-1455.html
- http://secunia.com/advisories/45791
- http://secunia.com/advisories/47998
- http://secunia.com/advisories/48256
- http://secunia.com/advisories/48692
- http://secunia.com/advisories/48915
- http://secunia.com/advisories/48948
- http://secunia.com/advisories/49198
- http://secunia.com/advisories/55322
- http://secunia.com/advisories/55350
- http://secunia.com/advisories/55351
- http://www.securityfocus.com/bid/49388
- http://www.securityfocus.com/bid/49778
- http://www.securitytracker.com/id?1025997
- http://www.securitytracker.com/id?1026103
- http://www.securitytracker.com/id?1026704
- http://www.securitytracker.com/id/1029190
- http://lists.opensuse.org/opensuse-security-announce/2020-01/msg00040.html
- https://hermes.opensuse.org/messages/13154861
- https://hermes.opensuse.org/messages/13155432
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2011-3389
- http://www.ubuntu.com/usn/USN-1263-1
- http://www.mandriva.com/security/advisories?name=MDVSA-2012:058
- http://www.redhat.com/support/errata/RHSA-2011-1384.html
- http://www.redhat.com/support/errata/RHSA-2012-0006.html
- https://github.com/mpgn/BEAST-PoC
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 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:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2021-45346
- https://github.com/guyinatuxedo/sqlite3_record_leaking
- https://security.netapp.com/advisory/ntap-20220303-0001/
- https://sqlite.org/forum/forumpost/056d557c2f8c452ed5
- https://sqlite.org/forum/forumpost/53de8864ba114bf6
- https://www.sqlite.org/cves.html#status_of_recent_sqlite_cves
low severity
- Vulnerable module: dash
- Introduced through: dash@0.5.12-2
Detailed paths
-
Introduced through: python@3.8-slim › dash@0.5.12-2
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:12 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:12 dash.
References
low severity
- Vulnerable module: apt
- Introduced through: apt@2.6.1 and apt/libapt-pkg6.0@2.6.1
Detailed paths
-
Introduced through: python@3.8-slim › apt@2.6.1
-
Introduced through: python@3.8-slim › apt/libapt-pkg6.0@2.6.1
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:12 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:12 apt.
References
- https://security-tracker.debian.org/tracker/CVE-2011-3374
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642480
- https://people.canonical.com/~ubuntu-security/cve/2011/CVE-2011-3374.html
- https://seclists.org/fulldisclosure/2011/Sep/221
- https://snyk.io/vuln/SNYK-LINUX-APT-116518
- https://ubuntu.com/security/CVE-2011-3374
- https://access.redhat.com/security/cve/cve-2011-3374
low severity
new
- Vulnerable module: gcc-12/gcc-12-base
- Introduced through: gcc-12/gcc-12-base@12.2.0-14, gcc-12/libgcc-s1@12.2.0-14 and others
Detailed paths
-
Introduced through: python@3.8-slim › gcc-12/gcc-12-base@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libgcc-s1@12.2.0-14
-
Introduced through: python@3.8-slim › gcc-12/libstdc++6@12.2.0-14
NVD Description
Note: Versions mentioned in the description apply only to the upstream gcc-12 package and not the gcc-12 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A flaw was found in gcc. An attacker could cause a Denial of Service (DoS) by passing a string that is not null-terminated to the std::from_chars() function in the libstdc++ library. This issue triggers an out-of-bounds read beyond the allocated buffer, potentially leading to invalid data parsing or an application crash.
Remediation
There is no fixed version for Debian:12 gcc-12.
References
- https://security-tracker.debian.org/tracker/CVE-2026-115456
- https://access.redhat.com/security/cve/CVE-2026-115456
- https://bugzilla.redhat.com/show_bug.cgi?id=2563044
- https://access.redhat.com/errata/RHSA-2026:98648
- https://access.redhat.com/errata/RHSA-2026:98524
- https://access.redhat.com/errata/RHSA-2026:98534
- https://access.redhat.com/errata/RHSA-2026:98633
- https://access.redhat.com/errata/RHSA-2026:98640
- https://access.redhat.com/errata/RHSA-2026:98526
- https://access.redhat.com/errata/RHSA-2026:99632
- https://access.redhat.com/errata/RHSA-2026:95581
- https://access.redhat.com/errata/RHSA-2026:95981
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
- Fixed in: 3.7.9-2+deb12u7
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A flaw was found in gnutls. The PKCS#7 padding check, performed during decryption, was not constant-time. This timing side-channel could allow a remote attacker to potentially leak sensitive information about the padding bytes through observable timing differences. This vulnerability is a form of information disclosure.
Remediation
Upgrade Debian:12 gnutls28 to version 3.7.9-2+deb12u7 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-5419
- https://access.redhat.com/errata/RHSA-2026:20613
- https://access.redhat.com/security/cve/CVE-2026-5419
- https://bugzilla.redhat.com/show_bug.cgi?id=2467686
- https://access.redhat.com/errata/RHSA-2026:20612
- https://access.redhat.com/errata/RHSA-2026:13274
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:26409
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:30004
- https://access.redhat.com/errata/RHSA-2026:32962
- https://www.gnutls.org/security-new.html#GNUTLS-SA-2026-04-29-13
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:72502
- https://access.redhat.com/errata/RHSA-2026:74674
- https://access.redhat.com/errata/RHSA-2026:82304
- https://access.redhat.com/errata/RHSA-2026:82322
- https://access.redhat.com/errata/RHSA-2026:82347
- https://access.redhat.com/errata/RHSA-2026:82354
- https://access.redhat.com/errata/RHSA-2026:82372
- https://access.redhat.com/errata/RHSA-2026:82857
- https://access.redhat.com/errata/RHSA-2026:82888
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.40-1.1
Detailed paths
-
Introduced through: python@3.8-slim › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
- https://security-tracker.debian.org/tracker/CVE-2022-3219
- https://access.redhat.com/security/cve/CVE-2022-3219
- https://bugzilla.redhat.com/show_bug.cgi?id=2127010
- https://dev.gnupg.org/D556
- https://dev.gnupg.org/T5993
- https://marc.info/?l=oss-security&m=165696590211434&w=4
- https://security.netapp.com/advisory/ntap-20230324-0001/
low severity
- Vulnerable module: ncurses/libncursesw6
- Introduced through: ncurses/libncursesw6@6.4-4, ncurses/libtinfo6@6.4-4 and others
Detailed paths
-
Introduced through: python@3.8-slim › ncurses/libncursesw6@6.4-4
-
Introduced through: python@3.8-slim › ncurses/libtinfo6@6.4-4
-
Introduced through: python@3.8-slim › ncurses/ncurses-base@6.4-4
-
Introduced through: python@3.8-slim › ncurses/ncurses-bin@6.4-4
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:12 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:12 ncurses.
References
- https://security-tracker.debian.org/tracker/CVE-2025-6141
- https://invisible-island.net/ncurses/NEWS.html#index-t20250329
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00107.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00109.html
- https://lists.gnu.org/archive/html/bug-ncurses/2025-03/msg00114.html
- https://vuldb.com/?ctiid.312610
- https://vuldb.com/?id.312610
- https://vuldb.com/?submit.593000
- https://www.gnu.org/
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2011-4116
- https://github.com/Perl-Toolchain-Gang/File-Temp/issues/14
- https://rt.cpan.org/Public/Bug/Display.html?id=69106
- https://seclists.org/oss-sec/2011/q4/238
- http://www.openwall.com/lists/oss-security/2011/11/04/2
- http://www.openwall.com/lists/oss-security/2011/11/04/4
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
- Fixed in: 1:4.13+dfsg1-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@3.8-slim › shadow/passwd@1:4.13+dfsg1-1+b1
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:12 relevant fixed versions and status.
In Shadow 4.13, it is possible to inject control characters into fields provided to the SUID program chfn (change finger). Although it is not possible to exploit this directly (e.g., adding a new user fails because \n is in the block list), it is possible to misrepresent the /etc/passwd file when viewed. Use of \r manipulations and Unicode characters to work around blocking of the : character make it possible to give the impression that a new user has been added. In other words, an adversary may be able to convince a system administrator to take the system offline (an indirect, social-engineered denial of service) by demonstrating that "cat /etc/passwd" shows a rogue user account.
Remediation
Upgrade Debian:12 shadow to version 1:4.13+dfsg1-1+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2023-29383
- https://lists.debian.org/debian-lts-announce/2025/04/msg00026.html
- https://github.com/shadow-maint/shadow/commit/e5905c4b84d4fb90aefcd96ee618411ebfac663d
- https://github.com/shadow-maint/shadow/pull/687
- https://www.trustwave.com/en-us/resources/blogs/spiderlabs-blog/cve-2023-29383-abusing-linux-chfn-to-misrepresent-etc-passwd/
- https://www.trustwave.com/en-us/resources/security-resources/security-advisories/?fid=31797
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
new
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
SQLite before 3.54.0 contains an authorization bypass vulnerability in lookupName() that invokes the authorizer only for the first joined table's USING column. Attackers able to submit SQL can query a shared USING column in a RIGHT or FULL JOIN to read columns denied via sqlite3_set_authorizer() SQLITE_READ restrictions.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
- https://security-tracker.debian.org/tracker/CVE-2026-119377
- https://abraxaslabs.tech/research/sqlite-fj-using-auth
- https://github.com/sqlite/sqlite
- https://github.com/sqlite/sqlite/blob/version-3.53.4/src/resolve.c#L775
- https://github.com/sqlite/sqlite/commit/5694c3bb2a6a40770ecd2f65910eea756734dfd8
- https://github.com/sqlite/sqlite/commit/7ff247c5b9ead3ad8a69c26d3fd264878e127237
- https://sqlite.org/bugs/info/2026-07-05T08:15:45Z
- https://sqlite.org/releaselog/3_54_0.html
- https://sqlite.org/src/info/2cb22877683680c1
- https://sqlite.org/src/info/bbd69ce274620008
- https://www.vulncheck.com/advisories/sqlite-before-3.54.0-authorizer-bypass-via-right-or-full-join-using
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
In libexpat before 2.7.4, XML_ExternalEntityParserCreate does not copy unknown encoding handler user data.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u4 or higher.
References
low severity
new
- Vulnerable module: apt
- Introduced through: apt@2.6.1 and apt/libapt-pkg6.0@2.6.1
- Fixed in: 2.6.2
Detailed paths
-
Introduced through: python@3.8-slim › apt@2.6.1
-
Introduced through: python@3.8-slim › apt/libapt-pkg6.0@2.6.1
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:12 relevant fixed versions and status.
On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic (including a malicious mirror or proxy) between an APT client and an archive server triggered by a package install can trick the client into installing an attacker-controlled unverified package and achieve remote code execution with root privileges.
The vulnerability is caused by the reuse of hard links and requires the client to follow redirects and retry the download of package files. It requires the client to have a non-zero Acquire::Retries configuration setting; the value 3 is the default starting with Debian 12 (bookworm) and Ubuntu 22.04 LTS (Jammy Jellyfish), so older releases are unaffected in a default configuration
Remediation
Upgrade Debian:12 apt to version 2.6.2 or higher.
References
low severity
- Vulnerable module: bzip2/libbz2-1.0
- Introduced through: bzip2/libbz2-1.0@1.0.8-5+b1
Detailed paths
-
Introduced through: python@3.8-slim › bzip2/libbz2-1.0@1.0.8-5+b1
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:12 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:12 bzip2.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42250
- https://cert.pl/en/posts/2026/05/CVE-2026-42250/
- https://sourceware.org/bzip2/
- https://inbox.sourceware.org/bzip2-devel/20260528145407.293768-1-mark@klomp.org/
- https://sourceware.org/cgit/bzip2/commit/?id=35d122a3df8b0cc4082a4d89fdc6ee99f375fe67
low severity
- Vulnerable module: diffutils
- Introduced through: diffutils@1:3.8-4
Detailed paths
-
Introduced through: python@3.8-slim › diffutils@1:3.8-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:12 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:12 diffutils.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53910
- https://cert.pl/en/posts/2026/07/CVE-2026-53910
- https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=73ed7ce85cc78effb94daf028c9af6b4e5252e50
- https://cgit.git.savannah.gnu.org/cgit/diffutils.git/commit/?id=9ff04d5b84743e331e80b589335a52c5480d1815
- https://git.savannah.gnu.org/cgit/diffutils.git/
low severity
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
- Fixed in: 1.21.23
Detailed paths
-
Introduced through: python@3.8-slim › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
It was discovered that dpkg-deb does not properly sanitize directory permissions when extracting a control member into a temporary directory, which is documented as being a safe operation even on untrusted data. This may result in leaving temporary files behind on cleanup. Given automated and repeated execution of dpkg-deb commands on adversarial .deb packages or with well compressible files, placed inside a directory with permissions not allowing removal by a non-root user, this can end up in a DoS scenario due to causing disk quota exhaustion or disk full conditions.
Remediation
Upgrade Debian:12 dpkg to version 1.21.23 or higher.
References
low severity
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
- Fixed in: 1.21.23
Detailed paths
-
Introduced through: python@3.8-slim › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
It was discovered that dpkg-deb (a component of dpkg, the Debian package management system) does not properly validate the end of the data stream when uncompressing a zstd-compressed .deb archive, which may result in denial of service (infinite loop spinning the CPU).
Remediation
Upgrade Debian:12 dpkg to version 1.21.23 or higher.
References
low severity
new
- Vulnerable module: dpkg
- Introduced through: dpkg@1.21.22
Detailed paths
-
Introduced through: python@3.8-slim › dpkg@1.21.22
NVD Description
Note: Versions mentioned in the description apply only to the upstream dpkg package and not the dpkg package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
A directory traversal bug was discovered when unpacking 3.0 (quilt) source packages, where the packaging tarball could contain the quilt database directory (.pc) with attacker controlled symlinks, where that in combination with patches that would fail to apply, could be used to make the code used to restore the backup files to either modify or remove the files pointed to by the attacker controlled symlinks.
Remediation
There is no fixed version for Debian:12 dpkg.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u5
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat in Expat before 2.7.2 allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u5 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-59375
- https://github.com/libexpat/libexpat/blob/676a4c531ec768732fac215da9730b5f50fbd2bf/expat/Changes#L45-L74
- https://github.com/libexpat/libexpat/blob/R_2_7_2/expat/Changes
- https://github.com/libexpat/libexpat/issues/1018
- https://github.com/libexpat/libexpat/pull/1034
- https://issues.oss-fuzz.com/issues/439133977
- http://www.openwall.com/lists/oss-security/2025/09/16/2
- http://www.openwall.com/lists/oss-security/2026/05/01/5
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
An issue was discovered in libexpat before 2.6.4. There is a crash within the XML_ResumeParser function because XML_StopParser can stop/suspend an unstarted parser.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-50602
- https://github.com/libexpat/libexpat/pull/915
- https://lists.debian.org/debian-lts-announce/2025/04/msg00040.html
- https://security.netapp.com/advisory/ntap-20250404-0008/
- https://cert-portal.siemens.com/productcert/html/ssa-202008.html
- https://cert-portal.siemens.com/productcert/html/ssa-355557.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.0 uses insufficient entropy, and thus hash flooding can occur via a crafted XML document.
Remediation
There is no fixed version for Debian:12 expat.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41080
- https://github.com/libexpat/libexpat/issues/47
- https://github.com/libexpat/libexpat/pull/1183
- https://blog.hartwork.org/posts/expat-2-8-0-released/
- https://www.openwall.com/lists/oss-security/2026/04/26/1
- http://www.openwall.com/lists/oss-security/2026/04/26/1
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in copyString.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
xmlwf in libexpat before 2.8.2 has an integer overflow for the output filename when -d outputDir is used.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in doProlog that is related to storeEntityValue and entity textLen.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
xmlwf in libexpat before 2.8.2 has an integer overflow in endDoctypeDecl via NOTATION declarations.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
xmlwf in libexpat before 2.8.2 has an integer overflow in resolveSystemId.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 has an integer overflow in XML_ParseBuffer because it lacked a check that was present in XML_Parse.
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 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:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: expat/libexpat1
- Introduced through: expat/libexpat1@2.5.0-1+deb12u1
- Fixed in: 2.5.0-1+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › expat/libexpat1@2.5.0-1+deb12u1
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:12 relevant fixed versions and status.
libexpat before 2.8.2 lacks handler call depth tracking for calls to XML_ResumeParser from within handlers in cases of a policy violation. Thus, a use-after-free can occur (similar to the CVE-2026-50219 situation).
Remediation
Upgrade Debian:12 expat to version 2.5.0-1+deb12u3 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u10
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
When the assert() function in the GNU C Library versions 2.13 to 2.40 fails, it does not allocate enough space for the assertion failure message string and size information, which may lead to a buffer overflow if the message string size aligns to page size.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u10 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-0395
- https://sourceware.org/bugzilla/show_bug.cgi?id=32582
- https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2025-0001
- https://sourceware.org/pipermail/libc-announce/2025/000044.html
- https://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/22/4
- http://www.openwall.com/lists/oss-security/2025/01/23/2
- https://security.netapp.com/advisory/ntap-20250228-0006/
- http://www.openwall.com/lists/oss-security/2025/04/13/1
- http://www.openwall.com/lists/oss-security/2025/04/24/7
- https://lists.debian.org/debian-lts-announce/2025/04/msg00039.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-577017.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u11
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Untrusted LD_LIBRARY_PATH environment variable vulnerability in the GNU C Library version 2.27 to 2.38 allows attacker controlled loading of dynamically shared library in statically compiled setuid binaries that call dlopen (including internal dlopen calls after setlocale or calls to NSS functions such as getaddrinfo).
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u11 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-4802
- https://sourceware.org/bugzilla/show_bug.cgi?id=32976
- https://sourceware.org/cgit/glibc/commit/?id=1e18586c5820e329f741d5c710275e165581380e
- http://www.openwall.com/lists/oss-security/2025/05/16/7
- http://www.openwall.com/lists/oss-security/2025/05/17/2
- https://lists.debian.org/debian-lts-announce/2025/05/msg00033.html
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u13
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
The regcomp function in the GNU C library version from 2.4 to 2.41 is subject to a double free if some previous allocation fails. It can be accomplished either by a malloc failure or by using an interposed malloc that injects random malloc failures. The double free can allow buffer manipulation depending of how the regex is constructed. This issue affects all architectures and ABIs supported by the GNU C library.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u13 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Passing too large an alignment to the memalign suite of functions (memalign, posix_memalign, aligned_alloc) in the GNU C Library version 2.30 to 2.42 may result in an integer overflow, which could consequently result in a heap corruption.
Note that the attacker must have control over both, the size as well as the alignment arguments of the memalign function to be able to exploit this. The size parameter must be close enough to PTRDIFF_MAX so as to overflow size_t along with the large alignment argument. This limits the malicious inputs for the alignment for memalign to the range [1<<62+ 1, 1<<63] and exactly 1<<63 for posix_memalign and aligned_alloc.
Typically the alignment argument passed to such functions is a known constrained quantity (e.g. page size, block size, struct sizes) and is not attacker controlled, because of which this may not be easily exploitable in practice. An application bug could potentially result in the input alignment being too large, e.g. due to a different buffer overflow or integer overflow in the application or its dependent libraries, but that is again an uncommon usage pattern given typical sources of alignments.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Calling getnetbyaddr or getnetbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend for networks and queries for a zero-valued network in the GNU C Library version 2.0 to version 2.42 can leak stack contents to the configured DNS resolver.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
The regcomp and regexec functions in the GNU C Library version 2.3 to version 2.44 may read freed memory and free the same heap block twice when a memory allocation fails while a regular expression is compiled or matched. The re_dfa_add_node (the NFA node table) and build_range_exp (bracket ranges) grow several arrays with consecutive realloc calls and store the new pointers only after all of them succeed. When a later call fails, the pattern buffer keeps pointers to blocks that were already freed, and the error cleanup frees them again. In regexec, the back-reference cache (match_ctx_add_entry) frees its array when a realloc fails but keeps the pointer, which is freed again on the error path.
An attacker does not need to supply a crafted regular expression: patterns large enough to grow these arrays are common. The failure has to hit a specific allocation, though, so the issue can only be reached when the system is already under memory pressure. An attacker who supplies the pattern or the subject string has little control over which allocation fails, so the expected impact is a crash of the process. This issue affects all architectures and ABIs supported by the GNU C Library.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Calling the wide scanf family of functions (swscanf, fwscanf, wscanf, vswscanf, vfwscanf and vwscanf) with a %s or %[ conversion without the 'l' length modifier in the GNU C Library version 2.2 to version 2.44 writes an extra null byte one past the end of the destination array when the converted multibyte string and its terminating null byte exactly fill that array.
These conversions store each wide input character into the caller's char array as a multibyte sequence. The conversion ends with the sequence that returns to the initial shift state, which also stores the terminating null byte, and the functions then append a second null byte. A destination sized for the converted string and one terminator, as the C standard requires the caller to provide, is therefore written one byte past its end. The out-of-bounds byte is always a null byte, which may corrupt adjacent data or crash the process. An attacker who supplies the input can trigger the overflow with a string whose converted length exactly fills the destination.
The narrow scanf functions, the %ls and %l[ conversions into a wchar_t array, and the 'a' and 'm' allocation modifiers are not affected, and storing a wide scanf conversion into a narrow char array is uncommon. This issue affects all architectures and ABIs supported by the GNU C Library.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Converting crafted CP949 input to UTF-8 character encoding and ignoring invalid characters, in the GNU C Library version 2.1 or later may result in the converter reading past the end of the input buffer, causing the calling application to crash.
When the CP949 decoder encounters an invalid input byte sequence like '\xa2\xe8' it ends up advancing the pointer tracking the read buffer position twice. If //IGNORE is set on the destination encoding and this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer. To exploit this, the target iconv function needs to set //IGNORE on the destination of the conversion and the input and encoding needs to be attacker controlled.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Converting crafted ISO-2022-CN-EXT input to UTF-8 character encoding, in the GNU C Library version 2.2 through 2.44 may result in the converter reading past the end of the input buffer, causing the calling application to crash.
When the ISO-2022-CN-EXT decoder encounters an invalid input byte sequence like '\x0e' it ends up advancing the pointer tracking the read buffer position twice. If this sequence is at the end of the input buffer, the decoder may then end up reading past the bounds of the input buffer. To exploit this, the input and encoding needs to be attacker controlled.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Converting crafted input from UCS-4 to IBM1390 or IBM1399 character encoding, in the GNU C Library version 2.3.3 and later may result in the converter reading past the end of the input buffer, causing the calling application to crash.
When converting from UCS-4, these encoders may encounter a combining base such as U+00E6 and jump ahead by 4 bytes to check the next UCS-4 code point. The check for end of buffer however does not account for this, which may result in a buffer overread if the following code point has less than 4 bytes remaining. Exploitation of this bug not only requires attacker control of input and encoding, but also strict control over layout of the input in memory.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
The glob functions in the GNU C Library versions 2.44 and earlier may free the same heap block twice when a memory allocation fails while glob prepends the directory name to the names it matched. The names already rewritten are freed, but their pointers stay in the result vector, and the error path frees them again with globfree.
The allocation must fail after at least one name has been rewritten, so the issue can only be reached when the process is already close to its memory limit, for example under an address space limit (RLIMIT_AS) or on a 32-bit system. The attacker needs control to make the result large enough to make the program or service run out of memory, either by controlling the glob pattern and having knowledge of the filesystem layout or through other means. This issue affects all architectures and ABIs supported by the GNU C Library.
Remediation
There is no fixed version for Debian:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2026-126765
- https://sourceware.org/bugzilla/show_bug.cgi?id=34993
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0032
- https://sourceware.org/pipermail/libc-alpha/2026-November/182067.html
- http://www.openwall.com/lists/oss-security/2026/11/19/9
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
The iconv() function in the GNU C Library versions 2.43 and earlier may crash due to an assertion failure when converting inputs from the IBM1390 or IBM1399 character sets, which may be used to remotely crash an application.
This vulnerability can be trivially mitigated by removing the IBM1390 and IBM1399 character sets from systems that do not need them.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-4046
- https://sourceware.org/bugzilla/show_bug.cgi?id=33980
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0007;hb=HEAD
- https://inbox.sourceware.org/libc-announce/76814edf-cf7f-47ec-979d-2dce0a2c76bf@gotplt.org/T/#u
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C Library version 2.34 to version 2.43 could, with a crafted response from the configured DNS server, result in a violation of the DNS specification that causes the application to treat a non-answer section of the DNS response as a valid answer.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
- Fixed in: 2.36-9+deb12u14
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
Calling gethostbyaddr or gethostbyaddr_r with a configured nsswitch.conf that specifies the library's DNS backend in the GNU C library version 2.34 to version 2.43 could result in an invalid DNS hostname being returned to the caller in violation of the DNS specification.
Remediation
Upgrade Debian:12 glibc to version 2.36-9+deb12u14 or higher.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
The deprecated functions ns_printrrf, ns_printrr and fp_nquery in the GNU C Library version 2.0.1 to version 2.43 fail to validate the RDATA content against the RDATA length in a DNS response when processing A6, CERT, LOC, TKEY or TSIG records, which may allow an attacker to craft a DNS response, causing a target application to crash or read uninitialized memory.
These functions are for application debugging only and hence not in the path of code executed by the DNS resolver. Further, they have been deprecated since version 2.34 and should not be used by any new applications. Applications should consider porting away from these interfaces since they may be removed in future versions.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
new
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 relevant fixed versions and status.
The gettext family of functions in the GNU C Library version 2.0 and later accept LANGUAGE environment variable entries that contain '/' or that are equal to "..", unless the program is setuid or setgid (AT_SECURE). An attacker who can set LANGUAGE in the environment of a program that uses gettext can make it load a message catalog (.mo file) from an arbitrary location in the file system. A crafted .mo file can crash the program through out-of-range offsets, or supply translations whose format directives do not match the arguments passed by the program. That causes undefined behaviour in the printf family of functions and may allow arbitrary code execution with the privileges of the program. The safety of message catalogs relies on them being installed in trusted, read-only locations, and the directory traversal bypasses this.
The fix for CVE-2014-0475 rejects ".." path components in locale names passed to setlocale or taken from the LC_ALL, LC_* and LANG environment variables. gettext reads LANGUAGE directly and appends each colon-separated entry to the message catalog directory, so that fix did not cover LANGUAGE.
LANGUAGE is only used when the LC_MESSAGES locale is not "C", "C.<encoding>" or "POSIX", so the attacker must also be able to select another installed locale, for example through LANG or LC_ALL. Exploitation also requires that the attacker can place the crafted file in a location readable by the target program, and that the environment crosses a trust boundary without the program running as AT_SECURE. An example is an SSH server that accepts LANGUAGE and LANG from clients through the AcceptEnv directive and restricts an account to a forced command; the attacker may use this to escape the restriction.
Remediation
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
- https://security-tracker.debian.org/tracker/CVE-2026-8674
- https://joshua.hu/fuzzing-glibc-libresolv
- https://sourceware.org/bugzilla/show_bug.cgi?id=31026
- https://sourceware.org/git/?p=glibc.git;a=blob_plain;f=advisories/GLIBC-SA-2026-0021
- https://sourceware.org/git/?p=glibc.git;a=commit;h=506ea57086bfb9ce3daff1c14246a1cb532aba0a
- http://www.openwall.com/lists/oss-security/2026/09/17/4
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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:12 glibc.
References
low severity
- Vulnerable module: glibc/libc-bin
- Introduced through: glibc/libc-bin@2.36-9+deb12u8 and glibc/libc6@2.36-9+deb12u8
Detailed paths
-
Introduced through: python@3.8-slim › glibc/libc-bin@2.36-9+deb12u8
-
Introduced through: python@3.8-slim › glibc/libc6@2.36-9+deb12u8
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:12 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
There is no fixed version for Debian:12 glibc.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.40-1.1
Detailed paths
-
Introduced through: python@3.8-slim › gnupg2/gpgv@2.2.40-1.1
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
- Vulnerable module: gnupg2/gpgv
- Introduced through: gnupg2/gpgv@2.2.40-1.1
Detailed paths
-
Introduced through: python@3.8-slim › gnupg2/gpgv@2.2.40-1.1
NVD Description
Note: Versions mentioned in the description apply only to the upstream gnupg2 package and not the gnupg2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
gpgtar in GnuPG before 2.5.19 can allow file overwrite via crafted data in an archive. When extracting an untrusted archive with --directory (aka -C) into an existing directory containing a pre-existing symlink, gpgtar can follow that symlink and create or overwrite a file outside the selected extraction directory. The write is limited by the extraction user's filesystem permissions. An archive extracted into a fresh empty directory does not have this risk.
Remediation
There is no fixed version for Debian:12 gnupg2.
References
low severity
new
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
The certificate authentication info handling in gnutls from 2.5.9 up to 3.8.13 does not reset the certificate count and list pointer when re-allocation of raw_certificate_list fails, which allows remote attackers to cause a denial of service for a peer under heap pressure.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
low severity
new
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
The RSA-PSK ClientKeyExchange handler in gnutls before 3.8.14 does not return after detecting a memory allocation failure when copying the PSK username, which allows remote attackers to cause a denial of service for a peer under heap pressure.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
low severity
new
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
A double free in the X.509 name constraints enforcement of GnuTLS 3.8.13 on all platforms allows a remote attacker to cause a denial of service (application crash) via a certificate chain containing a NameConstraints extension processed while the application is under memory pressure. When an already populated name constraints object is reinitialized, previously freed list pointers are not cleared, so a memory allocation failure precisely at reinitialization leaves a dangling pointer that is freed again during a later cleanup.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
GnuTLS v3.8.13 does not reject end-entity X.509 certificates that contain a contradictory combination of Key Usage (KU) and Extended Key Usage (EKU). NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2026-67693
- http://gnutls.com
- https://gist.github.com/lkloliver/6fbfc191bc6163942c8017551ac3f238
- https://gitlab.com/gnutls/gnutls/-/blob/3.8.13/lib/x509/verify.c#L1119-1178
- https://gitlab.com/gnutls/gnutls/-/work_items/1642
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-67693
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
GnuTLS v3.8.13 can perhaps unexpectedly trust a certificate on the basis of Common Name when Subject Alternative Name has an SRV otherName (1.3.6.1.5.5.7.8.7) whose value is an OCTET STRING. NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2026-88647
- https://gist.github.com/lkloliver/f98ec3de1a871fdfc02b70b8b9ba7642
- https://gitlab.com/gnutls/gnutls/-/issues/1802
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-88647
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
In GnuTLS v3.8.13, an excluded msUPN/SRV otherName is never checked. NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2026-88648
- https://gist.github.com/lkloliver/1f2a97cb8d0b31aa27b6bd0354358d7d
- https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.10
- https://www.rfc-editor.org/rfc/rfc5280#section-6.1.4
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-88648
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
GnuTLS v3.8.13 does not properly enforce name constraints, as demonstrated by a permitted subtree violation for "EE O=Evil accepted although outside permitted O=Good." NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2026-95184
- http://gnutls.com
- https://evil.com
- https://gist.github.com/lkloliver/0c8b47fa75a0958fa88587665b82ae15
- https://www.gnutls.org
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-95184
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
low severity
- Vulnerable module: gnutls28/libgnutls30
- Introduced through: gnutls28/libgnutls30@3.7.9-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › gnutls28/libgnutls30@3.7.9-2+deb12u3
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:12 relevant fixed versions and status.
GnuTLS v3.8.13 does not reject a critical keyUsage extension when it cannot be processed, such as when extnValue is an ASN.1 NULL (05 00) instead of a BIT STRING. NOTE: the Supplier does not consider this an actionable security vulnerability because of its "threat model doesn't consider attacks only possible by modifying anything within the trust boundary (private keys, trusted certificate authorities and their issued certificates including intermediate CAs, etc.)" policy.
Remediation
There is no fixed version for Debian:12 gnutls28.
References
- https://security-tracker.debian.org/tracker/CVE-2026-95210
- http://gnutls.com
- https://gist.github.com/lkloliver/4aad23689202720c4068f43b3c6069c7
- https://gitlab.com/gnutls/gnutls/-/blob/e2169a87c7fb91935c2845088204b102baed4c5f/SECURITY.md
- https://gitlab.com/gnutls/gnutls/-/work_items/1965
- https://github.com/lkloliver/poc/tree/main/CVE-2026-95210
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 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:12 krb5.
References
low severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
new
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
NVD Description
This vulnerability has not been analyzed by NVD yet.
Remediation
There is no fixed version for Debian:12 krb5.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
- Fixed in: 1.20.1-2+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 relevant fixed versions and status.
In MIT Kerberos 5 (aka krb5) before 1.22 (with incremental propagation), there is an integer overflow for a large update size to resize() in kdb_log.c. An authenticated attacker can cause an out-of-bounds write and kadmind daemon crash.
Remediation
Upgrade Debian:12 krb5 to version 1.20.1-2+deb12u3 or higher.
References
low severity
- Vulnerable module: krb5/libgssapi-krb5-2
- Introduced through: krb5/libgssapi-krb5-2@1.20.1-2+deb12u2, krb5/libk5crypto3@1.20.1-2+deb12u2 and others
Detailed paths
-
Introduced through: python@3.8-slim › krb5/libgssapi-krb5-2@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libk5crypto3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5-3@1.20.1-2+deb12u2
-
Introduced through: python@3.8-slim › krb5/libkrb5support0@1.20.1-2+deb12u2
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:12 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:12 krb5.
References
low severity
- Vulnerable module: libcap2
- Introduced through: libcap2@1:2.66-4
- Fixed in: 1:2.66-4+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › libcap2@1:2.66-4
NVD Description
Note: Versions mentioned in the description apply only to the upstream libcap2 package and not the libcap2 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
The PAM module pam_cap.so of libcap configuration supports group names starting with “@”, during actual parsing, configurations not starting with “@” are incorrectly recognized as group names. This may result in nonintended users being granted an inherited capability set, potentially leading to security risks. Attackers can exploit this vulnerability to achieve local privilege escalation on systems where /etc/security/capability.conf is used to configure user inherited privileges by constructing specific usernames.
Remediation
Upgrade Debian:12 libcap2 to version 1:2.66-4+deb12u1 or higher.
References
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
Detailed paths
-
Introduced through: python@3.8-slim › libgcrypt20@1.10.1-3
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:12 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:12 libgcrypt20.
References
- https://security-tracker.debian.org/tracker/CVE-2024-2236
- https://access.redhat.com/errata/RHSA-2024:9404
- https://bugzilla.redhat.com/show_bug.cgi?id=2268268
- https://access.redhat.com/errata/RHSA-2025:3534
- https://access.redhat.com/errata/RHSA-2025:3530
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://access.redhat.com/security/cve/CVE-2024-2236
- https://bugzilla.redhat.com/show_bug.cgi?id=2245218
low severity
- Vulnerable module: libgcrypt20
- Introduced through: libgcrypt20@1.10.1-3
- Fixed in: 1.10.1-3+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › libgcrypt20@1.10.1-3
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:12 relevant fixed versions and status.
Libgcrypt before 1.12.2 sometimes allows a heap-based buffer overflow and denial of service via crafted ECDH ciphertext to gcry_pk_decrypt.
Remediation
Upgrade Debian:12 libgcrypt20 to version 1.10.1-3+deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-41989
- https://dev.gnupg.org/T8211
- https://lists.gnupg.org/pipermail/gnupg-announce/2026q2/000503.html
- https://www.openwall.com/lists/oss-security/2026/04/21/1
- https://cert-portal.siemens.com/productcert/html/ssa-019113.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: libtasn1-6
- Introduced through: libtasn1-6@4.19.0-2
Detailed paths
-
Introduced through: python@3.8-slim › libtasn1-6@4.19.0-2
NVD Description
Note: Versions mentioned in the description apply only to the upstream libtasn1-6 package and not the libtasn1-6 package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
Stack-based buffer overflow in libtasn1 version: v4.20.0. The function fails to validate the size of input data resulting in a buffer overflow in asn1_expend_octet_string.
Remediation
There is no fixed version for Debian:12 libtasn1-6.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.16-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.
Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.
There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.
The FIPS modules in 3.4, 3.3, 3.2, 3.1 and 3.0 are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.16-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-13176
- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- https://openssl-library.org/news/secadv/20250120.txt
- http://www.openwall.com/lists/oss-security/2025/01/20/2
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.html
- https://security.netapp.com/advisory/ntap-20250124-0005/
- https://security.netapp.com/advisory/ntap-20250418-0010/
- https://security.netapp.com/advisory/ntap-20250502-0006/
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.15-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Calling the OpenSSL API function SSL_select_next_proto with an empty supported client protocols buffer may cause a crash or memory contents to be sent to the peer.
Impact summary: A buffer overread can have a range of potential consequences such as unexpected application beahviour or a crash. In particular this issue could result in up to 255 bytes of arbitrary private data from memory being sent to the peer leading to a loss of confidentiality. However, only applications that directly call the SSL_select_next_proto function with a 0 length list of supported client protocols are affected by this issue. This would normally never be a valid scenario and is typically not under attacker control but may occur by accident in the case of a configuration or programming error in the calling application.
The OpenSSL API function SSL_select_next_proto is typically used by TLS applications that support ALPN (Application Layer Protocol Negotiation) or NPN (Next Protocol Negotiation). NPN is older, was never standardised and is deprecated in favour of ALPN. We believe that ALPN is significantly more widely deployed than NPN. The SSL_select_next_proto function accepts a list of protocols from the server and a list of protocols from the client and returns the first protocol that appears in the server list that also appears in the client list. In the case of no overlap between the two lists it returns the first item in the client list. In either case it will signal whether an overlap between the two lists was found. In the case where SSL_select_next_proto is called with a zero length client list it fails to notice this condition and returns the memory immediately following the client list pointer (and reports that there was no overlap in the lists).
This function is typically called from a server side application callback for ALPN or a client side application callback for NPN. In the case of ALPN the list of protocols supplied by the client is guaranteed by libssl to never be zero in length. The list of server protocols comes from the application and should never normally be expected to be of zero length. In this case if the SSL_select_next_proto function has been called as expected (with the list supplied by the client passed in the client/client_len parameters), then the application will not be vulnerable to this issue. If the application has accidentally been configured with a zero length server list, and has accidentally passed that zero length server list in the client/client_len parameters, and has additionally failed to correctly handle a "no overlap" response (which would normally result in a handshake failure in ALPN) then it will be vulnerable to this problem.
In the case of NPN, the protocol permits the client to opportunistically select a protocol when there is no overlap. OpenSSL returns the first client protocol in the no overlap case in support of this. The list of client protocols comes from the application and should never normally be expected to be of zero length. However if the SSL_select_next_proto function is accidentally called with a client_len of 0 then an invalid memory pointer will be returned instead. If the application uses this output as the opportunistic protocol then the loss of confidentiality will occur.
This issue has been assessed as Low severity because applications are most likely to be vulnerable if they are using NPN instead of ALPN - but NPN is not widely used. It also requires an application configuration or programming error. Finally, this issue would not typically be under attacker control making active exploitation unlikely.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Due to the low severity of this issue we are not issuing new releases of OpenSSL at this time. The fix will be included in the next releases when they become available.
Remediation
Upgrade Debian:12 openssl to version 3.0.15-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-5535
- http://www.openwall.com/lists/oss-security/2024/06/27/1
- http://www.openwall.com/lists/oss-security/2024/06/28/4
- http://www.openwall.com/lists/oss-security/2024/08/15/1
- https://github.com/openssl/openssl/commit/4ada436a1946cbb24db5ab4ca082b69c1bc10f37
- https://github.com/openssl/openssl/commit/99fb785a5f85315b95288921a321a935ea29a51e
- https://github.com/openssl/openssl/commit/cf6f91f6121f4db167405db2f0de410a456f260c
- https://github.com/openssl/openssl/commit/e86ac436f0bd54d4517745483e2315650fae7b2c
- https://github.openssl.org/openssl/extended-releases/commit/9947251413065a05189a63c9b7a6c1d4e224c21c
- https://github.openssl.org/openssl/extended-releases/commit/b78ec0824da857223486660177d3b1f255c65d87
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20240712-0005/
- https://security.netapp.com/advisory/ntap-20241025-0006/
- https://security.netapp.com/advisory/ntap-20241025-0010/
- https://www.openssl.org/news/secadv/20240627.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-613116.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
- https://cert-portal.siemens.com/productcert/html/ssa-915275.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.15-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.
Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.
In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.
The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.
Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.15-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-9143
- https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
- https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
- https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
- https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
- https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
- https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
- https://openssl-library.org/news/secadv/20241016.txt
- http://www.openwall.com/lists/oss-security/2024/10/16/1
- http://www.openwall.com/lists/oss-security/2024/10/23/1
- http://www.openwall.com/lists/oss-security/2024/10/24/1
- https://lists.debian.org/debian-lts-announce/2024/10/msg00033.html
- https://lists.debian.org/debian-lts-announce/2024/11/msg00000.html
- https://security.netapp.com/advisory/ntap-20241101-0001/
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-277137.html
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
- https://cert-portal.siemens.com/productcert/html/ssa-769027.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow.
Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.
When parsing CMS (Auth)EnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs.
Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME (Auth)EnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.
OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15467
- https://github.com/openssl/openssl/commit/2c8f0e5fa9b6ee5508a0349e4572ddb74db5a703
- https://github.com/openssl/openssl/commit/5f26d4202f5b89664c5c3f3c62086276026ba9a9
- https://github.com/openssl/openssl/commit/6ced0fe6b10faa560e410e3ee8d6c82f06c65ea3
- https://github.com/openssl/openssl/commit/ce39170276daec87f55c39dad1f629b56344429e
- https://github.com/openssl/openssl/commit/d0071a0799f20cc8101730145349ed4487c268dc
- https://openssl-library.org/news/secadv/20260127.txt
- http://www.openwall.com/lists/oss-security/2026/01/27/10
- http://www.openwall.com/lists/oss-security/2026/02/25/6
- https://github.com/guiimoraes/CVE-2025-15467
- https://cert-portal.siemens.com/productcert/html/ssa-434797.html
- https://access.redhat.com/errata/RHSA-2026:1472
- https://access.redhat.com/errata/RHSA-2026:1473
- https://access.redhat.com/errata/RHSA-2026:1496
- https://access.redhat.com/errata/RHSA-2026:1503
- https://access.redhat.com/errata/RHSA-2026:1519
- https://access.redhat.com/errata/RHSA-2026:1594
- https://access.redhat.com/errata/RHSA-2026:1733
- https://access.redhat.com/errata/RHSA-2026:1736
- https://access.redhat.com/errata/RHSA-2026:2072
- https://access.redhat.com/errata/RHSA-2026:2077
- https://access.redhat.com/errata/RHSA-2026:2485
- https://access.redhat.com/errata/RHSA-2026:2563
- https://access.redhat.com/errata/RHSA-2026:2633
- https://access.redhat.com/errata/RHSA-2026:2659
- https://access.redhat.com/errata/RHSA-2026:2671
- https://access.redhat.com/errata/RHSA-2026:2844
- https://access.redhat.com/errata/RHSA-2026:2974
- https://access.redhat.com/errata/RHSA-2026:2995
- https://access.redhat.com/errata/RHSA-2026:3228
- https://access.redhat.com/errata/RHSA-2026:3415
- https://access.redhat.com/errata/RHSA-2026:3461
- https://access.redhat.com/errata/RHSA-2026:3462
- https://access.redhat.com/errata/RHSA-2026:4419
- https://access.redhat.com/errata/RHSA-2026:4943
- https://access.redhat.com/errata/RHSA-2026:6481
- https://access.redhat.com/errata/RHSA-2026:7261
- https://access.redhat.com/security/cve/CVE-2025-15467
- https://bugzilla.redhat.com/show_bug.cgi?id=2430376
- https://cert-portal.siemens.com/productcert/html/ssa-734552.html
- https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-15467.json
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system.
Remediation
There is no fixed version for Debian:12 openssl.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-68160
- https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
- https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69418
- https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
- https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
- https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
- https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
- https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69419
- https://github.com/openssl/openssl/commit/41be0f216404f14457bbf3b9cc488dba60b49296
- https://github.com/openssl/openssl/commit/7e9cac9832e4705b91987c2474ed06a37a93cecb
- https://github.com/openssl/openssl/commit/a26a90d38edec3748566129d824e664b54bee2e2
- https://github.com/openssl/openssl/commit/cda12de3bc0e333ea8d2c6fd15001dbdaf280015
- https://github.com/openssl/openssl/commit/ff628933755075446bca8307e8417c14d164b535
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-69420
- https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9
- https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
- https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
- https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
- https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.17-1~deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.
Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.
Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.17-1~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9230
- https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45
- https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280
- https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def
- https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd
- https://github.com/openssl/openssl/commit/bae259a211ada6315dc50900686daaaaaa55f482
- https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3
- https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba
- https://openssl-library.org/news/secadv/20250930.txt
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://lists.debian.org/debian-lts-announce/2025/10/msg00001.html
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-585531.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.17-1~deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address.
Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application.
The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker.
In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity.
The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.
The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.17-1~deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-9232
- https://github.com/openssl/openssl/commit/2b4ec20e47959170422922eaff25346d362dcb35
- https://github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b
- https://github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3
- https://github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf
- https://github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0
- https://openssl-library.org/news/secadv/20250930.txt
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-585531.html
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: When an application passes a stack to PEM_X509_INFO_read_bio_ex() to add entries to, and reading fails, OpenSSL frees every entry in the stack, both the old ones and any new ones, but leaves them in the stack.
Impact summary: An application that passes an existing stack to PEM_X509_INFO_read_bio_ex() and keeps using it after a failed read may use memory that was already freed. This can cause a crash or, in principle, memory corruption. Malformed PEM data can make the read fail, but only applications that pass an existing stack are affected, and OpenSSL itself does not do this.
CWE: CWE-416: Use After Free
Description: PEM_X509_INFO_read_bio_ex() reads certificates, CRLs and private keys from PEM data and adds them to a stack of X509_INFO structures. If the application passes a stack that is not NULL, the function adds the new entries to it and must leave the entries that are already there unchanged.
If reading fails, the function frees every entry in the stack. This includes the entries that were there before the call, and the entries added by the call. It does not remove these entries from the stack, so the stack keeps pointers to freed memory. The failure can happen at any point, even before any entry was added. A PEM item with invalid content is enough. This also happens if the stack was empty: entries added before the failure are freed but stay in the stack.
An application that then reads or frees the stack will use memory that was already freed. This can crash the application or, in principle, corrupt memory.
Only applications that pass a stack that is not NULL are affected. OpenSSL itself never does this. Its own callers, including the code that TLS uses to load CA certificates, always pass NULL. When the stack is NULL, the function frees only the entries that it created itself, which is safe. We expect that very few applications pass an existing stack. An attacker can make the read fail with malformed PEM data, but cannot make an application pass an existing stack.
The same problem affects PEM_X509_INFO_read_bio(), PEM_X509_INFO_read() and PEM_X509_INFO_read_ex(), which use the same code. OpenSSL 1.1.1 and 1.0.2 have only the first two of these functions.
FIPS impact: no The affected code is outside the FIPS module boundary.
Remediation
There is no fixed version for Debian:12 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-107493
- https://github.com/openssl/openssl/commit/0486dfadfec558e1808f59d35a8d79e541c4e7d7
- https://github.com/openssl/openssl/commit/c57a5ccf0c060755b5494a6870922b7c6cdd7dd8
- https://github.com/openssl/openssl/commit/c8f6d04f8e6d40b1bf83334e4a2ec9daf5943a3d
- https://openssl-library.org/news/secadv/20261117.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Encrypting a CMS message to an EC certificate whose group order is 1 may cause CMS_encrypt() or CMS_encrypt_ex() to loop indefinitely.
Impact summary: An attacker able to supply the recipient certificate to an application performing CMS encryption can cause that application to loop indefinitely, consuming CPU and resulting in Denial of Service.
CWE: CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop')
Description: CMS_encrypt() and CMS_encrypt_ex() encrypt a message to one or more recipient certificates and, for an EC recipient, generate an ephemeral key in the recipient's group. If the certificate declares a group order of 1, random scalar generation can only produce zero. The key generation routine then retries without limit while waiting for a nonzero private scalar, so the call never returns.
The OpenSSL TLS and QUIC implementations do not use this path. An application is exposed only if it calls CMS_encrypt() or CMS_encrypt_ex() with a recipient certificate whose EC parameters are attacker-controlled. Certificates with normal EC group orders do not trigger the loop.
OpenSSL 4.0 and later reject unknown explicit EC groups in default builds. These versions are affected only when configured with the enable-ec_explicit_curves option.
The result is a hang that consumes a CPU core until the process is interrupted, a Denial of Service. The severity is Low because the attacker must supply the recipient certificate and the application must choose to encrypt to it; ordinary CMS encryption to trusted recipients is unaffected.
The fix makes EC key generation fail when the group has no valid nonzero private scalar, instead of retrying indefinitely.
FIPS impact: no The FIPS modules in 4.1, 4.0, 3.5 and 3.0 are not affected. The FIPS provider does not support arbitrary explicit EC domain parameters, so an order-1 group is rejected during key import before the vulnerable key generation path is reached.
Remediation
There is no fixed version for Debian:12 openssl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-107496
- https://github.com/openssl/openssl/commit/36e15b618decdff1b116eead6747718e6e729ad2
- https://github.com/openssl/openssl/commit/a0051cfe699bf5a047bc1c4faef65f80f7987366
- https://github.com/openssl/openssl/commit/a8531368ddb1f86d2a2782a8b693926bb67b59e7
- https://openssl-library.org/news/secadv/20261110.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22795
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.18-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.18-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-22796
- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.19-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer.
Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker.
RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced.
If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext.
As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue.
The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.19-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-31790
- https://github.com/openssl/openssl/commit/001e01db3e996e13ffc72386fe79d03a6683b5ac
- https://github.com/openssl/openssl/commit/abd8b2eec7e3f3fda60ecfb68498b246b52af482
- https://github.com/openssl/openssl/commit/b922e24e5b23ffb9cb9e14cadff23d91e9f7e406
- https://github.com/openssl/openssl/commit/d5f8e71cd0a54e961d0c3b174348f8308486f790
- https://github.com/openssl/openssl/commit/eed200f58cd8645ed77e46b7e9f764e284df379e
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: Parsing a crafted DER-encoded ASN.1 structure with a primitive element whose content exceeds 2 gigabytes in length may cause a heap buffer over-read on 64-bit Unix and Unix-like platforms.
Impact summary: The heap buffer over-read may crash the application (Denial of Service) or to load into the decoded ASN.1 object contents of memory beyond the end of the input buffer. More typically such ASN.1 elements would instead be truncated.
An integer truncation in OpenSSL's ASN.1 decoder causes the content length of an ASN.1 primitive element to be mishandled when it exceeds 2 gigabytes. In the worst case the truncated length is treated as a request to scan the binary content for a terminating zero byte, possibly causing OpenSSL to read either less than or beyond the end of the allocated buffer.
Applications that pass attacker-supplied data to d2i_X509(), d2i_PKCS7(), or any other d2i_* decoding function are affected. OpenSSL's own command-line tools are not vulnerable, as data read through the BIO layer is checked before it reaches the affected code. The issue only affects 64-bit Unix and Unix-like platforms; 32-bit platforms and 64-bit Windows are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34180
- https://github.com/openssl/security/commit/1c6908e4fa5fa568752221d8eaf561a809751e5d
- https://github.com/openssl/security/commit/cbe418ae978539cf14a398a207dba834c0e93e83
- https://github.com/openssl/security/commit/d93853c42110d6319e3df07842b488cb9f7ac5ff
- https://github.com/openssl/security/commit/da5d62af75f69d6fbf7803743d7c56ac75461e43
- https://github.com/openssl/security/commit/f696c73c3e61b8c502d040af62e690c060908a16
- https://github.com/openssl/openssl/commit/1c6908e4fa5fa568752221d8eaf561a809751e5d
- https://github.com/openssl/openssl/commit/cbe418ae978539cf14a398a207dba834c0e93e83
- https://github.com/openssl/openssl/commit/d93853c42110d6319e3df07842b488cb9f7ac5ff
- https://github.com/openssl/openssl/commit/da5d62af75f69d6fbf7803743d7c56ac75461e43
- https://github.com/openssl/openssl/commit/f696c73c3e61b8c502d040af62e690c060908a16
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue Summary: Cryptographic Message Services (CMS) processing fails to perform sufficient input validation on the cipher and tag length fields of AuthEnvelopedData containers, leading to various potential compromises.
Impact Summary: Attackers making use of these vulnerabilities may achieve key-equivalent functionality for a given CMS recipient and/or bypass integrity validation for a given message.
In one use case, an attacker may send a CMS message containing AuthEnvelopedData with the cipher specified as a non-AEAD cipher. OpenSSL erroneously allows this selection, and attempts to decrypt and validate the message.
An on-path attacker who captures one legitimate AES-GCM AuthEnvelopedData addressed to the victim can re-emit it with the recipientInfos set left byte-for-byte intact, so the victim's private key still unwraps the genuine CEK (the content-encryption key), but with the inner OID rewritten to AES-256-OFB (Output Feedback Mode, an unauthenticated keystream mode) and with an attacker-chosen IV and ciphertext. The victim initializes AES-256-OFB under the real CEK, never consults the MAC field, and CMS_decrypt() returns success.
If the application under attack responds to the attacker with any indicator showing success or failure of the decryption effort, it is possible for the attacker to use this as an oracle to obtain key equivalent functionality for the CEK used for the chosen recipient of the message.
In another use case, an attacker can reduce the tag length of the chosen AEAD cipher for a given AuthEnvelopedData container to be a single byte long, allowing an attacker to brute force CMS decryption, producing an integrity bypass for applications that trust CMS_decrypt() to reject modified content.
The FIPS modules are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-34182
- https://github.com/openssl/security/commit/03c1f4d45fb963aee7d5833390c507cd290182bc
- https://github.com/openssl/security/commit/439ed7d2c0962ce964482727264668bf277c333f
- https://github.com/openssl/security/commit/7947e6a81eb8776802f159fb6762cb7fcf7e34c7
- https://github.com/openssl/security/commit/9fd97f8cfdc2c0be214998de3b2b55c8edf6c7ac
- https://github.com/openssl/security/commit/d2ca86bcd43e4f17d899f347101766b6107676e0
- https://github.com/openssl/openssl/commit/03c1f4d45fb963aee7d5833390c507cd290182bc
- https://github.com/openssl/openssl/commit/439ed7d2c0962ce964482727264668bf277c333f
- https://github.com/openssl/openssl/commit/7947e6a81eb8776802f159fb6762cb7fcf7e34c7
- https://github.com/openssl/openssl/commit/9fd97f8cfdc2c0be214998de3b2b55c8edf6c7ac
- https://github.com/openssl/openssl/commit/d2ca86bcd43e4f17d899f347101766b6107676e0
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-35189
- https://github.com/openssl/openssl/commit/2b93c73b2c70ddc4c61c5e4bfaaa6bd71379eb84
- https://github.com/openssl/openssl/commit/3842516cc15e8b2cf55747011045e77547e71d89
- https://github.com/openssl/openssl/commit/8e0efc7549b7ff8246d40e585e3fd604f728473f
- https://github.com/openssl/openssl/commit/c72ae182cac17a82e4246c6ecd4e9c4ec3586ec9
- https://openssl-library.org/news/secadv/20260929.txt
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: A specially crafted password-encrypted CMS message can trigger a NULL pointer dereference during CMS decryption.
Impact summary: This NULL pointer dereference leads to an application crash and a Denial of Service.
The CMS PasswordRecipientInfo.keyDerivationAlgorithm field is defined as OPTIONAL in the ASN.1 specification and may therefore be absent in specially crafted inputs. During the password-based CMS decryption the OpenSSL CMS implementation dereferences this field without first checking whether it was present.
An attacker who supplies such a CMS message to an application performing password-based CMS decryption can trigger an application crash, leading to a Denial of Service.
Applications that process password-encrypted CMS messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42766
- https://github.com/openssl/security/commit/056d06c1918fafbb98c1c85a02e4c47cc4e199ce
- https://github.com/openssl/security/commit/12bc26ffb3a2be728c9b86e1cae277de5b33dfa4
- https://github.com/openssl/security/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7
- https://github.com/openssl/security/commit/ab52d88cb5374876d59aee3c91f9e4ccce2b7ce4
- https://github.com/openssl/security/commit/da26f368732b83e40e9d356fe61c3d3aaab6d2e8
- https://github.com/openssl/openssl/commit/056d06c1918fafbb98c1c85a02e4c47cc4e199ce
- https://github.com/openssl/openssl/commit/12bc26ffb3a2be728c9b86e1cae277de5b33dfa4
- https://github.com/openssl/openssl/commit/3ff64913615d648cfbb6a6f1cf5529ae7ea829d7
- https://github.com/openssl/openssl/commit/ab52d88cb5374876d59aee3c91f9e4ccce2b7ce4
- https://github.com/openssl/openssl/commit/da26f368732b83e40e9d356fe61c3d3aaab6d2e8
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: An attacker-controlled CMP (Certificate Management Protocol) server could trigger a NULL pointer dereference in a CMP client application.
Impact summary: A NULL pointer dereference causes a crash of the application and a Denial of Service.
An attacker controlling a CMP server (or acting as a man-in-the-middle) could craft a CMP response containing a CRMF (Certificate Request Message Format) CertRepMessage with an EncryptedValue structure where the symmAlg field has an algorithm OID but no parameters field. When the OpenSSL CMP client processes this response, the NULL dereference occurs, causing a crash of the CMP client.
Applications that process untrusted CMP/CRMF messages may be affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.22-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42767
- https://github.com/openssl/security/commit/61a86a8cd73546c9fea916f3d304c1293e05c046
- https://github.com/openssl/security/commit/665d5254083affde9982efca7c41dd01cacc8774
- https://github.com/openssl/security/commit/810b722f772652ad48042bcc7ab07e3414b11d0f
- https://github.com/openssl/security/commit/b90ff3b1bd33b1c18e6a09936d097c2eddef8873
- https://github.com/openssl/security/commit/e6f912907fc2ec82a0fd07aae55172c5e5e3d90d
- https://github.com/openssl/openssl/commit/61a86a8cd73546c9fea916f3d304c1293e05c046
- https://github.com/openssl/openssl/commit/665d5254083affde9982efca7c41dd01cacc8774
- https://github.com/openssl/openssl/commit/810b722f772652ad48042bcc7ab07e3414b11d0f
- https://github.com/openssl/openssl/commit/b90ff3b1bd33b1c18e6a09936d097c2eddef8873
- https://github.com/openssl/openssl/commit/e6f912907fc2ec82a0fd07aae55172c5e5e3d90d
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the peer key is not properly checked for the subgroup membership.
Impact summary: A malicious peer which presents an X9.42 key carrying the victim's p and g parameters, a forged q = r (a small prime factor of the cofactor (p−1)/q_local), and a public value Y of order r can recover the victim's private key after a small number of key exchange attempts.
When EVP_PKEY_derive_set_peer() is called with a DHX (X9.42) peer key, the subgroup membership check Y^q ≡ 1 (mod p) is performed using the peer's own q parameter, not the local key's q. The peer's domain parameters are then matched against the domain parameters of the private key, but the value of q is not compared.
A malicious peer who presents an X9.42 key carrying the victim's p, g, a forged q = r (a small prime factor of the cofactor), and a public value Y of order r passes all checks. The shared secret then takes only r distinct values, leaking priv mod r. Repeating for each small-prime factor of the cofactor and combining via CRT recovers the full private key (Lim–Lee / small-subgroup-confinement attack).
The realistic attack surface is narrow: principally CMP deployments with long-lived RA/CA DHX keys and bespoke enterprise or government applications using X9.42 DHX static keys with interactive protocols and therefore this issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, 3.1.2 and 3.0 are affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-42770
- https://github.com/openssl/security/commit/3da5a516cd2635a320ff748503db2cef7c4b0f02
- https://github.com/openssl/security/commit/3ddbb7ab50bd93dfc59cbe08e269a67605aeebdb
- https://github.com/openssl/security/commit/5f452bba2c681423d8fcffd120a19b757ee42e3c
- https://github.com/openssl/security/commit/7fbfde7677ed8808828bf00ff01c937ca04bdda2
- https://github.com/openssl/security/commit/ca2237ab5615641b662183b077f62c08d75e8070
- https://github.com/openssl/openssl/commit/3da5a516cd2635a320ff748503db2cef7c4b0f02
- https://github.com/openssl/openssl/commit/3ddbb7ab50bd93dfc59cbe08e269a67605aeebdb
- https://github.com/openssl/openssl/commit/5f452bba2c681423d8fcffd120a19b757ee42e3c
- https://github.com/openssl/openssl/commit/7fbfde7677ed8808828bf00ff01c937ca04bdda2
- https://github.com/openssl/openssl/commit/ca2237ab5615641b662183b077f62c08d75e8070
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: When an application drives an AES-OCB context through the public EVP_Cipher() one-shot interface, the application-supplied initialisation vector (IV) is silently discarded.
Impact summary: Every message encrypted under the same key uses the same effective nonce regardless of the IV supplied by the caller, resulting in (key, nonce) reuse and loss of confidentiality. If the same code path is used to compute the authentication tag, the tag depends only on the (key, IV) pair and not on the plaintext or ciphertext, allowing universal forgery of arbitrary ciphertext from a single captured message.
OpenSSL provides two ways to drive a cipher: the documented streaming interface (EVP_CipherUpdate / EVP_CipherFinal_ex) and a lower-level one-shot, EVP_Cipher(), whose documentation explicitly recommends against use by applications in favour of EVP_CipherUpdate() and EVP_CipherFinal_ex(). The OCB provider's streaming handler flushes the application-supplied IV into the OCB context before processing data; the one-shot handler did not. Every call to EVP_Cipher() on an AES-OCB context therefore ran with the all-zero key-derived offset state left by cipher initialisation, regardless of the caller's IV.
If EVP_EncryptFinal_ex() is subsequently used to obtain the authentication tag, the deferred IV setup runs at that point and clears the running checksum that should have been accumulated over the plaintext. The resulting tag is a function of (key, IV) only and verifies against any ciphertext produced under the same (key, IV) pair.
The OpenSSL SSL/TLS implementation is not affected: AES-OCB is not a TLS cipher suite, and libssl does not call EVP_Cipher() in any case. Applications that drive AES-OCB through the documented streaming AEAD API (EVP_CipherUpdate / EVP_CipherFinal_ex) are not affected. Only applications that combine the AES-OCB cipher with the EVP_Cipher() one-shot API are vulnerable.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as AES-OCB is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-45445
- https://github.com/openssl/security/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451
- https://github.com/openssl/security/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7
- https://github.com/openssl/security/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af
- https://github.com/openssl/security/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c
- https://github.com/openssl/security/commit/983d54b5cce8d16147548ed1a37892d1720bbab6
- https://github.com/openssl/openssl/commit/323f0b6e7d530a4cb4336d50c88cb70f3ac2a451
- https://github.com/openssl/openssl/commit/787a6dfba81b7b09c1e05ab31396c0cd7c36b3f7
- https://github.com/openssl/openssl/commit/7ac4715234ee72d9f3c93426a2c08554b5b771af
- https://github.com/openssl/openssl/commit/843c9b94ca9c2ed248bb30127bb4f3d7af0d607c
- https://github.com/openssl/openssl/commit/983d54b5cce8d16147548ed1a37892d1720bbab6
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: The implementations of AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) mishandle the authentication of AAD (Additional Authenticated Data) with an empty ciphertext allowing a forgery of such messages.
Impact summary: An attacker can forge empty messages with arbitrary AAD to the victim's application using these ciphers.
AES-SIV (RFC 5297) and AES-GCM-SIV (RFC 8452) are nonce-misuse-resistant AEAD
modes: they accept a key, nonce, optional AAD (bytes that are authenticated
but not encrypted), and plaintext, and produces ciphertext plus a 16-byte
tag. On decrypt, EVP_DecryptFinal_ex() is documented to return success only
if the tag is verified succesfully.
In OpenSSL's provider implementation of these ciphers, the expected tag is
computed only when decryption function is invoked with non-empty data.
If the caller supplies AAD and then calls EVP_DecryptFinal_ex() without
invocation of the ciphertext update, which can happen when the received
ciphertext length is zero, the tag is never recalculated and still holds its
all-zeros value.
When AES-GCM-SIV is used, an attacker who sends arbitrary AAD, empty ciphertext, and all-zeros tag passes authentication under any key they do not know, single-shot. When AES-SIV is used, for mounting the attack it's necessary for the application to reuse the decryption context without resetting the key.
AES-SIV is implemented since OpenSSL 3.0. AES-GCM-SIV is implemented since OpenSSL 3.2.
No protocols implemented in OpenSSL itself (TLS/CMS/PKCS7/HPKE/QUIC) support either AES-GCM-SIV or AES-SIV. To mount an attack, the applications must implement their own protocol and use the EVP interface. Also they must skip the ciphertext update when a message with an empty ciphertext arrives.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as these algorithms are not FIPS approved and the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-45446
- https://github.com/openssl/security/commit/25b32cd9d41d2bc01b6abc425bb4baf2c2236fdc
- https://github.com/openssl/security/commit/71e2a5d263518cf5866043bd60ee4994d59e53a3
- https://github.com/openssl/security/commit/7fe3f33a3b3a4c487aa4dcdbc87057f66ffd2b85
- https://github.com/openssl/security/commit/daca0f48e4a69a2892a62262bad59e62a8a76598
- https://github.com/openssl/security/commit/eec5e9bf0d867333b8495e456f5235d225798a68
- https://github.com/openssl/openssl/commit/25b32cd9d41d2bc01b6abc425bb4baf2c2236fdc
- https://github.com/openssl/openssl/commit/71e2a5d263518cf5866043bd60ee4994d59e53a3
- https://github.com/openssl/openssl/commit/7fe3f33a3b3a4c487aa4dcdbc87057f66ffd2b85
- https://github.com/openssl/openssl/commit/daca0f48e4a69a2892a62262bad59e62a8a76598
- https://github.com/openssl/openssl/commit/eec5e9bf0d867333b8495e456f5235d225798a68
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: A specially crafted PKCS#7 or S/MIME signed message could trigger a use-after-free during PKCS#7 signature verification.
Impact summary: A use-after-free may result in process crashes, heap corruption, or potentially remote code execution.
When processing a PKCS#7 or S/MIME signed message, if the SignedData digestAlgorithms field is present as an empty ASN.1 SET, OpenSSL may incorrectly free a caller-owned BIO during PKCS7_verify(). A subsequent use of the BIO by the calling application results in a use-after-free condition.
In the common case this occurs when the application later calls BIO_free() on the BIO originally passed to PKCS7_verify(). Depending on allocator behavior and application-specific BIO usage patterns, this may result in a crash or other memory corruption. In some application contexts this may potentially be exploitable for remote code execution.
Applications that process PKCS#7 or S/MIME signed messages using OpenSSL PKCS#7 APIs may be affected. Applications using the CMS APIs for this processing are not affected.
The FIPS modules in 4.0, 3.6, 3.5, 3.4, and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-45447
- https://github.com/openssl/security/commit/3aad5eb7af4de4ee0633c30a8541a54d9bbde63c
- https://github.com/openssl/security/commit/7d4a980c62258c5910cc883936e0c8dbab4d75a8
- https://github.com/openssl/security/commit/9dfd688ad2290fc5075cacbc9bf0c9a93eefed54
- https://github.com/openssl/security/commit/a541ae8bfe849a30cc885e8780715c0f488e496c
- https://github.com/openssl/security/commit/c505d7559da5d5f9f2c3913c6883a5562ce7273e
- https://github.com/openssl/openssl/commit/3aad5eb7af4de4ee0633c30a8541a54d9bbde63c
- https://github.com/openssl/openssl/commit/7d4a980c62258c5910cc883936e0c8dbab4d75a8
- https://github.com/openssl/openssl/commit/9dfd688ad2290fc5075cacbc9bf0c9a93eefed54
- https://github.com/openssl/openssl/commit/a541ae8bfe849a30cc885e8780715c0f488e496c
- https://github.com/openssl/openssl/commit/c505d7559da5d5f9f2c3913c6883a5562ce7273e
- https://openssl-library.org/news/secadv/20260609.txt
- https://access.redhat.com/errata/RHSA-2026:25237
- https://access.redhat.com/errata/RHSA-2026:25239
- https://access.redhat.com/errata/RHSA-2026:26275
- https://access.redhat.com/errata/RHSA-2026:26319
- https://access.redhat.com/errata/RHSA-2026:29197
- https://access.redhat.com/errata/RHSA-2026:34102
- https://access.redhat.com/errata/RHSA-2026:35869
- https://access.redhat.com/errata/RHSA-2026:36215
- https://access.redhat.com/errata/RHSA-2026:36217
- https://access.redhat.com/errata/RHSA-2026:39009
- https://access.redhat.com/errata/RHSA-2026:39012
- https://access.redhat.com/errata/RHSA-2026:39981
- https://access.redhat.com/security/cve/CVE-2026-45447
- https://bugzilla.redhat.com/show_bug.cgi?id=2481898
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-45447.json
- https://access.redhat.com/errata/RHSA-2026:44438
- https://access.redhat.com/errata/RHSA-2026:47735
- https://access.redhat.com/errata/RHSA-2026:47737
- https://access.redhat.com/errata/RHSA-2026:58563
- https://access.redhat.com/errata/RHSA-2026:58981
- https://access.redhat.com/errata/RHSA-2026:59831
- https://access.redhat.com/errata/RHSA-2026:66524
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54872
- https://github.com/openssl/openssl/commit/1a5bee8dc57430a2be69cd1ffe7fec6a62f4f179
- https://github.com/openssl/openssl/commit/3f7e1363dccec6f7732bb9e9fa471bb6e4aa68cb
- https://github.com/openssl/openssl/commit/7d83bc7764999dfd91b83b4f0815b45390422afd
- https://github.com/openssl/openssl/commit/8166827a78aad164a07aa86dea2b425403ced471
- https://openssl-library.org/news/secadv/20260929.txt
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54874
- https://github.com/openssl/openssl/commit/4808b5d64176451f3d93d87d0ac9c81a9b13fb23
- https://github.com/openssl/openssl/commit/7110cb2f75806d0bf809eb2f90790d477900be40
- https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- https://github.com/openssl/openssl/commit/cc0c6710917cd5eec001b297355d2ba723505107
- https://github.com/openssl/openssl/commit/f52ffc11b90737ac89083909618dc2e1f42c561c
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63072
- https://github.com/openssl/openssl/commit/2a3dac874c8057c1f0186849bf1ede1ae7b6b756
- https://github.com/openssl/openssl/commit/87784ad619af36b8807c2044b3940006fccc1e42
- https://github.com/openssl/openssl/commit/9530a5fd1aacaeccdced4478ea2340a480613335
- https://github.com/openssl/openssl/commit/9ec2f6d2ae2bcad907cf7ee38584855bafe4979a
- https://github.com/openssl/openssl/commit/a0c8ec557d9cac078f032d76cdf684fe743eb382
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63074
- https://github.com/openssl/openssl/commit/01e567978a55fba18142a230380c31296049fae7
- https://github.com/openssl/openssl/commit/21a5d9658b0c66daace60e10ea18ff32a448de9f
- https://github.com/openssl/openssl/commit/74ae7f6df47a5767c1010b88c47507dfc5b32c46
- https://github.com/openssl/openssl/commit/75360af9650d4e0c82ba0050c5c9912cd79e54af
- https://github.com/openssl/openssl/commit/f636f9ca0fa1bae5b42f9e787f025c96fb09c43a
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-63076
- https://github.com/openssl/openssl/commit/37882aa2e0256e1072442a8f62f7db45b995c45b
- https://github.com/openssl/openssl/commit/a17cc8d612ecff6d94a9b7ca8b5283ddf5ff570e
- https://github.com/openssl/openssl/commit/a1f348ccb328c3afbd4ba6883f9b7c813c043259
- https://github.com/openssl/openssl/commit/a7af46a92d0ce19a90e669ef56d2576a07924226
- https://github.com/openssl/openssl/commit/cdacfff557389abfa9e4615abded2ec984517d6c
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: A signed integer overflow when sizing the destination buffer for Unicode output in ASN1_mbstring_ncopy() can lead to a heap buffer overflow.
Impact summary: A heap buffer overflow may lead to a crash or possibly attacker controlled code execution or other undefined behaviour.
In ASN1_mbstring_copy() and ASN1_mbstring_ncopy() the destination size for Unicode output is computed in a signed int: by left shift of the input character count for BMPSTRING (UTF-16) and UNIVERSALSTRING (UTF-32), and by summing per-character byte counts for UTF8STRING. The calculation overflows when the input reaches around 2^30 characters. In the worst case (UNIVERSALSTRING at 2^30 characters) the size wraps to zero, OPENSSL_malloc(1) is called, and the subsequent character copy writes several gigabytes past the one-byte allocation.
X.509 certificate processing routes through ASN1_STRING_set_by_NID(), whose DIRSTRING_TYPE mask excludes UNIVERSALSTRING and whose per-NID size limits cap the input length; no network protocol or certificate-handling path in OpenSSL exercises the overflow. Triggering the bug requires an application that calls ASN1_mbstring_copy() or ASN1_mbstring_ncopy() directly, or registers a custom string type via ASN1_STRING_TABLE_add(), with attacker-controlled input on the order of half a gigabyte or more. For these reasons this issue was assigned Low severity.
The FIPS modules in 4.0, 3.6, 3.5, 3.4 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7383
- https://github.com/openssl/security/commit/4f8d2bddaa2c8e06f9c33390ee1717059a6e4be6
- https://github.com/openssl/security/commit/80c15faaf78042bbb8654a0e234c50c381732f74
- https://github.com/openssl/security/commit/bd17511070fb39a67bfa19682affb765e706a974
- https://github.com/openssl/security/commit/c332adaced43bcbb85f97410597e951c11ec3083
- https://github.com/openssl/security/commit/d32350ae8ef7426718f5aa9e383d4b51398ee255
- https://github.com/openssl/openssl/commit/4f8d2bddaa2c8e06f9c33390ee1717059a6e4be6
- https://github.com/openssl/openssl/commit/80c15faaf78042bbb8654a0e234c50c381732f74
- https://github.com/openssl/openssl/commit/bd17511070fb39a67bfa19682affb765e706a974
- https://github.com/openssl/openssl/commit/c332adaced43bcbb85f97410597e951c11ec3083
- https://github.com/openssl/openssl/commit/d32350ae8ef7426718f5aa9e383d4b51398ee255
- https://openssl-library.org/news/secadv/20260609.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-75803
- https://github.com/openssl/openssl/commit/119ab9555dc62275bbd71f6f49529b1a44feba42
- https://github.com/openssl/openssl/commit/3621257986e27e540bf96a11570929a6e5a9e05b
- https://github.com/openssl/openssl/commit/6c7aa6f8f6449b7fe0137ee8be65fcd239bd7d6a
- https://github.com/openssl/openssl/commit/bdeb0cd994d915342787f117ee75044f0dc36f34
- https://github.com/openssl/openssl/commit/bf95f5f772e9362f87b25cfa2f8cb15d984865b9
- https://openssl-library.org/news/secadv/20260825.txt
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-75805
- https://github.com/openssl/openssl/commit/7588db7fef14209c3caa3a101d11a02006b19166
- https://github.com/openssl/openssl/commit/7ca0ccb5172a577e9b87267d77bfe21e5481a5e7
- https://github.com/openssl/openssl/commit/9eb2a8a9b86136cdb39d6d7d50644dd66941cdc3
- https://github.com/openssl/openssl/commit/abf02872a4b71767ecc72293424420f5b009190f
- https://openssl-library.org/news/secadv/20260929.txt
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-75806
- https://github.com/openssl/openssl/commit/04728a289a823e68137f88da016cb9ede307217d
- https://github.com/openssl/openssl/commit/050b275cd671a6eed1d6457642d41a5a77aab972
- https://github.com/openssl/openssl/commit/3a4589d015a9049d47b66f186cf50a8711343a1d
- https://github.com/openssl/openssl/commit/5af82fefbaf2b5fec2fc0e1d87f112844902f01d
- https://openssl-library.org/news/secadv/20260929.txt
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-77696
- https://github.com/openssl/openssl/commit/1c4aed808a7aea32d2d013049c2e0d9fef164fc9
- https://github.com/openssl/openssl/commit/20b20628d39b2dcc4677194bd68c7c060fa598cb
- https://github.com/openssl/openssl/commit/419f5cb519721dceed393dbc524d79e487c72e64
- https://github.com/openssl/openssl/commit/6b90445a56b99a328ac1feba058abf976504f440
- https://openssl-library.org/news/secadv/20260929.txt
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.22-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 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:12 openssl to version 3.0.22-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-84782
- https://github.com/openssl/openssl/commit/906cf0ef1c85ca40ce69163e9086d6d3fe292943
- https://github.com/openssl/openssl/commit/9f6b34422af7eb5dac61322e33dac1ae989fa628
- https://github.com/openssl/openssl/commit/a383dafdd754eb5b22bf45e37e1bff9d07277a58
- https://github.com/openssl/openssl/commit/d951e02ede8f6a6ff8150546db44b34f0518192c
- https://openssl-library.org/news/secadv/20260929.txt
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
A DANE-enabled TLS client may crash by dereferencing a NULL pointer when processing an unusual combination of certificate and TLSA records.
Remediation
There is no fixed version for Debian:12 openssl.
References
low severity
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
- Fixed in: 3.0.20-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Issue summary: When CMS password-based decryption (RFC 3211 / PWRI key unwrap) processes attacker-supplied CMS data, an attacker-chosen stream-mode KEK cipher can trigger a heap out-of-bounds read in kek_unwrap_key().
Impact summary: A heap buffer over-read may trigger a crash which leads to Denial of Service for an application if the input buffer ends at a memory page boundary and the following page is unmapped. There is no information disclosure as the over-read bytes are not revealed to the attacker.
The key unwrapping function performs a check-byte test as specified in the RFC that reads 7 bytes from a heap allocation that is based on the wrapped key length from the message. There is a minimum length check based on the block length of the wrapping cipher. However the cipher is selected from an OID carried in the attacker's PWRI keyEncryptionAlgorithm with no requirement that the cipher be a block cipher. When an attacker selects a stream-mode cipher the guard will be ineffective and the allocated buffer containing the unwrapped key can be too small to fit the check-bytes specified in the RFC and a buffer over-read can happen.
Applications calling CMS_decrypt() or CMS_decrypt_set1_password() (equivalently openssl cms -decrypt -pwri_password ...) on untrusted CMS data are vulnerable to this issue. No password knowledge is required: the over-read happens during the unwrap attempt before any authentication succeeds.
The over-read is limited to a few bytes and is not written to output, so there is no information disclosure. Triggering a crash requires the allocation to border unmapped memory, which is unlikely with the normal allocator.
The FIPS modules are not affected by this issue.
Remediation
Upgrade Debian:12 openssl to version 3.0.20-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-9076
- https://github.com/openssl/security/commit/05b066366842f930fadd9a6e94df98030af431bb
- https://github.com/openssl/security/commit/3d8d5bc1056b2f62da9fede23fedbf47e85187b0
- https://github.com/openssl/security/commit/715349a1d7c6db970e6815dafb90915f07307f98
- https://github.com/openssl/security/commit/77bf00ab13f6ff5e516535432f0328ed70ec0c26
- https://github.com/openssl/security/commit/eecbe330977e8d023aae1ca2d9bdbe983ef3fdc6
- https://github.com/openssl/openssl/commit/05b066366842f930fadd9a6e94df98030af431bb
- https://github.com/openssl/openssl/commit/3d8d5bc1056b2f62da9fede23fedbf47e85187b0
- https://github.com/openssl/openssl/commit/715349a1d7c6db970e6815dafb90915f07307f98
- https://github.com/openssl/openssl/commit/77bf00ab13f6ff5e516535432f0328ed70ec0c26
- https://github.com/openssl/openssl/commit/eecbe330977e8d023aae1ca2d9bdbe983ef3fdc6
- https://openssl-library.org/news/secadv/20260609.txt
low severity
new
- Vulnerable module: openssl
- Introduced through: openssl@3.0.14-1~deb12u2 and openssl/libssl3@3.0.14-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › openssl@3.0.14-1~deb12u2
-
Introduced through: python@3.8-slim › openssl/libssl3@3.0.14-1~deb12u2
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:12 relevant fixed versions and status.
Receiving crafted out-of-sequence DTLS handshake fragments may cause OpenSSL to allocate a full message-length reassembly buffer for each buffered message, so a small amount of wire data consumes a large amount of memory.
Remediation
There is no fixed version for Debian:12 openssl.
References
low severity
- Vulnerable module: pam/libpam-modules
- Introduced through: pam/libpam-modules@1.5.2-6+deb12u1, pam/libpam-modules-bin@1.5.2-6+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › pam/libpam-modules@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-modules-bin@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam-runtime@1.5.2-6+deb12u1
-
Introduced through: python@3.8-slim › pam/libpam0g@1.5.2-6+deb12u1
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:12 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:12 pam.
References
- https://security-tracker.debian.org/tracker/CVE-2026-54411
- https://cwe.mitre.org/data/definitions/208.html
- https://github.com/linux-pam/linux-pam
- https://github.com/linux-pam/linux-pam/blob/master/libpam/include/pam_inline.h
- https://github.com/linux-pam/linux-pam/blob/master/modules/pam_userdb/pam_userdb.c#L327
low severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u1 or higher.
References
low severity
- Vulnerable module: pcre2/libpcre2-8-0
- Introduced through: pcre2/libpcre2-8-0@10.42-1
- Fixed in: 10.42-1+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › pcre2/libpcre2-8-0@10.42-1
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:12 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:12 pcre2 to version 10.42-1+deb12u2 or higher.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-15649
- https://github.com/pmqs/IO-Compress/commit/fd28c1d2374eee9811f6d0c5bddc0957abdf1da8.patch
- https://github.com/pmqs/IO-Compress/issues/65
- https://metacpan.org/release/PMQS/IO-Compress-2.215/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/1
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u3
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 relevant fixed versions and status.
Perl threads have a working directory race condition where file operations may target unintended paths.
If a directory handle is open at thread creation, the process-wide current working directory is temporarily changed in order to clone that handle for the new thread, which is visible from any third (or more) thread already running.
This may lead to unintended operations such as loading code or accessing files from unexpected locations, which a local attacker may be able to exploit.
The bug was introduced in commit 11a11ecf4bea72b17d250cfb43c897be1341861e and released in Perl version 5.13.6
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u3 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-40909
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098226
- https://github.com/Perl/perl5/commit/11a11ecf4bea72b17d250cfb43c897be1341861e
- https://github.com/Perl/perl5/commit/918bfff86ca8d6d4e4ec5b30994451e0bd74aba9.patch
- https://github.com/Perl/perl5/issues/10387
- https://github.com/Perl/perl5/issues/23010
- https://perldoc.perl.org/5.14.0/perl5136delta#Directory-handles-not-copied-to-threads
- https://www.openwall.com/lists/oss-security/2025/05/22/2
- http://www.openwall.com/lists/oss-security/2025/05/23/1
- http://www.openwall.com/lists/oss-security/2025/05/30/4
- http://www.openwall.com/lists/oss-security/2025/06/02/2
- http://www.openwall.com/lists/oss-security/2025/06/02/5
- http://www.openwall.com/lists/oss-security/2025/06/02/6
- http://www.openwall.com/lists/oss-security/2025/06/02/7
- http://www.openwall.com/lists/oss-security/2025/06/03/1
- http://seclists.org/fulldisclosure/2025/Sep/53
- http://seclists.org/fulldisclosure/2025/Sep/54
- http://seclists.org/fulldisclosure/2025/Sep/55
- https://lists.debian.org/debian-lts-announce/2026/04/msg00018.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-12087
- https://github.com/Perl/perl5/commit/de19a0b0ad1900fef976c5c1400bd8f11ec6c6cb.patch
- https://metacpan.org/release/PEVANS/Socket-2.041/changes
- http://www.openwall.com/lists/oss-security/2026/06/15/10
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-15534
- https://github.com/Perl/perl5/commit/54cf3d44cbbedd17d774e9a37921963e8fd5d0cb.patch
- https://github.com/Perl/perl5/commit/568e6fd238867bb9e99fa3f47cba3169009239e0.patch
- http://www.openwall.com/lists/oss-security/2026/08/09/12
- http://www.openwall.com/lists/oss-security/2026/08/09/13
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-19487
- https://github.com/Perl/perl5/commit/1a21abacaf6f684928bae8baaa153733c8c238eb.patch
- http://www.openwall.com/lists/oss-security/2026/08/13/8
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
- https://github.com/Perl/perl5/issues/22892
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-48959
- https://github.com/pmqs/IO-Compress/commit/68db44076f4c1a86a2ffe53a958eac6cabaf72e2.patch
- https://metacpan.org/release/PMQS/IO-Compress-2.220/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/2
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-48962
- https://github.com/pmqs/IO-Compress/commit/f2db247bf90d4cc7ee2710be384946081f3b4610.patch
- https://metacpan.org/release/PMQS/IO-Compress-2.220/changes
- http://www.openwall.com/lists/oss-security/2026/05/27/4
- https://access.redhat.com/errata/RHSA-2026:29182
- https://access.redhat.com/errata/RHSA-2026:29210
- https://access.redhat.com/errata/RHSA-2026:29867
- https://access.redhat.com/errata/RHSA-2026:29941
- https://access.redhat.com/errata/RHSA-2026:30085
- https://access.redhat.com/errata/RHSA-2026:30086
- https://access.redhat.com/errata/RHSA-2026:30115
- https://access.redhat.com/errata/RHSA-2026:30843
- https://access.redhat.com/errata/RHSA-2026:30851
- https://access.redhat.com/errata/RHSA-2026:30858
- https://access.redhat.com/errata/RHSA-2026:30859
- https://access.redhat.com/errata/RHSA-2026:30860
- https://access.redhat.com/security/cve/CVE-2026-48962
- https://bugzilla.redhat.com/show_bug.cgi?id=2481767
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-48962.json
- https://access.redhat.com/errata/RHSA-2026:50262
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7010
- https://github.com/Perl-Toolchain-Gang/HTTP-Tiny/commit/d73c7651e82ace02693842df55928b6c3ae7c38d.patch
- https://metacpan.org/release/HAARG/HTTP-Tiny-0.093-TRIAL/changes
- http://www.openwall.com/lists/oss-security/2026/05/11/17
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u4
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl to version 5.36.0-7+deb12u4 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-7017
- https://github.com/Perl-Toolchain-Gang/HTTP-Tiny/commit/84984ef3930ddd4afcf5eb83b40d3cee200739c3.patch
- https://github.com/Perl-Toolchain-Gang/HTTP-Tiny/commit/8f32ca89e21c3ad0422adc698fa6ad17a193f55f.patch
- https://github.com/Perl-Toolchain-Gang/HTTP-Tiny/commit/e7a03aedf2395158f2b0d3bad2df943349227bb3.patch
- https://github.com/Perl-Toolchain-Gang/HTTP-Tiny/pull/36
- https://metacpan.org/release/HAARG/HTTP-Tiny-0.095-TRIAL/changes
- http://www.openwall.com/lists/oss-security/2026/07/07/13
- https://cert-portal.siemens.com/productcert/html/ssa-457936.html
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 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:12 perl.
References
- https://security-tracker.debian.org/tracker/CVE-2026-82560
- https://github.com/rra/podlators/commit/70510174f69eb54aa6d617bde4e1402cd9b7c61f.patch
- https://metacpan.org/release/RRA/podlators-v6.1.0/source/lib/Pod/Text.pm#L245-261
- https://metacpan.org/release/RRA/podlators-v6.1.1/changes
- http://www.openwall.com/lists/oss-security/2026/09/19/6
low severity
- Vulnerable module: perl/perl-base
- Introduced through: perl/perl-base@5.36.0-7+deb12u1
- Fixed in: 5.36.0-7+deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › perl/perl-base@5.36.0-7+deb12u1
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:12 relevant fixed versions and status.
A heap buffer overflow vulnerability was discovered in Perl.
Release branches 5.34, 5.36, 5.38 and 5.40 are affected, including development versions from 5.33.1 through 5.41.10.
When there are non-ASCII bytes in the left-hand-side of the tr operator, S_do_trans_invmap can overflow the destination pointer d.
$ perl -e '$_ = "\x{FF}" x 1000000; tr/\xFF/\x{100}/;' Segmentation fault (core dumped)
It is believed that this vulnerability can enable Denial of Service and possibly Code Execution attacks on platforms that lack sufficient defenses.
Remediation
Upgrade Debian:12 perl to version 5.36.0-7+deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2024-56406
- https://github.com/Perl/perl5/commit/87f42aa0e0096e9a346c9672aa3a0bd3bef8c1dd.patch
- https://metacpan.org/release/SHAY/perl-5.38.4/changes
- https://metacpan.org/release/SHAY/perl-5.40.2/changes
- http://www.openwall.com/lists/oss-security/2025/04/13/3
- http://www.openwall.com/lists/oss-security/2025/04/13/4
- http://www.openwall.com/lists/oss-security/2025/04/13/5
low severity
- Vulnerable module: sed
- Introduced through: sed@4.9-1
- Fixed in: 4.9-1+deb12u1
Detailed paths
-
Introduced through: python@3.8-slim › sed@4.9-1
NVD Description
Note: Versions mentioned in the description apply only to the upstream sed package and not the sed package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
When sed is invoked with both -i (in-place edit) and --follow-symlinks, the function open_next_file() performs two separate, non-atomic filesystem operations on the same path:
- resolves symlink to its target and stores the resolved path for determining when output is written,
- opens the original symlink path (not the resolved one) to read the file. Between these two calls there is a race window. If an attacker atomically replaces the symlink with a different target during that window, sed will: read content from the new (attacker-chosen) symlink target and write the processed result to the path recorded in step 1. This can lead to arbitrary file overwrite with attacker-controlled content in the context of the sed process.
This issue was fixed in version 4.10.
Remediation
Upgrade Debian:12 sed to version 4.9-1+deb12u1 or higher.
References
low severity
- Vulnerable module: shadow/login
- Introduced through: shadow/login@1:4.13+dfsg1-1+b1 and shadow/passwd@1:4.13+dfsg1-1+b1
Detailed paths
-
Introduced through: python@3.8-slim › shadow/login@1:4.13+dfsg1-1+b1
-
Introduced through: python@3.8-slim › shadow/passwd@1:4.13+dfsg1-1+b1
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:12 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:12 shadow.
References
- https://security-tracker.debian.org/tracker/CVE-2024-56433
- https://github.com/shadow-maint/shadow/blob/e2512d5741d4a44bdd81a8c2d0029b6222728cf0/etc/login.defs#L238-L241
- https://github.com/shadow-maint/shadow/issues/1157
- https://github.com/shadow-maint/shadow/releases/tag/4.4
- https://cert-portal.siemens.com/productcert/html/ssa-398330.html
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 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:12 sqlite3.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 relevant fixed versions and status.
An integer overflow exists in the FTS5 https://sqlite.org/fts5.html extension. It occurs when the size of an array of tombstone pointers is calculated and truncated into a 32-bit integer. A pointer to partially controlled data can then be written out of bounds.
Remediation
There is no fixed version for Debian:12 sqlite3.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 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:12 sqlite3.
References
low severity
- Vulnerable module: sqlite3/libsqlite3-0
- Introduced through: sqlite3/libsqlite3-0@3.40.1-2
Detailed paths
-
Introduced through: python@3.8-slim › sqlite3/libsqlite3-0@3.40.1-2
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:12 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:12 sqlite3.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 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:12 systemd.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 relevant fixed versions and status.
systemd, a system and service manager, (as PID 1) hits an assert and freezes execution when an unprivileged IPC API call is made with spurious data. On version v249 and older the effect is not an assert, but stack overwriting, with the attacker controlled content. From version v250 and newer this is not possible as the safety check causes an assert instead. This IPC call was added in v239, so versions older than that are not affected. Versions 260-rc1, 259.2, 258.5, and 257.11 contain patches. No known workarounds are available.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2026-29111
- https://github.com/systemd/systemd/commit/1d22f706bd04f45f8422e17fbde3f56ece17758a
- https://github.com/systemd/systemd/commit/20021e7686426052e3a7505425d7e12085feb2a6
- https://github.com/systemd/systemd/commit/21167006574d6b83813c7596759b474f56562412
- https://github.com/systemd/systemd/commit/3cee294fe8cf4fa0eff933ab21416d099942cabd
- https://github.com/systemd/systemd/commit/42aee39107fbdd7db1ccd402a2151822b2805e9f
- https://github.com/systemd/systemd/commit/54588d2dedff54bfb6036670820650e4ea74628f
- https://github.com/systemd/systemd/commit/7ac3220213690e8a8d6d2a6e81e43bd1dce01d69
- https://github.com/systemd/systemd/commit/80acea4ef80a4bb78560ed970c34952299b890d6
- https://github.com/systemd/systemd/commit/b5fd14693057e5f2c9b4a49603be64ec3608ff6c
- https://github.com/systemd/systemd/commit/efa6ba2ab625aaa160ac435a09e6482fc63bdbe8
- https://github.com/systemd/systemd/security/advisories/GHSA-gx6q-6f99-m764
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 relevant fixed versions and status.
In udev in systemd before 260, local root execution can occur via malicious hardware devices and unsanitized kernel output.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
low severity
- Vulnerable module: systemd/libsystemd0
- Introduced through: systemd/libsystemd0@252.30-1~deb12u2 and systemd/libudev1@252.30-1~deb12u2
- Fixed in: 252.39-1~deb12u2
Detailed paths
-
Introduced through: python@3.8-slim › systemd/libsystemd0@252.30-1~deb12u2
-
Introduced through: python@3.8-slim › systemd/libudev1@252.30-1~deb12u2
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:12 relevant fixed versions and status.
In nspawn in systemd 233 through 259 before 260, an escape-to-host action can occur via a crafted optional config file.
Remediation
Upgrade Debian:12 systemd to version 252.39-1~deb12u2 or higher.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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
There is no fixed version for Debian:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53615
- https://github.com/util-linux/util-linux/commit/05c2dbadf34cc74192287f377904afaaf4061623
- https://github.com/util-linux/util-linux/commit/a2d858176b609ab5b8535021a3af9cd302d23d31
- https://github.com/util-linux/util-linux/commit/e9d544d013267ea86b70ee8ff78abd280e6641af
- https://github.com/util-linux/util-linux/releases/tag/v2.41.4
- https://github.com/util-linux/util-linux/security/advisories/GHSA-h4rw-gv36-wmp5
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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
There is no fixed version for Debian:12 util-linux.
References
low severity
- Vulnerable module: util-linux
- Introduced through: util-linux@2.38.1-5+deb12u1, util-linux/bsdutils@1:2.38.1-5+deb12u1 and others
Detailed paths
-
Introduced through: python@3.8-slim › util-linux@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/bsdutils@1:2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libblkid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libmount1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libsmartcols1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/libuuid1@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/mount@2.38.1-5+deb12u1
-
Introduced through: python@3.8-slim › util-linux/util-linux-extra@2.38.1-5+deb12u1
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:12 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
There is no fixed version for Debian:12 util-linux.
References
- https://security-tracker.debian.org/tracker/CVE-2026-53613
- https://github.com/util-linux/util-linux/commit/0b010025a0e429bc80355c94db86a843395d49e2
- https://github.com/util-linux/util-linux/commit/0d3d55975aa3492c62fd345eac38f41cd166c0b0
- https://github.com/util-linux/util-linux/commit/2c773f336134acf016e639abb6f12ba7341fe4b8
- https://github.com/util-linux/util-linux/commit/39fef62bf3226abb6bb018fa8750afa0327e84b4
- https://github.com/util-linux/util-linux/commit/472cc3fb2d4d47cca7aab2e0b59eb3fb8a9359ec
- https://github.com/util-linux/util-linux/commit/646fb66603d10a7ac337e14f566f1af48e3107c9
- https://github.com/util-linux/util-linux/commit/708d1b3c51932dc5ba8082c7368187715e6a8d78
- https://github.com/util-linux/util-linux/commit/78a860982e036f38fe9c0b3344998df5ac2c2ff5
- https://github.com/util-linux/util-linux/commit/85d16b341f7232c9dbb4884b632e1e956584bee9
- https://github.com/util-linux/util-linux/commit/a9508d216eb8977979102782672e0470cc9bf2a2
- https://github.com/util-linux/util-linux/releases/tag/v2.41.5
- https://github.com/util-linux/util-linux/releases/tag/v2.42.2
- https://github.com/util-linux/util-linux/releases/tag/v2.42.4
- https://github.com/util-linux/util-linux/security/advisories/GHSA-8gj5-72r3-428g
low severity
- Vulnerable module: xz-utils/liblzma5
- Introduced through: xz-utils/liblzma5@5.4.1-0.2
- Fixed in: 5.4.1-1
Detailed paths
-
Introduced through: python@3.8-slim › xz-utils/liblzma5@5.4.1-0.2
NVD Description
Note: Versions mentioned in the description apply only to the upstream xz-utils package and not the xz-utils package as distributed by Debian.
See How to fix? for Debian:12 relevant fixed versions and status.
XZ Utils provide a general-purpose data-compression library plus command-line tools. In XZ Utils 5.3.3alpha to 5.8.0, the multithreaded .xz decoder in liblzma has a bug where invalid input can at least result in a crash. The effects include heap use after free and writing to an address based on the null pointer plus an offset. Applications and libraries that use the lzma_stream_decoder_mt function are affected. The bug has been fixed in XZ Utils 5.8.1, and the fix has been committed to the v5.4, v5.6, v5.8, and master branches in the xz Git repository. No new release packages will be made from the old stable branches, but a standalone patch is available that applies to all affected releases.
Remediation
Upgrade Debian:12 xz-utils to version 5.4.1-1 or higher.
References
- https://security-tracker.debian.org/tracker/CVE-2025-31115
- https://github.com/tukaani-project/xz/commit/d5a2ffe41bb77b918a8c96084885d4dbe4bf6480
- https://github.com/tukaani-project/xz/security/advisories/GHSA-6cc8-p5mm-29w2
- https://tukaani.org/xz/xz-cve-2025-31115.patch
- http://www.openwall.com/lists/oss-security/2025/04/03/1
- http://www.openwall.com/lists/oss-security/2025/04/03/2
- http://www.openwall.com/lists/oss-security/2025/04/03/3
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html