How severe is CVE-2019-3774?

CVE-2019-3774 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-3774?

CVE-2019-3774 affects the following packages: org.springframework.batch:spring-batch-core (Maven), org.springframework.batch:spring-batch-core (Maven), org.springframework.batch:spring-batch-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-3774?

Update org.springframework.batch:spring-batch-core to 3.0.10.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3774 is resolved across your whole dependency graph.

How do I detect CVE-2019-3774 in my Maven dependencies?

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

How do I mitigate CVE-2019-3774 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 CVE-2019-3774 actively exploited in the wild?

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

CVE-2019-3774 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th 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 CVE-2019-3774?

CVE-2019-3774 is classified as XML External Entity (XXE) (CWE-611). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-3774 published, and has it been updated?

CVE-2019-3774 was published on January 18, 2019 and was last updated on October 20, 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

CRITICAL severity

CVE-2019-3774 — spring-batch-core

CRITICAL

CVE-2019-3774 is a critical-severity (CVSS 9.8) XML External Entity (XXE) vulnerability in org.springframework.batch:spring-batch-core. A fix is available for org.springframework.batch:spring-batch-core — see the affected versions and patch details below.

Low severity vulnerability that affects org.springframework.batch:spring-batch-core

Also known asGHSA-3wc8-659g-r88q

Published

Jan 18, 2019

Updated

Oct 20, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% 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

3 pkgs affected

☕org.springframework.batch:spring-batch-core☕org.springframework.batch:spring-batch-core☕org.springframework.batch:spring-batch-core

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

Spring Batch versions 3.0.9, 4.0.1, 4.1.0, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.batch:spring-batch-core`	all versions	3.0.10.RELEASE`org.springframework.batch:spring-batch-core:3.0.10.RELEASE`
☕Maven	`org.springframework.batch:spring-batch-core`	≥ 4.0.0.RELEASE&&< 4.0.2.RELEASE	4.0.2.RELEASE`org.springframework.batch:spring-batch-core:4.0.2.RELEASE`
☕Maven	`org.springframework.batch:spring-batch-core`	≥ 4.1.0.RELEASE&&< 4.1.1.RELEASE	4.1.1.RELEASE`org.springframework.batch:spring-batch-core:4.1.1.RELEASE`

Affected Products

1 product · 3 configurations

Application

spring batchbroadcom

≥ 4.0.0 && ≤ 4.0.1

1 version

4.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.springframework.batch:spring-batch-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.batch:spring-batch-core to 3.0.10.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3774 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.

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

Product	Fixed in	Advisory
Red Hat Fuse 7.8.0	`spring-batch-core`	RHSA-2020:5568

Frequently Asked Questions

Spring Batch versions 3.0.9, 4.0.1, 4.1.0, and older unsupported versions, were susceptible to XML External Entity Injection (XXE) when receiving XML data from untrusted sources.

O3 Security · Impact-Aware SCA

Is CVE-2019-3774 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works