Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.8

dd-plist XML External Entitly vulnerability

CVE-2016-15026GHSA-4jx2-hvqw-93j9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (com.googlecode.plist:dd-plist 1.18), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.8 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2016-15026: 0.55% estimated exploitation activity in the next 30 days; percentile 45.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

A vulnerability was found in 3breadt dd-plist 1.17 and classified as problematic. Affected by this issue is some unknown functionality. The manipulation leads to xml external entity reference. An attack has to be approached locally. Upgrading to version 1.18 is able to address this issue. The name of the patch is 8c954e8d9f6f6863729e50105a8abf3f87fff74c. It is recommended to upgrade the affected component. VDB-221486 is the identifier assigned to this vulnerability.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-4jx2-hvqw-93j9

Agent brief

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

# Patch Next advisory brief: CVE-2016-15026

Advisory: dd-plist XML External Entitly vulnerability
IDs: CVE-2016-15026, GHSA-4jx2-hvqw-93j9
Record: https://patchnext.com/advisories/cve-2016-15026 (revision 1, source checked 26 Oct 2026, 16:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.googlecode.plist:dd-plist 1.18. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.googlecode.plist:dd-plist: affected < 1.18; fixed in 1.18

## Suggested inspection (read-only)
- Maven com.googlecode.plist:dd-plist: 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.googlecode.plist:dd-plist.
- 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-4jx2-hvqw-93j9 (GitHub-reviewed advisory GHSA-4jx2-hvqw-93j9 lists affected ranges: Maven com.googlecode.plist:dd-plist >=0 <1.18)

Commands are suggestions: review each one before running it.

Loading voting…