Skip to content

fix(deps): update dependency next-mdx-remote to v6 [security] - #493

Open
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-next-mdx-remote-vulnerability
Open

fix(deps): update dependency next-mdx-remote to v6 [security]#493
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-next-mdx-remote-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
next-mdx-remote 5.0.06.0.0 age confidence

next-mdx-remote affected by arbitrary code execution in React server-side rendering of untrusted MDX content

CVE-2026-0969 / GHSA-g4xw-jxrg-5f6m

More information

Details

The serialize function used to compile MDX in next-mdx-remote is vulnerable to arbitrary code execution due to insufficient sanitization of MDX content.

Severity

  • CVSS Score: 8.8 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

hashicorp/next-mdx-remote (next-mdx-remote)

v6.0.0

Compare Source

Breaking/Major Changes

Configuration

📅 Schedule: (in timezone Europe/London)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot changed the title fix(deps): update dependency next-mdx-remote to v6 [security] fix(deps): update dependency next-mdx-remote to v6 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate
renovate Bot deleted the renovate/npm-next-mdx-remote-vulnerability branch March 27, 2026 02:03
@renovate renovate Bot changed the title fix(deps): update dependency next-mdx-remote to v6 [security] - autoclosed fix(deps): update dependency next-mdx-remote to v6 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch 3 times, most recently from 2b0ce30 to 88aa417 Compare April 4, 2026 11:48
@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch from 88aa417 to c68b2f8 Compare April 18, 2026 19:52
@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch from c68b2f8 to 2dbc145 Compare April 26, 2026 10:15
@renovate renovate Bot changed the title fix(deps): update dependency next-mdx-remote to v6 [security] fix(deps): update dependency next-mdx-remote to v6 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title fix(deps): update dependency next-mdx-remote to v6 [security] - autoclosed fix(deps): update dependency next-mdx-remote to v6 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch 2 times, most recently from 2dbc145 to c5c0502 Compare April 27, 2026 21:53
@sonarqubecloud

Copy link
Copy Markdown

1 similar comment
@sonarqubecloud

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch from c5c0502 to cfac9b4 Compare June 24, 2026 21:59
@sonarqubecloud

Copy link
Copy Markdown

@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch 2 times, most recently from 5b1e505 to a3c6273 Compare July 27, 2026 19:12
@renovate
renovate Bot force-pushed the renovate/npm-next-mdx-remote-vulnerability branch from a3c6273 to 823569f Compare July 27, 2026 22:49
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants