How severe is GHSA-xvm2-9xvc-hx7f?

GHSA-xvm2-9xvc-hx7f has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-xvm2-9xvc-hx7f?

GHSA-xvm2-9xvc-hx7f affects the following packages: com.monitorjbl:xlsx-streamer (Maven). Ecosystems affected: Maven.

How do I fix GHSA-xvm2-9xvc-hx7f?

Update com.monitorjbl:xlsx-streamer to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvm2-9xvc-hx7f is resolved across your whole dependency graph.

How do I detect GHSA-xvm2-9xvc-hx7f in my Maven dependencies?

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

How do I mitigate GHSA-xvm2-9xvc-hx7f 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.

Is GHSA-xvm2-9xvc-hx7f actively exploited in the wild?

No public exploit code has been indexed for GHSA-xvm2-9xvc-hx7f 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-xvm2-9xvc-hx7f?

GHSA-xvm2-9xvc-hx7f has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 69th 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-xvm2-9xvc-hx7f?

GHSA-xvm2-9xvc-hx7f is classified as XML External Entity (XXE) (CWE-611), CWE-776 (CWE-776). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xvm2-9xvc-hx7f published, and has it been updated?

GHSA-xvm2-9xvc-hx7f was published on March 2, 2022 and was last updated on February 16, 2024. 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

CRITICAL severity

Improper Restriction of XML External Entity Reference in com.monitorjbl:xlsx-streamerGHSA-xvm2-9xvc-hx7f

CRITICALFix: monitorjbl/excel-streaming-reader@0749c7b

GHSA-xvm2-9xvc-hx7f is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in com.monitorjbl:xlsx-streamer. A fix is available for com.monitorjbl:xlsx-streamer — see the affected versions and patch details below.

Also known asCVE-2022-23640

Published

Mar 2, 2022

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 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-xvm2-9xvc-hx7f.

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs69th percentile — riskier than 69% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-xvm2-9xvc-hx7f by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕com.monitorjbl:xlsx-streamer

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

Impact

Prior to xlsx-streamer 2.1.0, the XML parser that was used did not apply all the necessary settings to prevent XML Entity Expansion issues.

Patches

Upgrade to version 2.1.0.

Workarounds

No known workaround.

References

https://github.com/monitorjbl/excel-streaming-reader/commit/0749c7b9709db078ccdeada16d46a34bc2910c73

For more information

If you have any questions or comments about this advisory:

Open an issue in monitorjbl/excel-streaming-reader

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.monitorjbl:xlsx-streamer`	all versions	2.1.0`com.monitorjbl:xlsx-streamer:2.1.0`

Affected Products

1 product · 1 configurations

Application

excel streaming readerexcel_streaming_reader_project

< 2.1.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 com.monitorjbl:xlsx-streamer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.monitorjbl:xlsx-streamer to 2.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvm2-9xvc-hx7f 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.

Frequently Asked Questions

### Impact Prior to xlsx-streamer 2.1.0, the XML parser that was used did not apply all the necessary settings to prevent XML Entity Expansion issues. ### Patches Upgrade to version 2.1.0. ### Workarounds No known workaround. ### References https://github.com/monitorjbl/excel-streaming-reader/commit/0749c7b9709db078ccdeada16d46a34bc2910c73 ### For more information If you have any questions or comments about this advisory: * Open an issue in [monitorjbl/excel-streaming-reader](https://github.com/monitorjbl/excel-streaming-reader)