Skip to content

chore(security): accept picomatch ReDoS until a fix ships - #22

Merged
cacack merged 1 commit into
mainfrom
chore/osv-ignore-picomatch-redos
Nov 18, 2026
Merged

cacack merged 1 commit into
mainfrom
chore/osv-ignore-picomatch-redos

Conversation

@cacack

@cacack cacack commented Nov 18, 2026

Copy link
Copy Markdown
Owner

Accepts GHSA-fc5q-39xc-vjpf (picomatch ReDoS) in .osv-scanner.toml until a fix ships.

  • Advisory: CVE-2026-112366, CVSS 8.7. OSV revised it on 2026-11-17 to cover picomatch through 4.0.7, with no fixed version.
  • Affected here: bash-language-server 5.8.1 and vscode-langservers-extracted 4.10.0 (picomatch 2.3.2), yaml-language-server 2.0.0 (picomatch 4.0.7). npm has no newer bash-language-server or vscode-langservers-extracted.
  • Why acceptable: exploiting it takes attacker-supplied glob patterns; these language servers get globs only from our own editor and workspace configs.
  • Expiry: 2027-01-17, two months, like the existing bash-language-server entries.
  • Impact: it was failing security-deps on every supply-chain PR (seen on chore(deps): update dependency ubuntu to v26 #20) and would fail the weekly scan.

Verify: make security-deps passes locally with the entry ("No issues found"); security-deps passes on this PR.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CSVrYV8Q2U4YTwnnLKZJqU

GHSA-fc5q-39xc-vjpf (CVE-2026-112366) was revised on 2026-11-17 to cover
picomatch through 4.0.7 with no fixed release, failing security-deps on
every supply-chain PR. It is reachable only through glob patterns, which
the Neovim language servers take from our own configs. Expires in two
months, like the other language-server entries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CSVrYV8Q2U4YTwnnLKZJqU
@cacack
cacack merged commit b82f537 into main Nov 18, 2026
6 checks passed
@cacack
cacack deleted the chore/osv-ignore-picomatch-redos branch November 18, 2026 00:34
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.

1 participant