{"answers":{"affected":"2 open source packages ship an affected version, including AngleSharp.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54570 exists.","fix":"Upgrade AngleSharp to 1.5.0 or later.","what":"CVE-2026-54570 is a medium-severity cross-site scripting vulnerability in AngleSharp, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-54570 and fix it if it is affected.\n\nWhat it is: CVE-2026-54570 is a medium-severity cross-site scripting vulnerability in AngleSharp, published on 18 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54570 exists.\n\nAffected packages and fixed versions:\n- AngleSharp (NuGet): affected all versions; fixed in 1.5.0\n- AngleSharp (NuGet): affected all versions; fixed in 1.5.0\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-54570/ (Markdown: https://insights.sbomify.com/CVE-2026-54570/index.md)","id":"CVE-2026-54570","markdown":"https://insights.sbomify.com/CVE-2026-54570/index.md","name":"CVE-2026-54570","record":{"aliases":["ECHO-dcab-2378-985b","GHSA-pgww-w46g-26qg"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"AngleSharp HTML parser","requires_auth":"none","summary":"Attackers can exploit a parser differential in AngleSharp to bypass sanitizers and execute malicious scripts via mutation XSS.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-80","name":"Improper Neutralization of Script-Related HTML Tags in a Web Page"}],"description":"AngleSharp is a .NET library for parsing angle bracket based hyper-texts. Prior to 1.5.0, MathAnnotationXmlElement in AngleSharp/Mathml/Dom/Internal/MathAnnotationXmlElement.cs is not treated as an HTML integration point when its encoding attribute is text/html or application/xhtml+xml, causing Consume in AngleSharp/Html/Parser/HtmlDomBuilder.cs to route tokens through foreign-content parsing instead of HTML parsing. A sanitizer can therefore observe a different DOM from the browser that reparses the serialized output. An attacker can combine this namespace differential with markup-breaking characters in an attribute value so that an element hidden from the sanitizer becomes active script-capable HTML after browser reparse, resulting in mutation cross-site scripting. This issue is fixed in version 1.5.0.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"AngleSharp: HTML5 Spec Compliance: mXSS via annotation-xml HTML Integration Point Bypass","id":"CVE-2026-54570","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"xss","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"ESPAsyncWebServer: Integer overflow in multipart boundary parser causes denial of service","id":"CVE-2026-54571"},"packages":[{"ecosystem":"NuGet","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"AngleSharp","purl":null,"source":"GHSA-pgww-w46g-26qg"},{"ecosystem":"NuGet","fixed":["1.5.0"],"introduced":["0"],"last_affected":[],"package":"AngleSharp","purl":"pkg:nuget/AngleSharp","source":"GHSA-pgww-w46g-26qg"}],"prev":{"headline":"senaite.core Vulnerable to Eval Injection and Missing Authorization","id":"CVE-2026-54569"},"products":["AngleSharp"],"published":"2026-08-18","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-18","vendors":["AngleSharp"]},"summary":"Attackers can exploit a parser differential in AngleSharp to bypass sanitizers and execute malicious scripts via mutation XSS.","url":"https://insights.sbomify.com/CVE-2026-54570/"}