Repository navigation
Telegram Support Bot v6.0.1
A security patch release for v6.0.0. Docker images: bostrot/telegram-support-bot:v6.0.1 / :latest (amd64, arm64). There are no configuration or behaviour changes, and all Discord and Signal deployments should update.
🔒 Security fixes
- Request forgery (server-side request forgery,
js/request-forgery): IDs that end up in outgoing API request paths are now strictly validated and URL-encoded (#222).- Discord: channel IDs must be numeric 17–20 digit snowflakes. Names that don't resolve to one, and invalid configured or cached IDs, are rejected instead of being passed through.
- Signal: attachment IDs from incoming messages must be a single safe path segment.
- This completes the hardening from v6.0.0 (#218, Discord guild IDs and Signal group lookups).
- Resource exhaustion (
js/resource-exhaustion): the Discord gateway heartbeat interval is bounded with a safe default, and reconnects replace the previous timer (#218, verified in this release).
All three open code-scanning alerts (#17, #18, #19) are resolved, and code scanning reports 0 open alerts. Regression tests were added for each case.
🛠 Maintenance
- CI: a new
Testworkflow runsnpm ci, build,npm testandnpx eslint src/on Node 26 for every pull request and every push tomaster(#222). - Docs: the comment in
src/defaults.tsnow correctly says thatMONGO_URIoverridesmongodb_uri(since #199; comment only, no behaviour change). The wiki's Upgrading the bot page now covers the v6.0.0 breaking changes.
⬆️ Upgrading
From 6.0.0, just update:
- Docker:
git pull && docker compose build --pull supportbot && docker compose up -d, or pullbostrot/telegram-support-bot:v6.0.1. - npm:
git pull && npm ci && npm run build && npm run prod
Coming from 5.x? Read the v6.0.0 breaking changes first: Node 26+, MongoDB 4.4+, MONGO_URI precedence, and no arm/v7 image.
Pull requests
#222 Validate Discord and Signal request path IDs, fix MONGO_URI comment, add CI tests · #223 Release v6.0.1
Contributors
Full Changelog: v6.0.0...v6.0.1