VulertSecurity VulertSecurity

Vulnerability Database · Go · Package report

github.com/evanphx/json-patch: vulnerability history, versions and safety

github.com/evanphx/json-patch is a package in the Go ecosystem. Vulert records 2 vulnerabilities for it across 120 releases, from Apr 2021 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded H1 U1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all github.com/evanphx/json-patch vulnerabilities

Vulert verdict on github.com/evanphx/json-patch v0.5.2 i

Updated on 23 Oct 2026

Action needed: v0.5.2 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 64/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Widely used
  • Community Quiet

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release v0.5.2 — affected i
  • Vulnerabilities on record 2 over 1 year · 0 in the last year i
  • Latest disclosure 13 May 2022 i
  • Highest CVSS 7.7 i
  • With no published fix 0 i
  • Stars 1,232 i
  • OpenSSF scorecard 3/10 i
  • Last release 69 months ago i
  • Licence BSD-3-Clause i

Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.

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 tracks for github.com/evanphx/json-patch, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
v0.0.0-20250128174352-84a4bb100ade 28 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20250128174352-84a4bb100ade+incompatible 28 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v4.13.0+incompatible 28 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v5.9.11+incompatible 28 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20250128150130-7a7a88a24da9+incompatible 28 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20250127174627-bd18525ff3c7+incompatible 27 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v5.9.10+incompatible 27 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20250127174255-0a3482b56b0c+incompatible 27 Jan 2025 H1 U1 BSD-3-Clause Yes Details →
v5.9.1-0.20240617005152-a1282d4524d4+incompatible 17 Jun 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240609165810-106306d7fea7+incompatible 09 Jun 2024 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20240304175850-e7cfbbbcc6e3 04 Mar 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240304175850-e7cfbbbcc6e3+incompatible 04 Mar 2024 H1 U1 BSD-3-Clause Yes Details →
v5.9.1-0.20240304175850-e7cfbbbcc6e3+incompatible 04 Mar 2024 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20240128001059-b7a4e4a87a35 28 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240128001059-b7a4e4a87a35+incompatible 28 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v5.9.0+incompatible 28 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240127225823-009bc564fa61+incompatible 27 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20240116233555-b82b685c982b 16 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240116233555-b82b685c982b+incompatible 16 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v5.8.1+incompatible 16 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20240112230335-05c952675fb5 12 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20240112230335-05c952675fb5 12 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240112230335-05c952675fb5+incompatible 12 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v5.8.0+incompatible 12 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240112021028-a9c085a75a55+incompatible 12 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20240112015321-3da7b272ecf9+incompatible 12 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v5.7.1-0.20240111215205-f72a4640c1fb+incompatible 11 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v5.7.1-0.20240111215157-738124dc50b9+incompatible 11 Jan 2024 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20231218002242-3ee20a4f4155+incompatible 18 Dec 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20231211005710-e1550af71bf1+incompatible 11 Dec 2023 H1 U1 BSD-3-Clause Yes Details →
v5.7.1-0.20231211005710-e1550af71bf1+incompatible 11 Dec 2023 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20230911212826-dc808d1b15ce 11 Sep 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230911212826-dc808d1b15ce+incompatible 11 Sep 2023 H1 U1 BSD-3-Clause Yes Details →
v5.7.0+incompatible 11 Sep 2023 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20230911175755-13264185e8b8 11 Sep 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230911175755-13264185e8b8+incompatible 11 Sep 2023 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20230810201007-08317d1eab77 10 Aug 2023 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20230810201007-08317d1eab77 10 Aug 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230810201007-08317d1eab77+incompatible 10 Aug 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230810200945-78844ea5152e+incompatible 10 Aug 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230808094219-0d1d2a12fd1b+incompatible 08 Aug 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230803123945-a11f4f47e5be+incompatible 03 Aug 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230329190351-dd9b733cf6fc+incompatible 29 Mar 2023 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20230114013955-b2e4d76267a9 14 Jan 2023 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20230114013955-b2e4d76267a9 14 Jan 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230114013955-b2e4d76267a9+incompatible 14 Jan 2023 H1 U1 BSD-3-Clause Yes Details →
v5.6.1-0.20230114013955-b2e4d76267a9+incompatible 14 Jan 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20230114013817-a126b2c1d217+incompatible 14 Jan 2023 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20221123132823-6dc810981054+incompatible 23 Nov 2022 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20220218214202-38b1cb8e38b3+incompatible 18 Feb 2022 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20220202153745-b65b5a46d932+incompatible 02 Feb 2022 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20211215012201-6a7ad8a3ea21+incompatible 15 Dec 2021 H1 U1 BSD-3-Clause Yes Details →
v5.6.1-0.20211215012201-6a7ad8a3ea21+incompatible 15 Dec 2021 H1 U1 BSD-3-Clause Yes Details →
v4.12.1-0.20211209174738-f6d37ce5e82a+incompatible 09 Dec 2021 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20211021164042-50fdc0b4c9ab 21 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20211021164042-50fdc0b4c9ab 21 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v4.12.0+incompatible 21 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20211020184723-5561fe05a1ec 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20211020184723-5561fe05a1ec 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.1-0.20211020184723-5561fe05a1ec+incompatible 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v5.6.0+incompatible 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20211020174503-df14171284c7 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.1-0.20211020174503-df14171284c7+incompatible 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v5.5.1-0.20211020174503-df14171284c7+incompatible 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.1-0.20211020174350-556cb6472883+incompatible 20 Oct 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.1-0.20210915083147-71ddd89ec052+incompatible 15 Sep 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.1-0.20210708113300-19e83eee5ca0+incompatible 08 Jul 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.1-0.20210708113136-3dcaf12ac696+incompatible 08 Jul 2021 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20210604045104-3c3c85ec60c9 04 Jun 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210604045104-3c3c85ec60c9 04 Jun 2021 H1 U1 BSD-3-Clause Yes Details →
v4.11.0+incompatible 04 Jun 2021 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20210601025549-3e2cfc05e32a 01 Jun 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210601025549-3e2cfc05e32a 01 Jun 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210531235754-0cc7ddb3af9f 31 May 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210531235321-1ab3b4f5c898 31 May 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210523131352-3bfa62b2c642 23 May 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210513151621-10a1c0a04bcf 13 May 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.3-0.20210421004028-60af5a5e5c58 21 Apr 2021 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20210105222246-07737475986b 05 Jan 2021 H1 U1 BSD-3-Clause Yes Details →
v0.5.2 05 Jan 2021 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20210105221914-47e17ebe675f+incompatible 05 Jan 2021 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20210105221708-0516b57e142c+incompatible 05 Jan 2021 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20210105221512-058fed478734+incompatible 05 Jan 2021 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20210105212032-e4c922b492be+incompatible 05 Jan 2021 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201222001644-b14c45b2b688+incompatible 22 Dec 2020 H1 U1 BSD-3-Clause Yes Details →
v5.1.1-0.20201222001644-b14c45b2b688+incompatible 22 Dec 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201221232339-f4fe090fcfb7+incompatible 21 Dec 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201216145407-bee3b985a0e8+incompatible 16 Dec 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201128204636-147e2b447e42+incompatible 28 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v5.1.1-0.20201128204636-147e2b447e42+incompatible 28 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201128182507-a764fc22f3b5+incompatible 28 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v5.1.1-0.20201128182507-a764fc22f3b5+incompatible 28 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201128004009-ce26fd451017+incompatible 28 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v5.1.1-0.20201128004009-ce26fd451017+incompatible 28 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201103184836-bce379e3099a+incompatible 03 Nov 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201015220411-23edf22e1874+incompatible 15 Oct 2020 H1 U1 BSD-3-Clause Yes Details →
v5.1.1-0.20201015220411-23edf22e1874+incompatible 15 Oct 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.1-0.20201002225736-680774c1b3cf+incompatible 02 Oct 2020 H1 U1 BSD-3-Clause Yes Details →
v0.0.0-20200812034914-d05b3863d2c7 12 Aug 2020 H1 U1 BSD-3-Clause Yes Details →
v4.9.0+incompatible 12 Aug 2020 H1 U1 BSD-3-Clause Yes Details →
v5.1.1-0.20200812034914-d05b3863d2c7+incompatible 12 Aug 2020 H1 U1 — Yes Details →
v4.8.1-0.20200808141351-4ac3b6975496+incompatible 08 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200808041328-fbc627776a3d 08 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200808040245-162e5629780b 08 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200808040232-1d4c88e65fde 08 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200805154226-4c18d304a429 05 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200805154221-42bcdf26fca5 05 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200805154216-9b58b85b0b7d 05 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200805154209-b237418f2346 05 Aug 2020 H1 U1 — Yes Details →
v0.0.0-20200624175548-44b01e11b72e 24 Jun 2020 H1 U1 — Yes Details →
v0.0.0-20200529091600-05d4a7f4b624 29 May 2020 H1 U1 — Yes Details →
v0.0.0-20200518170539-17efcbe3533f 18 May 2020 H1 U1 — Yes Details →
v0.0.0-20200326221011-78cf02996493 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326215721-c781b2a96bf6 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326214316-39fd76ecae93 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326214028-239740074c83 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326214028-9f7d3fd5c24b 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326214028-a8691c6cf046 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326034543-63b09d42374b 26 Mar 2020 H1 U1 — Yes Details →
v0.0.0-20200326011414-44ca1a372a39 26 Mar 2020 H1 U1 — Yes Details →

The newest 120 of 303 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for github.com/evanphx/json-patch

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2018-14632: JSON-Patch Out-of-bounds Write vulnerability in github.com/evanphx/json-patch 7.7 high 0.5.2 13 May 2022
CVE-2018-14632: Out-of-bounds write in github.com/evanphx/json-patch N/A unrated 0.5.2 14 Apr 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 github.com/evanphx/json-patch

Is github.com/evanphx/json-patch safe to use?

Vulert records 2 vulnerabilities for github.com/evanphx/json-patch in Go: 0 critical, 1 high, 0 medium and 0 low, plus 1 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is github.com/evanphx/json-patch's Vulert package health score?

Vulert scores github.com/evanphx/json-patch 64/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of github.com/evanphx/json-patch affected?

Yes. v0.5.2, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of github.com/evanphx/json-patch should I use?

v0.5.2 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does github.com/evanphx/json-patch have?

2 vulnerabilities are recorded for github.com/evanphx/json-patch in the Go ecosystem: 0 critical, 1 high, 0 medium and 0 low, plus 1 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 github.com/evanphx/json-patch vulnerabilities disclosed?

0 vulnerabilities were recorded for github.com/evanphx/json-patch in the last 12 months, and the oldest entry in this database dates to 14 Apr 2021. 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 github.com/evanphx/json-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 github.com/evanphx/json-patch for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/evanphx/json-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.