VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

patch: vulnerability history, versions and safety

patch is a package in the Debian ecosystem. Vulert records 23 vulnerabilities for it across 3 releases, from Mar 2011 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
23 vulnerabilities recorded U23
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 09 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all patch vulnerabilities

Vulert verdict on patch i

Updated on 23 Oct 2026

Careful: 8 of the 23 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 23 vulnerabilities on record across 15 years, 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 23 over 15 years · 2 in the last year i
  • Latest disclosure 09 Jul 2026 i
  • Highest CVSS 7.8 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

Every version Vulert holds for patch, 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.

i
Version Vulert vulnerabilities Fix published Details
2.8-2 U8 No Details →
2.8-1 U8 No Details →
2.7.6-7 U8 No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2011 2
  • 2015 2
  • 2017 4
  • 2018 6
  • 2019 5
  • 2021 2
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for patch

The 5 most severe of 23 vulnerabilities recorded for this package

Search all 23 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Remote Command Execution Vulnerability in Patch Package 7.8 high 2.5-1 05 Feb 2018
Directory Traversal Vulnerability in GNU Patch Package 7.5 high 2.7.3-1 25 Aug 2017
Directory Traversal Vulnerability in GNU Patch: CVE-2015-1396 7.5 high 2.7.3-1 25 Nov 2019
NULL Pointer Dereference Vulnerability in GNU Patch Package 5.5 medium No fix published 09 Jul 2026
Invalid Pointer Vulnerability in GNU patch 5.5 medium No fix published 22 Dec 2021

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 patch

Is patch safe to use?

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

How many vulnerabilities does patch have?

23 vulnerabilities are recorded for patch in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 23 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 patch vulnerabilities disclosed?

2 vulnerabilities were recorded for patch in the last 12 months, and the oldest entry in this database dates to 11 Mar 2011. 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 patch 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 patch for upcoming vulnerabilities?

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