Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.58% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-71436High confidence
Mermaid XY Charts are vulnerable to an infinite loop DoS
mermaid-js · mermaid
Official source article: GitHub GHSA-2V8P-3F2J-5MP7 ↗. Check the applicable product and release in the original source.
5.3MediumCVSS 4.0
Patch only the product branches with a verified fix
Fix availability varies by productMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs mermaid-js mermaid and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
2 package statesRelease-specific package status
Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian forkyforky · source | node-mermaid | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | node-mermaid | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
Open-source package ranges4 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| npmmermaid | >= 10.6.0, < 10.9.8 | 10.9.8 | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npmmermaid | >= 11.0.0-alpha.1, < 11.16.1 | 11.16.1 | GitHub advisory ↗upstream repository advisory · 6 Aug 2026 |
| npmmermaid | SEMVER: introduced 10.6.0; fixed 10.9.8 | 10.9.8 | OSV record ↗aggregator derived · 10 Sep 2026 |
| npmmermaid | SEMVER: introduced 11.0.0-alpha.1; fixed 11.16.1 | 11.16.1 | OSV record ↗aggregator derived · 10 Sep 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-71436 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitymermaid: Mermaid XY Charts: Denial of Service via invalid X-Axis parameters
The vendor explicitly identifies these products or versions as containing the fix.
- registry.redhat.io/devspaces/code-rhel9@sha256:02f759255a2259ae4c7e41a980dcecc9a72efcfb050dcdbeba4469d62eb352db_s390x as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/code-rhel9@sha256:23f78b2564f05173a9d5beb28d85369c6d2c095b479d4d11f3a8f1aae0844f04_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/code-rhel9@sha256:7cb88955f069bb340c95f2b1e8db96578446d3781ade3acf4540288f933b3dc5_amd64 as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/code-rhel9@sha256:a408da5c9d9e5c3e9ea1ed10eda3a539707972da9aafd3aa62f587f3f36f607a_arm64 as a component of Red Hat OpenShift Dev Spaces 3.30
- Summary
- A flaw was found in Mermaid XY Charts. A remote attacker could exploit this by providing invalid parameters when configuring an X-Axis. This could lead to an infinite loop, causing a denial of service (DoS) due to memory exhaustion and potentially crashing the page or JavaScript process.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. From version 10.6.0 until 10.9.8 and 11.16.1, Mermaid XY Charts are vulnerable to an infinite loop denial of service in the setXAxisRangeData function when configuring an X-Axis with invalid parameters. Because each loop iteration appends an element to an array, this generally causes a RangeError to appear after a few seconds, but it may instead cause the page or JavaScript process to crash from memory exhaustion, depending on the environment. This issue is fixed in versions 10.9.8 and 11.16.1.
What
Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. From version 10.6.0 until 10.9.8 and 11.16.1, Mermaid XY Charts are vulnerable to an infinite loop denial of service in the setXAxisRangeData function when configuring an X-Axis with invalid parameters. Because each loop iteration appends an element to an array, this generally causes a RangeError to appear after a few seconds, but it may instead cause the page or JavaScript process to crash from memory exhaustion, depending on the environment. This issue is fixed in versions 10.9.8 and 11.16.1.
Why
A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.
How
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.
What
Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. From version 10.6.0 until 10.9.8 and 11.16.1, Mermaid XY Charts are vulnerable to an infinite loop denial of service in the setXAxisRangeData function when configuring an X-Axis with invalid parameters. Because each loop iteration appends an element to an array, this generally causes a RangeError to appear after a few seconds, but it may instead cause the page or JavaScript process to crash from memory exhaustion, depending on the environment. This issue is fixed in versions 10.9.8 and 11.16.1.
Why
A malformed condition prevents a loop from making progress or terminating, allowing resource exhaustion.
How
An attacker operating through a network path may attempt exploitation when the stated preconditions are met. If successful, the issue may disrupt the affected service.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Loop with Unreachable Exit Condition ('Infinite Loop') → disrupt the affected service
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Passive interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Not a CVSS 4.0 base metric
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-835 ↗
CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop'). The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:LCommon Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.ATNoneAttack requirements: No additional deployment or execution condition is required.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIPassiveUser interaction: A user must unknowingly interact with the vulnerable system.VCNoneVulnerable-system confidentiality: No direct loss is represented by this metric.VINoneVulnerable-system integrity: No direct loss is represented by this metric.VALowVulnerable-system availability: A successful attack can cause a limited loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SALowSubsequent-system availability: A successful attack can cause a limited loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Fixed
- registry.redhat.io/devspaces/code-rhel9@sha256:02f759255a2259ae4c7e41a980dcecc9a72efcfb050dcdbeba4469d62eb352db_s390x as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/code-rhel9@sha256:23f78b2564f05173a9d5beb28d85369c6d2c095b479d4d11f3a8f1aae0844f04_ppc64le as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/code-rhel9@sha256:7cb88955f069bb340c95f2b1e8db96578446d3781ade3acf4540288f933b3dc5_amd64 as a component of Red Hat OpenShift Dev Spaces 3.30
- registry.redhat.io/devspaces/code-rhel9@sha256:a408da5c9d9e5c3e9ea1ed10eda3a539707972da9aafd3aa62f587f3f36f607a_arm64 as a component of Red Hat OpenShift Dev Spaces 3.30
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 6 Aug 2026 · Last source change 7 Aug 2026, 16:17 UTC · CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-54241
Product sourceCNA
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- >= 10.6.0, < 10.9.8; >= 11.0.0-alpha.1, < 11.16.1 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- >= 10.6.0, < 10.9.8; >= 11.0.0-alpha.1, < 11.16.1 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.