How severe is GHSA-3wc8-659g-r88q?

No CVSS score has been assigned to GHSA-3wc8-659g-r88q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3wc8-659g-r88q?

GHSA-3wc8-659g-r88q 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 GHSA-3wc8-659g-r88q?

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 GHSA-3wc8-659g-r88q is resolved across your whole dependency graph.

How do I detect GHSA-3wc8-659g-r88q 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-3wc8-659g-r88q 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.

How does O3 Security protect against GHSA-3wc8-659g-r88q?

O3 pinpoints whether GHSA-3wc8-659g-r88q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-3wc8-659g-r88q actively exploited in the wild?

No public exploit code has been indexed for GHSA-3wc8-659g-r88q 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 type of vulnerability is GHSA-3wc8-659g-r88q?

GHSA-3wc8-659g-r88q 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 GHSA-3wc8-659g-r88q published, and has it been updated?

GHSA-3wc8-659g-r88q was published on January 25, 2019 and was last updated on September 23, 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

GHSA-3wc8-659g-r88q

GHSA-3wc8-659g-r88q is a XML External Entity (XXE) vulnerability in org.springframework.batch:spring-batch-core. O3 Security confirms whether GHSA-3wc8-659g-r88q is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2019-3774

Published

Jan 25, 2019

Updated

Sep 23, 2025

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Blast Radius

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
☕Maven	`org.springframework.batch:spring-batch-core`	≥ 4.0.0.RELEASE&&< 4.0.2.RELEASE	4.0.2.RELEASE
☕Maven	`org.springframework.batch:spring-batch-core`	≥ 4.1.0.RELEASE&&< 4.1.1.RELEASE	4.1.1.RELEASE

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-3wc8-659g-r88q 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.
How O3 protects you
O3 pinpoints whether GHSA-3wc8-659g-r88q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-3wc8-659g-r88q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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 GHSA-3wc8-659g-r88q in your dependencies?

O3 detects GHSA-3wc8-659g-r88q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works