XML external entity (XXE) processing ('external-parameter-entities' feature was not fully disabled))

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

EPSS

• CVE-2019-10782: 1.53% estimated exploitation activity in the next 30 days; percentile 74.73 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Due to an incomplete fix for CVE-2019-9658, checkstyle was still vulnerable to XML External Entity (XXE) Processing. Impact User: Build Maintainers This vulnerability probably doesn't impact Maven/Gradle users as, in most cases, these builds are processing files that are trusted, or pre-vetted by a pull request reviewer before being run on internal CI infrastructure. User: Static Analysis as a Service If you operate a site/service that parses "untrusted" Checkstyle XML configuration files, you are vulnerable to this and should patch. Note from the discoverer of the original CVE-2019-9658: While looking at a few companies that run Checkstyle/PMD/ect... as a service I notice that it's a common pattern to run the static code analysis tool inside of a Docker container with the following flags: Running the analysis in Docker has the advantage that there should be no sensitive local file information that XXE can exfiltrate from the container. Additionally, these flags prevent…

Published by the source

31 Jan 2020, 18:00 UTC

Last modified by the source

9 Jan 2023, 05:02 UTC

Source last checked

26 Oct 2026, 15:52 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-763g-fqq7-48wg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2019-10782

Advisory: XML external entity (XXE) processing ('external-parameter-entities' feature was not fully disabled))
IDs: CVE-2019-10782, GHSA-763g-fqq7-48wg
Record: https://patchnext.com/advisories/cve-2019-10782 (revision 1, source checked 26 Oct 2026, 15:52 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.puppycrawl.tools:checkstyle 8.29. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.puppycrawl.tools:checkstyle: affected < 8.29; fixed in 8.29

## Suggested inspection (read-only)
- Maven com.puppycrawl.tools:checkstyle: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.puppycrawl.tools:checkstyle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-763g-fqq7-48wg (GitHub-reviewed advisory GHSA-763g-fqq7-48wg lists affected ranges: Maven com.puppycrawl.tools:checkstyle >=0 <8.29)

Commands are suggestions: review each one before running it.