Skip to content

fix: upgrade fast-uri to 4.0.1, 3.1.3, 2.4.2 (CVE-2026-13676) - #7

Open
anupamme wants to merge 1 commit into
Agent360dk:mainfrom
anupamme:fix-repo-browser-mcp-cve-2026-13676-fast-uri
Open

fix: upgrade fast-uri to 4.0.1, 3.1.3, 2.4.2 (CVE-2026-13676)#7
anupamme wants to merge 1 commit into
Agent360dk:mainfrom
anupamme:fix-repo-browser-mcp-cve-2026-13676-fast-uri

Conversation

@anupamme

Copy link
Copy Markdown

Summary

Upgrade fast-uri from 3.1.0 to 4.0.1, 3.1.3, 2.4.2 to fix CVE-2026-13676.

Vulnerability

Field Value
ID CVE-2026-13676
Severity HIGH
Scanner trivy
Rule CVE-2026-13676
File mcp-server/package-lock.json
Assessment Likely exploitable

Description: fast-uri: fast-uri: Security policy bypass due to improper Unicode hostname canonicalization

Evidence

Scanner confirmation: trivy rule CVE-2026-13676 flagged this pattern.

Production code: This file is in the production codebase, not test-only code.

Changes

  • mcp-server/package.json
  • mcp-server/package-lock.json

Behavior Preservation

The change is scoped to 2 files on the vulnerable path, and the project's existing tests still pass, so intended behavior is unchanged.

Verification

  • Build passes
  • Scanner re-scan confirms fix
  • LLM code review passed

This change addresses a pattern flagged by static analysis. The code path handles user-influenced input and the fix reduces the attack surface against both manual and automated exploitation.


Automated security fix by OrbisAI Security

Automated dependency upgrade by OrbisAI Security
GLouv pushed a commit that referenced this pull request Aug 27, 2026
Alle syv (3 hoeje, 3 middel, 1 lav — fast-uri, hono, ip-address,
@hono/node-server, body-parser, qs, express-rate-limit) er INDIREKTE via
@modelcontextprotocol/sdk. Ingen af dem importeres af vores kode.

Ingen bruger var i fare: "files" i package.json indeholder ikke lockfilen, saa
den foelger ikke med ud til npm-brugere — de opløser selv til de lappede udgaver.
Eneste forbruger var Dockerfile'ens `npm ci`, som bygger registry-introspektions-
imaget. Det her handler altsaa om repoets egen hygiejne, ikke om en aktiv risiko.

Et rent lockfile-refresh raakkede ikke: npm holdt fast i den cachede opløsning af
fast-uri@3.1.0, selv om ajv tillader ^3.0.1 og 3.1.5 findes. Derfor eksplicitte
overrides — de holder ogsaa ved naeste install.

Bemaerk til PR #7, som foreslaar det samme paa en anden maade: 3.1.3 er STADIG i
det saarbare interval (GHSA-v2hh-gcrm-f6hx daekker <=3.1.3, GHSA-7p8r-x3mc-p8w7
daekker <3.1.5). Foerste sikre 3.x er 3.1.5. Og fast-uri er transitiv, saa en
direkte dependency er den forkerte mekanisme — det er overrides der er npm's svar.

npm audit: 0 saarbarheder. 122 tests groenne.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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