How severe is CVE-2014-3574?

No CVSS score has been assigned to CVE-2014-3574 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-3574?

CVE-2014-3574 affects the following packages: org.apache.poi:poi (Maven), org.apache.poi:poi (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-3574?

Update org.apache.poi:poi to 3.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3574 is resolved across your whole dependency graph.

How do I detect CVE-2014-3574 in my Maven dependencies?

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

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

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is CVE-2014-3574 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-3574 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 CVE-2014-3574?

CVE-2014-3574 has an EPSS (Exploit Prediction Scoring System) score of 7.1%, placing it in the 94th 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-2014-3574 published, and has it been updated?

CVE-2014-3574 was published on September 4, 2014 and was last updated on April 16, 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

CVE-2014-3574 — poi

CVE-2014-3574 is a security vulnerability in org.apache.poi:poi. A fix is available for org.apache.poi:poi — see the affected versions and patch details below.

Improper Input Validation in Apache POI

Also known asGHSA-5wfp-8643-c58x

Published

Sep 4, 2014

Updated

Apr 16, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

7.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs94th percentile — riskier than 94% 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.poi:poi☕org.apache.poi:poi

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

Apache POI before 3.10.1 and 3.11.x before 3.11-beta2 allows remote attackers to cause a denial of service (CPU consumption and crash) via a crafted OOXML file, aka an XML Entity Expansion (XEE) attack.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.poi:poi`	all versions	3.10.1`org.apache.poi:poi:3.10.1`
☕Maven	`org.apache.poi:poi`	≥ 3.11-beta1&&< 3.11-beta2	3.11-beta2`org.apache.poi:poi:3.11-beta2`

Affected Products

1 product · 65 configurations

Application

poiapache

≤ 3.10

37 versions

0.10.20.30.40.50.60.70.10.00.11.00.12.00.13.00.14.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.poi:poi, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.poi:poi to 3.10.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-3574 is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

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 Product Security has determined that CVE-2014-3574 is not exploitable by default in JBoss Portal Platform as provided by Red Hat. This flaw would only be exploitable if the Apache POI library provided by JBoss Portal Platform were used by a custom application to process user-supplied XML documents.

Product	Fixed in	Advisory
Red Hat JBoss BPMS 6.0	see advisory	RHSA-2014:1399
Red Hat JBoss BRMS 6.0	see advisory	RHSA-2014:1400
Red Hat JBoss Data Virtualization 6.0	`apache-poi`	RHSA-2014:1398
Red Hat JBoss Fuse Service Works 6.0	`apache-poi`	RHSA-2014:1370
Red Hat JBoss Portal 6.2	`apache-poi`	RHSA-2015:1009

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-3574 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works