Repository navigation
fix(ci): clear two new markdownlint-cli transitive CVEs (katex, smol-toml) - #478
Merged
Merged
Conversation
…toml) Two new advisories landed and were GitHub-reviewed today, both reachable through [email protected]'s dependency tree (the version adopted in #471/#548's markdownlint-cli2 -> markdownlint-cli migration): - katex 0.11.0-0.18.1: CVE-2026-103923 / GHSA-238p-pmpm-9mq7, a prototype-pollution bypass of trust restrictions (low severity). Reached via markdownlint -> micromark-extension-math -> katex. - smol-toml <=1.8.0: GHSA-r4xh-jqrq-34v2, a quadratic-time parse() DoS on ordinary valid TOML input (moderate severity). Reached via markdownlint-cli -> smol-toml directly. Both have patched releases (katex 0.18.2, smol-toml 1.9.0) and this is a straightforward override bump, unlike the braces CVE that prompted the markdownlint-cli2 -> markdownlint-cli migration in the first place (that one had no patched release at all). Confirmed this independently reproduces on main as-is (not introduced by this change, and not specific to any one PR) before fixing it: $ npm ci && npm audit --audit-level=moderate # on main, unmodified 5 vulnerabilities (3 low, 2 moderate) After adding the two overrides: $ npm ci && npm audit --audit-level=moderate found 0 vulnerabilities $ node .github/linters/run-markdownlint.mjs --count-only 190 $ node .github/linters/run-markdownlint.mjs (exit 0, clean) markdownlint-cli itself stays pinned at 0.49.1; only its own transitive katex and smol-toml resolutions move. Co-authored-by: OpenCode Agent <[email protected]>
wz-gsa
added a commit
that referenced
this pull request
Oct 6, 2026
🤖 I have created a release *beep* *boop* --- ## [1.12.1](v1.12.0...v1.12.1) (2026-10-06) ### Bug Fixes * **ci:** clear two new markdownlint-cli transitive CVEs (katex, smol-toml) ([#478](#478)) ([f1913ba](f1913ba)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: William Zujkowski <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Two new advisories landed and were GitHub-reviewed today, both reachable through
[email protected]'s dependency tree (the version adopted in #471/#548'smarkdownlint-cli2→markdownlint-climigration):katex0.11.0–0.18.1:CVE-2026-103923/GHSA-238p-pmpm-9mq7, a prototype-pollution bypass of trust restrictions (low severity). Reached viamarkdownlint→micromark-extension-math→katex.smol-toml≤1.8.0:GHSA-r4xh-jqrq-34v2, a quadratic-timeparse()DoS on ordinary valid TOML input (moderate severity). Reached viamarkdownlint-cli→smol-tomldirectly.Both have patched releases (
[email protected],[email protected]) — unlike thebracesCVE that prompted themarkdownlint-cli2→markdownlint-climigration in the first place (that one had no patched release at all). This is a straightforward override bump.Not caused by this PR, not caused by #471/#548 either
Confirmed independently: this reproduces on current
main, unmodified, before making any change:Same "advisory lands, previously-green gate goes red with zero local changes" pattern as the
bracesCVE #471 fixed — these two were just GitHub-reviewed hours after #471/#548 merged.Fix
Two
overridesentries added to.github/linters/package.json.markdownlint-cliitself stays pinned at0.49.1; only its own transitivekatexandsmol-tomlresolutions move.Verification
190 matches the exact file-count parity established in #471.
Safety Checklist
Security Impact
Clears a moderate-severity DoS advisory and a low-severity prototype-pollution advisory in dev-only, CI-only tooling (markdown linting). No application runtime impact.
AI Disclosure
This PR was prepared with OpenCode AI assistance. Human review is required before merge.