Skip to main content
CVE-2025-42873VulnerabilityPublished

CVE-2025-42873: SAP_SE SAPUI5 framework (Markdown-it component) · Asymmetric Resource Consumption

Affects SAP_SE SAPUI5 framework (Markdown-it component)Source CVE Database V5

0

Not known to be exploited · CVSS 5.9 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
npmmarkdown-itpkg:npm/markdown-itOther threatsAffected
  • =756
  • =757
  • =758
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor SAP and third-party advisories for official patches or updates addressing CVE-2025-42873 and apply them promptly once available. 2. Implement input validation and sanitization on all markdown inputs to detect and block malformed content that could trigger the infinite loop. 3. Employ rate limiting and anomaly detection on endpoints processing markdown content to prevent abuse and detect unusual CPU usage spikes. 4. Consider isolating SAPUI5 services in dedicated environments with resource limits to contain potential DoS impact. 5. Regularly monitor system performance metrics, especially CPU and thread responsiveness, to identify early signs of exploitation. 6. Engage with SAP support to understand any interim workarounds or configuration changes that can mitigate risk. 7. Educate development and operations teams about the risks of outdated third-party libraries and enforce secure software supply chain practices. 8. Review and update incident response plans to include scenarios involving UI-layer DoS attacks.

Description

SAPUI5 (and OpenUI5) packages use outdated 3rd party libraries with known security vulnerabilities. When markdown-it encounters special malformed input, it fails to terminate properly, resulting in an infinite loop. This Denial of Service via infinite loop causes high CPU usage and system unresponsiveness due to a blocked processing thread. This vulnerability has no impact on confidentiality or integrity but has a high impact on system availability.

References

Community reviews

Loading reviews…