Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

CVE-2018-14632 json-patch

HIGHFix: evanphx/json-patch@4c9aadc

CVE-2018-14632 is a high-severity (CVSS 7.7) Out-of-bounds Write vulnerability in github.com/evanphx/json-patch. A fix is available for github.com/evanphx/json-patch — see the affected versions and patch details below.

JSON-Patch Out-of-bounds Write vulnerability

Also known asGHSA-gxhv-3hwf-wjp9GO-2021-0076
Published
Sep 6, 2018
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2018-14632 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
🐹github.com/evanphx/json-patch🐹github.com/evanphx/json-patch

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. An attacker can use this flaw to cause a denial of service attack on the Openshift master api service which provides cluster management.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/evanphx/json-patchall versions0.5.2go get github.com/evanphx/json-patch@v0.5.2
🐹Gogithub.com/evanphx/json-patch3.0.0&&< 3.0.1-0.20180525145409-4c9aadca8f893.0.1-0.20180525145409-4c9aadca8f89go get github.com/evanphx/json-patch@v3.0.1-0.20180525145409-4c9aadca8f89

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/evanphx/json-patch, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/evanphx/json-patch to 0.5.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-14632 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2018-14632 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2018-14632. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A multi-master Openshift Container Platform cluster is more resilient, however a sustained attack would still have an important impact.

ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.10atomic-openshift-0:3.10.66-1.git.0.91d1e89.el7RHSA-2018:2709
Red Hat OpenShift Container Platform 3.11atomic-openshift-0:3.11.16-1.git.0.b48b8f8.el7RHBA-2018:2652
Red Hat OpenShift Container Platform 3.6atomic-openshift-0:3.6.173.0.130-1.git.0.8d78a39.el7RHSA-2018:2654
Red Hat OpenShift Container Platform 3.7atomic-openshift-0:3.7.72-1.git.0.925b9cd.el7RHSA-2018:2906
Red Hat OpenShift Container Platform 3.9atomic-openshift-0:3.9.51-1.git.0.dc3a40b.el7RHSA-2018:2908

Frequently Asked Questions

An out of bound write can occur when patching an Openshift object using the 'oc patch' functionality in OpenShift Container Platform before 3.7. An attacker can use this flaw to cause a denial of service attack on the Openshift master api service which provides cluster management.
O3 Security · Impact-Aware SCA

Is CVE-2018-14632 in your dependencies?

O3 Security finds CVE-2018-14632 across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2018-14632: json-patch DoS (High 7.7) | O3 Security