How severe is GHSA-j65f-mvgw-prp2?

No CVSS score has been assigned to GHSA-j65f-mvgw-prp2 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-j65f-mvgw-prp2?

GHSA-j65f-mvgw-prp2 affects the following packages: org.apache.openjpa:openjpa (Maven), org.apache.openjpa:openjpa (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j65f-mvgw-prp2?

Update org.apache.openjpa:openjpa to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j65f-mvgw-prp2 is resolved across your whole dependency graph.

How do I detect GHSA-j65f-mvgw-prp2 in my Maven dependencies?

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

How do I mitigate GHSA-j65f-mvgw-prp2 if there is no patch (or I can't update yet)?

Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

Is GHSA-j65f-mvgw-prp2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-j65f-mvgw-prp2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j65f-mvgw-prp2?

GHSA-j65f-mvgw-prp2 has an EPSS (Exploit Prediction Scoring System) score of 9.5%, placing it in the 95th 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.

What type of vulnerability is GHSA-j65f-mvgw-prp2?

GHSA-j65f-mvgw-prp2 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-j65f-mvgw-prp2 published, and has it been updated?

GHSA-j65f-mvgw-prp2 was published on May 14, 2022 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Deserialization of Untrusted Data in Apache OpenJPA

EPSS Exploitation Probability

via FIRST.org ↗

9.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.apache.openjpa:openjpa☕org.apache.openjpa:openjpa

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

The BrokerFactory functionality in Apache OpenJPA 1.x before 1.2.3 and 2.x before 2.2.2 creates local executable JSP files containing logging trace data produced during deserialization of certain crafted OpenJPA objects, which makes it easier for remote attackers to execute arbitrary code by creating a serialized object and leveraging improperly secured server programs.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.openjpa:openjpa`	≥ 1.0.0&&< 1.2.3	1.2.3`org.apache.openjpa:openjpa:1.2.3`
☕Maven	`org.apache.openjpa:openjpa`	≥ 2.0.0&&< 2.2.2	2.2.2`org.apache.openjpa:openjpa:2.2.2`

Affected Products

1 product · 15 configurations

Application

openjpaapache

15 versions

1.0.01.0.11.0.21.0.31.0.41.1.01.2.01.2.11.2.22.0.02.0.12.1.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.openjpa:openjpa, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.openjpa:openjpa to 1.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j65f-mvgw-prp2 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.

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

RHSA-2013:1862Fuse ESB Enterprise 7.1.0 RHSA-2013:1185Red Hat JBoss Fuse 6.0

Frequently Asked Questions

The BrokerFactory functionality in Apache OpenJPA 1.x before 1.2.3 and 2.x before 2.2.2 creates local executable JSP files containing logging trace data produced during deserialization of certain crafted OpenJPA objects, which makes it easier for remote attackers to execute arbitrary code by creating a serialized object and leveraging improperly secured server programs.

O3 Security · Impact-Aware SCA

Is GHSA-j65f-mvgw-prp2 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Deserialization of Untrusted Data in Apache OpenJPAGHSA-j65f-mvgw-prp2