Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') The advisory has been revoked - it doesn't affect any version of package satellite/iop-vulnerability-frontend-rhel9  (opens in a new tab)


Threat Intelligence

EPSS
0.58% (43rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-SATELLITEIOPVULNERABILITYFRONTENDRHEL9-15750864
  • published23 Mar 2026
  • disclosed20 Mar 2026

Introduced: 20 Mar 2026

CVE-2026-33036  (opens in a new tab)
CWE-776  (opens in a new tab)

Amendment

The Red Hat security team deemed this advisory irrelevant for RHEL:7.

NVD Description

Note: Versions mentioned in the description apply only to the upstream satellite/iop-vulnerability-frontend-rhel9 package and not the satellite/iop-vulnerability-frontend-rhel9 package as distributed by RHEL.

fast-xml-parser allows users to process XML from JS object without C/C++ based libraries or callbacks. Versions 4.0.0-beta.3 through 5.5.5 contain a bypass vulnerability where numeric character references (&#NNN;, &#xHH;) and standard XML entities completely evade the entity expansion limits (e.g., maxTotalExpansions, maxExpandedLength) added to fix CVE-2026-26278, enabling XML entity expansion Denial of Service. The root cause is that replaceEntitiesValue() in OrderedObjParser.js only enforces expansion counting on DOCTYPE-defined entities while the lastEntities loop handling numeric/standard entities performs no counting at all. An attacker supplying 1M numeric entity references like A can force ~147MB of memory allocation and heavy CPU usage, potentially crashing the process—even when developers have configured strict limits. This issue has been fixed in version 5.5.6.