VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

cups: vulnerability history, versions and safety

cups is a package in the Debian ecosystem. Vulert records 221 vulnerabilities for it across 35 releases, from Nov -0001 to Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
221 vulnerabilities recorded U221
i
12 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
8 in the last 12 months

Most recent disclosure 25 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all cups vulnerabilities

Vulert verdict on cups i

Updated on 23 Oct 2026

Careful: 12 of the 221 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 221 vulnerabilities on record across 2026 years, 8 in the last year.

What to do: Plan around the 12 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 221 over 2026 years · 8 in the last year i
  • Latest disclosure 25 Apr 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 12 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for cups, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 35 of 35 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 2
  • 2002 14
  • 2003 6
  • 2004 4
  • 2005 40
  • 2007 18
  • 2008 26
  • 2009 14
  • 2010 16
  • 2011 4
  • 2012 2
  • 2014 18
  • 2015 10
  • 2018 9
  • 2019 10
  • 2020 4
  • 2021 2
  • 2022 1
  • 2023 5
  • 2024 3
  • 2025 5
  • 2026 8

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 8 of the 221 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for cups

The 5 most severe of 221 vulnerabilities recorded for this package

Search all 221 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Case-sensitive Location Directive Bypass in CUPS 9.8 critical 1.1.20final+rc1-1 31 Dec 2004
CUPS Memory Allocation Vulnerability - CVE-2010-2941: Denial of Service and Potential Code Execution 9.8 critical 1.4.4-7 05 Nov 2010
CUPS AppArmor Profile Vulnerability - Escape Confinement Risk 8.8 high 2.2.8-5 10 Aug 2018
CVE-2014-8166: Arbitrary Code Execution in CUPS 8.8 high No fix published 12 Jan 2018
CUPS Command Execution Vulnerability in Google Chrome OS - CVE-2017-15400 7.8 high 2.2.3-2 07 Feb 2018

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About cups

Is cups safe to use?

Vulert records 221 vulnerabilities for cups in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 221 not yet rated. 12 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does cups have?

221 vulnerabilities are recorded for cups in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 221 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new cups vulnerabilities disclosed?

8 vulnerabilities were recorded for cups in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of cups are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor cups for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the cups version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.