Patch vulnerabilitiesRanked by how likely they are to be used.

Product12 versions
The short answer

Patch is made by Gnu. We track 13 published vulnerabilities in it, across 12 versions. None of them is on the list of flaws known to be exploited today. If you run Patch, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Patch vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Patch's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Patch flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 11%

    Directory traversal vulnerability in GNU patch versions which support Git-style patching before 2.7.3 allows remote attackers to write to arbitrary files with the permissions of the target user via a ..

    CVSS7.5Published25 Aug 2017
  2. 8.4%

    An issue was discovered in GNU patch through 2.7.6.

    CVSS7.5Published13 Feb 2018
  3. 8.2%

    A double free exists in the another_hunk function in pch.c in GNU patch through 2.7.6.

    CVSS7.5Published13 Feb 2018
  4. 6.1%

    GNU patch 2.7.1 allows remote attackers to write to arbitrary files via a symlink attack in a patch file.

    CVSS4.3Published21 Jan 2015
  5. 5.3%

    GNU Patch version 2.7.6 contains an input validation vulnerability when processing patch files, specifically the EDITOR_PROGRAM invocation (using ed) can result in code execution.

    CVSS7.8Published6 Apr 2018
  6. 4.5%

    GNU patch through 2.7.6 is vulnerable to OS shell command injection that can be exploited by opening a crafted patch file that contains an ed style diff payload with shell metacharacters.

    CVSS7.8Published26 Jul 2019
  7. 3.9%

    In GNU patch through 2.7.6, the following of symlinks is mishandled in certain cases other than input files.

    CVSS5.9Published17 Jul 2019
  8. 3.3%

    A Directory Traversal vulnerability exists in the GNU patch before 2.7.4.

    CVSS7.5Published25 Nov 2019
  9. 2.7%

    do_ed_script in pch.c in GNU patch through 2.7.6 does not block strings beginning with a !

    CVSS7.8Published16 Aug 2019
  10. 2.4%

    GNU patch 2.7.2 and earlier allows remote attackers to cause a denial of service (memory consumption and segmentation fault) via a crafted diff file.

    CVSS5.5Published25 Aug 2017
EdgeProtect

Running Patch? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 13 published vulnerabilities listed under the name Patch, across 12 versions.

None of Patch's vulnerabilities is on the list of flaws known to be exploited today.

Create a EdgeProtect account and track Patch. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.