CVE coverage

Debian 11 CVE tracker

Noxen pulls Debian 11 (Bullseye) CVE data from OSV.dev's Debian ecosystem feed, which mirrors the Debian Security Tracker. Bullseye is in the Debian LTS phase (maintained by Freexian) through August 2026, so security backports still land — Noxen surfaces them with exact fix versions and matches against the installed source package.

Live

Headline numbers

  • Total CVE records (all distros)Loading…
  • Last buildLoading…
  • OSV records (Debian + others)Loading…
  • NVD records (cross-platform)Loading…

How matching works

What Noxen does for a Debian 11 host

  1. Reads /etc/os-release over SSH to confirm the host is on Debian 11.
  2. Reads the dpkg package list — every binary package, plus its corresponding source package via dpkg-query --showformat='${Source}'.
  3. Filters the local feed cache to OSV records tagged with ecosystem Debian:11.
  4. For each record, compares your installed version against the OSV-published fix version using the Debian/Ubuntu version-comparison rules (epoch, upstream, debian-revision).
  5. Emits a finding only when the installed version is older than the fix. Where Ubuntu Pro / ESM-only fixes apply, they are flagged separately.

Live listings

Top recent critical CVEs (Debian 11 / Debian ecosystem)

Most-recently-published critical CVEs in the Debian 11 / Debian ecosystem. Auto-deduped to one row per CVE ID. Snapshot baked at ; live re-fetch on page load.

CVESev.CVSSSummaryPackageFix inPublished
DEBIAN-CVE-2026-100075critical9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/srpt: Fix srpt_alloc_rw_ctxs() unwind counters When srpt_alloc_rw_ctxs() fails partway through a multi-buffer indirect descriptor, the unwind path destroys RDMA contlinux—
DEBIAN-CVE-2026-92288critical9.1Lemonldap::NG::Portal versions from 2.20.0 before 2.21.6, from 2.22.0 before 2.23.4 for Perl allow unauthenticated OAuth2 token introspection because checkEndPointAuthenticationCredentials does not verify the client secret of a public Relyilemonldap-ng—
DEBIAN-CVE-2026-97413critical9.8In the Linux kernel, the following vulnerability has been resolved: RDMA/rtrs-srv: Fix integer underflow in process_read and process_write usr_len is read from a network-supplied message field (le16_to_cpu) and used to compute data_len = linux—
DEBIAN-CVE-2026-93228critical9.1In the Linux kernel, the following vulnerability has been resolved: svcrdma: Reject Write/Reply chunks with segcount 0 A peer can send a Write or Reply chunk whose segcount field is zero. xdr_check_write_chunk() only rejects segcount > rclinux—
DEBIAN-CVE-2026-93207critical9.8In the Linux kernel, the following vulnerability has been resolved: SUNRPC: Zero rpc_gss_wire_cred at svcauth_gss_decode_credbody() entry svcauth_gss_decode_credbody() writes the caller's rpc_gss_wire_cred field by field and assigns gc_ctlinux—
DEBIAN-CVE-2026-96276critical9.8If a malicious SDK container declares an extension point with a crafted `directory` path, and a developer runs `flatpak build-init --writable-sdk --sdk-extension` with that SDK, attacker-chosen files could be written outside the working dirflatpak—
DEBIAN-CVE-2026-86246critical9.1Initialization of a resource with an insecure default vulnerability in Apache Tomcat Native enabled insecure options by default including ALLOW_CLIENT_RENEGOTIATION, NO_EXTENDED_MASTER_SECRET, IGNORE_UNEXPECTED_EOF and ALLOW_NO_DHE_KEX. tomcat-native—
DEBIAN-CVE-2026-86350critical9.1Inconsistent interpretation of HTTP/2 requests ('HTTP Request/Response smuggling') vulnerability in Apache Tomcat caused by a regression in fix for CVE-2026-41293 can trigger request header mix-up. This issue affects Apache Tomcat: from tomcat10—

Top recent high-severity CVEs (Debian 11 / Debian ecosystem)

CVESev.CVSSSummaryPackageFix inPublished
DEBIAN-CVE-2026-100700high7.5node-nodemailer—
DEBIAN-CVE-2026-100697high8.6adminer—
DEBIAN-CVE-2026-100693high8.4hugo—
DEBIAN-CVE-2026-100692high7.5hugo—
DEBIAN-CVE-2026-100690high7.5hugo—
DEBIAN-CVE-2026-100666high7.3netty—
DEBIAN-CVE-2026-100657high7.5netty—
DEBIAN-CVE-2026-100656high7.5netty—

New to severity terminology? CVE, CVSS, CWE, CPE explained.

Notable

Recent CVEs Debian 11 operators should know.

FAQ

Frequently asked about Debian 11 CVEs

Is Debian 11 still supported in 2026?

Yes — Debian 11 entered LTS in August 2024 (when regular Security Team support ended) and continues through August 2026 under Freexian's volunteer LTS programme. Paid ELTS coverage extends further. Backports are released for the same source packages the Security Tracker covers.

How do I check Debian 11 CVEs on a running host?

For a quick count: apt list --upgradable 2>/dev/null | grep -ci security. For a per-CVE breakdown with fix versions, Noxen reads dpkg over SSH and matches installed source-package versions against the OSV Debian:11 ecosystem feed.

What's the practical difference between Debian 11 and 12 for CVE coverage?

Same data source (Debian Security Tracker, mirrored through OSV). The difference is the package version set and what's been backported. A CVE fixed upstream in openssl 3.2 gets a separate Bullseye backport into the Bullseye-shipped 1.1.1 series and a Bookworm backport into 3.0. Noxen matches against the right per-release fix version automatically.

Scan a Debian 11 fleet with Noxen

Add your Debian 11 hosts via your existing ~/.ssh/config; Noxen reads dpkg state and matches against the live signed feed. No agent, no SaaS round-trip. $12/month, or $120/year.

← back to the CVE dashboard   Debian 12 →   AlmaLinux 9 →