How severe is CVE-2023-51074?

CVE-2023-51074 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2023-51074?

CVE-2023-51074 affects the following packages: com.jayway.jsonpath:json-path (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-51074?

Update com.jayway.jsonpath:json-path to 2.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-51074 is resolved across your whole dependency graph.

How do I detect CVE-2023-51074 in my Maven dependencies?

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

How do I mitigate CVE-2023-51074 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2023-51074?

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

Is CVE-2023-51074 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2023-51074, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2023-51074?

CVE-2023-51074 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was CVE-2023-51074 published, and has it been updated?

CVE-2023-51074 was published on December 27, 2023 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2023-51074 — json-path

MEDIUMFix: json-path/JsonPath@71a09c1

CVE-2023-51074 is a medium-severity (CVSS 5.3) remote code execution vulnerability in com.jayway.jsonpath:json-path. 1 public exploit reference exists, so weaponization risk is real. A fix is available for com.jayway.jsonpath:json-path — see the affected versions and patch details below.

json-path Out-of-bounds Write vulnerability

Also known asGHSA-pfh2-hfmq-phg5

Published

Dec 27, 2023

Updated

Aug 12, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 18, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% 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-2023-51074 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 378,156 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

1 pkg affected

☕com.jayway.jsonpath:json-path

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

Description

json-path v2.8.0 was discovered to contain a stack overflow via the Criteria.parse() method.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.jayway.jsonpath:json-path`	≥ 2.2.0&&< 2.9.0	2.9.0`com.jayway.jsonpath:json-path:2.9.0`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

json-path v2.8.0 was discovered to contain a stack overflow via the Crit…

github.comNVDJan 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.jayway.jsonpath:json-path, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.jayway.jsonpath:json-path to 2.9.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-51074 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-51074 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2023-51074. 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 HatModerate

Red Hat rates this at maximum of a Moderate impact. When interacting with a server to explore this possible vulnerability, the attacker would be the only one seeing a HTTP 500 error and no other user (or the server entirely) would be vulnerable in a real application scenario with multi-threads.

Product	Fixed in	Advisory
Red Hat AMQ Streams 2.7.0	see advisory	RHSA-2024:3527
Red Hat build of Apache Camel 4.4.0 for Spring Boot	`json-path`	RHSA-2024:2707
RHBOAC camel-quarkus 3 (camel-4.0/quarkus-3.2)	`json-path`	RHSA-2024:0789
RHINT Camel-Springboot 3.20.5	`json-path`	RHSA-2024:0792

Frequently Asked Questions

json-path v2.8.0 was discovered to contain a stack overflow via the Criteria.parse() method.

O3 Security · Impact-Aware SCA

Is CVE-2023-51074 in your dependencies?

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

Scan my dependencies How O3 SCA works