You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GHSA-7w5x-hrqm-74c2 (CVE-2026-85730, high severity, GitHub-reviewed): parse() in smol-toml <=1.7.0 can be forced into an infinite loop by a malformed TOML document (an array/inline-table value followed by a comment with no trailing newline), causing a denial of service. Fixed upstream in 1.7.1; this PR pins the latest 1.8.0.
Risk assessment
Runtime/dev/build/CI scope: dev-only in both manifests (root: via markdownlint-cli2; docs-site: via astro / @astrojs/internal-helpers)
Direct/transitive: transitive (no direct smol-toml dependency in either manifest); pinned via npm overrides
Reachability: only used by dev tooling (markdown linting, Astro docs build), not by the runtime firewall CLI or containers; parses trusted repo-local files, not attacker-controlled input in production, so exploitability is low, but the fix is a trivial patch bump with no known breaking changes
Validation
Commands run: npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts (root and docs-site, isolated from the internal ms-feed mirror), npm audit (both)
Result: root goes from findings on smol-toml/markdownlint-cli2 to 0 vulnerabilities; docs-site's smol-toml finding is resolved (7 pre-existing unrelated moderate ajv/dompurify findings remain, intentionally out of scope)
Remaining gaps: full npm install (with lifecycle scripts) is not runnable in this sandbox due to a persistent, unrelated npm "Exit handler never called!" issue; validated via --package-lock-only instead. Lockfiles were hand-patched (rather than regenerated) to avoid unrelated libc metadata churn from a newer local npm version.
Deployment/canary owner confirms runtime health, if needed
Rollback guidance
Revert this PR, or pin smol-toml back to 1.7.0 in the four changed files together (both overrides entries and both lockfile entries must be reverted as a set).
Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Caution
Protected files were modified in this change.
This pull request is in
request-reviewmode and requires explicit human scrutiny before merge.Protected files:
package-lock.json,package.jsonDependency Release Train Summary
What changed
smol-toml(npm, transitive dev dependency)package.json/package-lock.json(root),docs-site/package.json/docs-site/package-lock.jsonWhy now
GHSA-7w5x-hrqm-74c2 (CVE-2026-85730, high severity, GitHub-reviewed):
parse()in smol-toml <=1.7.0 can be forced into an infinite loop by a malformed TOML document (an array/inline-table value followed by a comment with no trailing newline), causing a denial of service. Fixed upstream in 1.7.1; this PR pins the latest 1.8.0.Risk assessment
markdownlint-cli2; docs-site: viaastro/@astrojs/internal-helpers)smol-tomldependency in either manifest); pinned via npmoverridesValidation
npm install --registry=https://registry.npmjs.org/ --package-lock-only --ignore-scripts(root anddocs-site, isolated from the internal ms-feed mirror),npm audit(both)smol-toml/markdownlint-cli2to 0 vulnerabilities; docs-site's smol-toml finding is resolved (7 pre-existing unrelated moderateajv/dompurifyfindings remain, intentionally out of scope)npm install(with lifecycle scripts) is not runnable in this sandbox due to a persistent, unrelated npm "Exit handler never called!" issue; validated via--package-lock-onlyinstead. Lockfiles were hand-patched (rather than regenerated) to avoid unrelatedlibcmetadata churn from a newer local npm version.Control Plane
Smart-Dependabot-Merge-Candidate: yes
Reviewer checklist
Rollback guidance
smol-tomlback to1.7.0in the four changed files together (bothoverridesentries and both lockfile entries must be reverted as a set).Note
This was originally intended as a pull request, but the git push operation failed.
Original error: The process '/usr/bin/git' failed with exit code 128
Workflow Run: View run details and download bundle artifact
The bundle file is available in the
agentartifact in the workflow run linked above.Create the pull request manually
Warning
Firewall blocked 1 domain
The following domain was blocked by the firewall during workflow execution:
msfeed25.pkgs.visualstudio.comTo allow these domains, add them to the
network.allowedlist in your workflow frontmatter:See Network Configuration for more information.
Add this agentic workflow to your repo
To install this agentic workflow, run