Skip to content

Admin, data, and filesystem-boundary batch (GHSA)

Signal: GitHub Security Advisories surfaced a 2026-05-04 batch where admin-like panels and filesystem adapters failed to separate low-trust users, station/project data, and host files.

Advisories in this batch

Why this is durable

Admin utilities, importers, WebDAV, markdown attachments, model/tool logs, and data readers often sit beside trusted workflows. Attackers look for these “supporting” paths because they frequently skip the same authorization, path containment, output encoding, secret redaction, and resource limits as the main product.

Immediate triage

  1. Patch zrok, Pelican, phpVMS, livewire-markdown-editor, n8n-MCP, and ParquetSharp where present.
  2. Disable phpVMS importers and destructive maintenance endpoints unless they are behind strong admin auth and CSRF protection.
  3. Audit WebDAV roots for symlinks and unexpected files created or modified outside intended storage.
  4. Redact and rotate MCP/tool secrets that may have been logged in n8n-MCP HTTP mode.
  5. Quarantine untrusted Parquet files and process them with resource limits until patched.

Hunt ideas

  • Search WebDAV access logs for symlink names, dot segments, encoded separators, and writes near host config paths.
  • Review phpVMS logs for /importer hits from non-admin sessions or unauthenticated clients, followed by table drops or mass deletes.
  • Search uploaded markdown attachments for HTML, SVG, polyglot images, executable MIME mismatches, and stored-script payloads.
  • Grep n8n-MCP logs for Authorization, API tokens, prompt/tool arguments, filesystem paths, and credential-shaped strings.

Durable controls

  • Use no-follow opens and canonical path containment for every filesystem adapter, not just HTTP file serving.
  • Require explicit admin authorization and confirmation for importers, migrations, resets, and destructive utilities.
  • Store tool-call logs behind redaction middleware with field-level deny lists for secrets, prompts, tokens, and credentials.
  • Put parser-heavy data formats behind depth, size, type-width, and CPU/memory budgets.

Operator lesson

Support features are production attack surface. If it imports, mounts, uploads, logs, or parses on behalf of a user, test it like an admin panel.