Intel

AIKIDO-2026-522265

@chat-adapter/slack is vulnerable to Information Disclosure

Pre-CVE
Found by Aikido Intel before public disclosure or CVE publication.
Published Oct 15, 2026
October 15, 2026

55

CVE Score

Medium

Information Disclosure

Are you affected? Scan for Free

TL;DR

Slack sets a remote file's url_private to the external_url supplied to files.remote.add, and that URL does not have to be a Slack host. @chat-adapter/slack fetchSlackFile in packages/adapter-slack/src/index.ts (message attachments and rehydrateAttachment) and packages/adapter-slack/src/api/client.ts fetches that URL with the bot bearer token and no origin check, so a download sends the token to the remote host, where it can be used with the bot's Slack scopes. The adapter fetch also follows the URL with no private-address check. Version 4.39.0 attaches the bearer token only for trusted Slack file origins or the configured API origin, and the adapter downloader refuses non-HTTPS and internal addresses.

How do I fix this?

Upgrade the @chat-adapter/slack library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and your deployment downloads Slack message file attachments through this adapter.

Versions

4.0.0 - 4.38.1

Fixed in 4.39.0

Background info

@chat-adapter/slack is vulnerable to Information Disclosure in versions 4.0.0 - 4.38.1.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea