Vulnerability Database · OSS-Fuzz · Package report

cups: vulnerability history, versions and safety

cups is a package in the OSS-Fuzz ecosystem. Vulert records 8 vulnerabilities for it across 4 affected ranges, from Aug 2024 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
8 vulnerabilities recorded H2 M6
i
8 with no fix published

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

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

Most recent disclosure 10 Apr 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on cups i

Updated on 23 Oct 2026

Careful: 8 of the 8 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each.

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

What to do: Plan around the 8 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 8 over 1 year · 2 in the last year i
  • Latest disclosure 10 Apr 2026 i
  • Highest CVSS n/a i
  • With no published fix 8 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from c0e2e975462b3890ad3d426942a9000987a2bdb8 onwards, no fix published yet 3
from 6e4a2c699948b5454a2c58b72aadb9d25a3b9353 onwards, no fix published yet 3
from 899362980fe53317fa5931f01b67f45d9b240137 onwards, no fix published yet 1
from 360ccf5e5922f25d4a35f6adba615aa2f5eceac4 onwards, no fix published yet 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 3
  • 2025 3
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for cups

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →

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 8 vulnerabilities for cups in OSS-Fuzz: 0 critical, 2 high, 6 medium and 0 low. 8 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does cups have?

8 vulnerabilities are recorded for cups in the OSS-Fuzz ecosystem: 0 critical, 2 high, 6 medium and 0 low. 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?

2 vulnerabilities were recorded for cups in the last 12 months, and the oldest entry in this database dates to 16 Aug 2024. 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.