/

CVE-2026-79572

Severity:

HIGH RISK

(7.5)

XXE (CWE-611) in Distribution Management Level Rules

CVE-2026-79572

Deferred

Vulnerability type

Category:

XML External Entity (XXE)

CWE:

CWE-611

Impact:

Sensitive Data Exposure and Server-Side Request Forgery

Severity:

HIGH RISK

(7.5)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A high-severity XML External Entity (XXE) vulnerability in the Distribution Management level-rule module allows crafted XML input to reference external entities. If attacker-controlled XML is processed by the affected component, the issue may expose local files, enable internal network scanning, or contribute to server-side attacks.

Affected context

The vulnerability occurs in Distribution Management v1.0.0 when the level-rule module processes XML that an attacker can influence. Risk is higher when the XML parser permits external entity resolution and the application has access to sensitive local files or internal network services.

Exploit preconditions

  • Attack surface: XML input handled by the level-rule module - Required access: Ability to submit or otherwise influence XML processed

by the application

  • Trigger point: Parsing of a crafted XML document - Why exploitation is possible: The XML parser may resolve attacker-defined

external entities, allowing references to local resources or network

locations

Why this happens

The underlying bug is unsafe XML parsing that permits external entity resolution for untrusted documents. XML entity declarations can cause the parser to retrieve local files or make requests to remote locations during parsing. This behavior maps to CWE-611, Improper Restriction of XML External Entity Reference.

Potential impact

  • An attacker may read sensitive local files accessible to the process.
  • The application could be used to probe internal network services.
  • The server may make unintended outbound requests.
  • Confidentiality of application or infrastructure data could be reduced.
  • In some deployment conditions, the issue could contribute to further server attacks.

General mitigation guidance

Mitigation generally focuses on disabling external entity resolution and external document retrieval for untrusted XML. Secure-by-default XML parsers with restricted entity processing are preferable to permissive parser configurations. Applications can reduce input trust by validating XML against an allowlisted schema, rejecting unnecessary document types or declarations, and isolating XML parsing from sensitive network and filesystem resources. Least-privilege service accounts, restricted outbound network access, and minimized filesystem permissions can limit impact if parsing controls fail.

How teams detect issues like this

Detection approaches include static analysis for XML parser configurations that enable external entities, external DTD loading, or network retrieval. Code review should examine every path where user-controlled XML reaches a parser and verify that secure processing settings are enforced consistently. Runtime monitoring can flag unexpected file access, DNS lookups, or outbound requests during XML parsing. CI policies and automated security review tools may help identify unsafe XML parser patterns before deployment.

Sources

SourceLink
github.comgithub.com/fangtang7/CVE/blob/main/Distribution%20Management/XXE.md

Frequently asked

questions

It may be remotely exploitable when an attacker can submit XML to a

reachable level-rule processing endpoint or workflow. The exact scope

depends on how the module is exposed and how XML input is authenticated.

The attacker needs the ability to supply or influence XML that the affected

parser processes. This may require authentication, depending on application

access controls.

Configure XML parsing to disable external entity and external resource

resolution, and use a secure parser configuration designed for untrusted

input.

Treat XML as untrusted data, enforce schema and input validation, test parser

security settings in CI, and restrict the process's filesystem and network

privileges.

Find out what's already
exploitable in your codebase.