{"answers":{"affected":"2 open source packages ship an affected version, including mermaid.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71437 exists.","fix":"Upgrade mermaid to 11.16.1 or later.","what":"CVE-2026-71437 is a medium-severity vulnerability in mermaid-js mermaid, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-71437 and fix it if it is affected.\n\nWhat it is: CVE-2026-71437 is a medium-severity vulnerability in mermaid-js mermaid, published on 6 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-71437 exists.\n\nAffected packages and fixed versions:\n- mermaid (npm): affected from 11.5.0; fixed in 11.16.1\n- mermaid (npm): affected from 11.5.0; fixed in 11.16.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-71437/ (Markdown: https://insights.sbomify.com/CVE-2026-71437/index.md)","id":"CVE-2026-71437","markdown":"https://insights.sbomify.com/CVE-2026-71437/index.md","name":"CVE-2026-71437","record":{"aliases":["CLEANSTART-2026-VN44005","DEBIAN-CVE-2026-71437","GHSA-3rrr-jr9j-h3q3","MINI-2jvp-98h4-crph","MINI-q5x3-44hg-hpmf","UBUNTU-CVE-2026-71437"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript diagramming library","requires_auth":"low_privilege","summary":"Attackers can pollute Object.prototype via malicious diagram text, potentially compromising the embedding application's behavior.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"Mermaid is a JavaScript tool that uses Markdown-inspired text to create and modify diagrams and charts. From version 11.5.0 until 11.16.1, Mermaid Architecture Diagrams are vulnerable to prototype pollution when a diagram defines a group with an id of __proto__. Because the group id is used directly as an object property key without validation, an attacker who can supply diagram text can pollute Object.prototype, potentially affecting the behavior of the embedding application. This issue is fixed in version 11.16.1.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Mermaid Architecture diagrams are vulnerable to prototype pollution","id":"CVE-2026-71437","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Mermaid configuration APIs allow prototype pollution","id":"CVE-2026-71438"},"packages":[{"ecosystem":"npm","fixed":["11.16.1"],"introduced":["11.5.0"],"last_affected":[],"package":"mermaid","purl":null,"source":"GHSA-3rrr-jr9j-h3q3"},{"ecosystem":"npm","fixed":["11.16.1"],"introduced":["11.5.0"],"last_affected":[],"package":"mermaid","purl":"pkg:npm/mermaid","source":"GHSA-3rrr-jr9j-h3q3"}],"prev":{"headline":"Mermaid XY Charts are vulnerable to an infinite loop DoS","id":"CVE-2026-71436"},"products":["mermaid"],"published":"2026-08-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-07","vendors":["mermaid-js"]},"summary":"Attackers can pollute Object.prototype via malicious diagram text, potentially compromising the embedding application's behavior.","url":"https://insights.sbomify.com/CVE-2026-71437/"}