How severe is GHSA-pfh2-hfmq-phg5?

GHSA-pfh2-hfmq-phg5 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 GHSA-pfh2-hfmq-phg5?

GHSA-pfh2-hfmq-phg5 affects the following packages: com.jayway.jsonpath:json-path (Maven). Ecosystems affected: Maven.

How do I fix GHSA-pfh2-hfmq-phg5?

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 GHSA-pfh2-hfmq-phg5 is resolved across your whole dependency graph.

How do I detect GHSA-pfh2-hfmq-phg5 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 GHSA-pfh2-hfmq-phg5 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

Is GHSA-pfh2-hfmq-phg5 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-pfh2-hfmq-phg5, 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 GHSA-pfh2-hfmq-phg5?

GHSA-pfh2-hfmq-phg5 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 52th 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 GHSA-pfh2-hfmq-phg5 published, and has it been updated?

GHSA-pfh2-hfmq-phg5 was published on December 27, 2023 and was last updated on September 10, 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

json-path Out-of-bounds Write vulnerabilityGHSA-pfh2-hfmq-phg5

MEDIUMFix: json-path/JsonPath@71a09c1

GHSA-pfh2-hfmq-phg5 is a medium-severity (CVSS 5.3) remote code execution vulnerability in com.jayway.jsonpath:json-path. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for com.jayway.jsonpath:json-path — see the affected versions and patch details below.

Also known asCVE-2023-51074

Published

Dec 27, 2023

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Nov 6, 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 CVEs52th percentile — riskier than 52% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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`

Affected Products

1 product · 1 configurations

Application

jayway jsonpathjson-path

≥ 2.2.0 && < 2.9.0

range

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 GHSA-pfh2-hfmq-phg5 is resolved across your whole dependency graph.
Workarounds
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process.

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 GHSA-pfh2-hfmq-phg5 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works