{"answers":{"affected":"2 open source packages ship an affected version, including next-mdx-remote.","exploited":"There is no known exploitation of CVE-2026-0969 in the wild and no public exploit code.","fix":"Upgrade next-mdx-remote to 6.0.0 or later.","what":"CVE-2026-0969 is a high-severity code injection vulnerability in HashiCorp Shared library, published on 12 Feb 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-0969 and fix it if it is affected.\n\nWhat it is: CVE-2026-0969 is a high-severity code injection vulnerability in HashiCorp Shared library, published on 12 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-0969 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- next-mdx-remote (npm): affected from 4.3.0; fixed in 6.0.0\n- next-mdx-remote (npm): affected from 4.3.0; fixed in 6.0.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-0969/ (Markdown: https://insights.sbomify.com/CVE-2026-0969/index.md)","id":"CVE-2026-0969","markdown":"https://insights.sbomify.com/CVE-2026-0969/index.md","name":"CVE-2026-0969","record":{"aliases":["GHSA-g4xw-jxrg-5f6m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"React MDX library","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by providing malicious MDX content to the next-mdx-remote library during server-side rendering.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"HashiCorp","cpe":[],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"The serialize function used to compile MDX in next-mdx-remote is vulnerable to arbitrary code execution due to insufficient sanitization of MDX content. This vulnerability, CVE-2026-0969, is fixed in next-mdx-remote 6.0.0.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Arbitrary code execution in React server-side rendering of untrusted MDX content","id":"CVE-2026-0969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"GoAnywhere MFT SAML Sessions do not redirect to logout URL on session timeout","id":"CVE-2026-0971"},"packages":[{"ecosystem":"npm","fixed":["6.0.0"],"introduced":["4.3.0"],"last_affected":[],"package":"next-mdx-remote","purl":null,"source":"GHSA-g4xw-jxrg-5f6m"},{"ecosystem":"npm","fixed":["6.0.0"],"introduced":["4.3.0"],"last_affected":[],"package":"next-mdx-remote","purl":"pkg:npm/next-mdx-remote","source":"GHSA-g4xw-jxrg-5f6m"}],"prev":{"headline":"Libssh: libssh: denial of service due to malformed sftp message","id":"CVE-2026-0968"},"products":["Shared library"],"published":"2026-02-12","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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-17","vendors":["HashiCorp"]},"summary":"Attackers can execute arbitrary code by providing malicious MDX content to the next-mdx-remote library during server-side rendering.","url":"https://insights.sbomify.com/CVE-2026-0969/"}