How severe is GHSA-mjf9-4pcv-vfg7?

No CVSS score has been assigned to GHSA-mjf9-4pcv-vfg7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mjf9-4pcv-vfg7?

GHSA-mjf9-4pcv-vfg7 affects the following packages: org.apache.openmeetings:openmeetings-parent (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mjf9-4pcv-vfg7?

Update org.apache.openmeetings:openmeetings-parent to 8.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjf9-4pcv-vfg7 is resolved across your whole dependency graph.

How do I detect GHSA-mjf9-4pcv-vfg7 in my Maven dependencies?

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

How do I mitigate GHSA-mjf9-4pcv-vfg7 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-mjf9-4pcv-vfg7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mjf9-4pcv-vfg7 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-mjf9-4pcv-vfg7?

GHSA-mjf9-4pcv-vfg7 has an EPSS (Exploit Prediction Scoring System) score of 68.8%, placing it in the 99th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-mjf9-4pcv-vfg7?

GHSA-mjf9-4pcv-vfg7 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-mjf9-4pcv-vfg7 published, and has it been updated?

GHSA-mjf9-4pcv-vfg7 was published on January 8, 2025 and was last updated on January 8, 2025. 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

Apache OpenMeetings vulnerable to Deserialization of Untrusted DataGHSA-mjf9-4pcv-vfg7

Fix: apache/openmeetings@1c3426c

GHSA-mjf9-4pcv-vfg7 is a Deserialization of Untrusted Data vulnerability in org.apache.openmeetings:openmeetings-parent. EPSS puts its 30-day exploitation probability at 68.8% (99th percentile). A fix is available for org.apache.openmeetings:openmeetings-parent — see the affected versions and patch details below.

Also known asCVE-2024-54676

Published

Jan 8, 2025

Updated

Jan 8, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mjf9-4pcv-vfg7.

EPSS Exploitation Probability

via FIRST.org ↗

68.8%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕org.apache.openmeetings:openmeetings-parent

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

Vendor: The Apache Software Foundation

Versions Affected: Apache OpenMeetings from 2.1.0 before 8.0.0

Description: Default clustering instructions at https://openmeetings.apache.org/Clustering.html doesn't specify white/black lists for OpenJPA this leads to possible deserialisation of untrusted data. Users are recommended to upgrade to version 8.0.0 and update their startup scripts to include the relevant 'openjpa.serialization.class.blacklist' and 'openjpa.serialization.class.whitelist' configurations as shown in the documentation.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.openmeetings:openmeetings-parent`	≥ 2.1.0&&< 8.0.0	8.0.0`org.apache.openmeetings:openmeetings-parent:8.0.0`

Affected Products

1 product · 1 configurations

Application

openmeetingsapache

≥ 2.1 && < 8.0.0

range

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.openmeetings:openmeetings-parent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.openmeetings:openmeetings-parent to 8.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mjf9-4pcv-vfg7 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.

Frequently Asked Questions

Vendor: The Apache Software Foundation Versions Affected: Apache OpenMeetings from 2.1.0 before 8.0.0 Description: Default clustering instructions at https://openmeetings.apache.org/Clustering.html doesn't specify white/black lists for OpenJPA this leads to possible deserialisation of untrusted data. Users are recommended to upgrade to version 8.0.0 and update their startup scripts to include the relevant 'openjpa.serialization.class.blacklist' and 'openjpa.serialization.class.whitelist' configurations as shown in the documentation.

O3 Security · Impact-Aware SCA

Is GHSA-mjf9-4pcv-vfg7 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works